|
|
Post by Chuck Elliot on Nov 11, 2014 10:27:47 GMT -5
Could someone with firmware 1.2 still loaded verify whether "Zone-2 Volume" works on their system? Zone 2 must be turned on to see the control. This seems to have stopped working with 1.3, but I may have screwed something up.  Also remember the the Tuner controls will not display unless Tuner is the source! |
|
|
|
Post by rogersch on Nov 11, 2014 13:14:06 GMT -5
Sorry Chuck I've no time tonight.
|
|
|
|
Post by weigle2 on Nov 11, 2014 16:08:16 GMT -5
Could someone with firmware 1.2 still loaded verify whether "Zone-2 Volume" works on their system? Zone 2 must be turned on to see the control. This seems to have stopped working with 1.3, but I may have screwed something up. Also remember the the Tuner controls will not display unless Tuner is the source! I could not get zone 2 volume to work. No OSD popup comes up like the Main zone. Did verify zone 2 was powered on. When changing the volume using the Emo remote control, the app display the change like it should, but the buttons in the app don't change anything. Looks like this part needs fixin' I am running 1.2 version. Chris |
|
|
|
Post by Chuck Elliot on Nov 11, 2014 16:15:09 GMT -5
Could someone with firmware 1.2 still loaded verify whether "Zone-2 Volume" works on their system? Zone 2 must be turned on to see the control. This seems to have stopped working with 1.3, but I may have screwed something up. Also remember the the Tuner controls will not display unless Tuner is the source! I could not get zone 2 volume to work. No OSD popup comes up like the Main zone. Did verify zone 2 was powered on. When changing the volume using the Emo remote control, the app display the change like it should, but the buttons in the app don't change anything. Looks like this part needs fixin' I am running 1.2 version. Chris There is no Zone2 popup. Addition controls appear in the Volume and Source frames. I observed the same thing you did. Changes on the "true" XMC-1 remote are reflected on the app, but the app Zone2 buttons do nothing. I will look at it later, tonight I'm taking a break! |
|
nuts
Minor Hero
50%
Posts: 36 
|
Post by nuts on Nov 11, 2014 16:25:21 GMT -5
Hi,
thanks for PC App und document!
Is it possible to wake up the XMC-1 from deep sleep mode?
Anyway the fist step (UDP broadcast '<?xml version="1.0" encoding="utf-8"?><emotivaPing />' => asnwer from XMC-1) works only one time for me (by my script) and then I have to restart my XMC-1 to receive the answer again.
Any idea what is wrong here?
|
|
|
|
Post by Chuck Elliot on Nov 11, 2014 16:55:23 GMT -5
Hi, thanks for PC App und document! Is it possible to wake up the XMC-1 from deep sleep mode? Anyway the fist step (UDP broadcast '<?xml version="1.0" encoding="utf-8"?><emotivaPing />' => asnwer from XMC-1) works only one time for me (by my script) and then I have to restart my XMC-1 to receive the answer again. Any idea what is wrong here? No not from "deep" sleep. Is the UDP port completely closed and re-open before the second try? Remember that the Ping goes out on Port 7000, but the reply comes back on Port 7001. |
|
nuts
Minor Hero
50%
Posts: 36
|
Post by nuts on Nov 12, 2014 15:06:45 GMT -5
Thanks for your answer. It seems like I am doing something wrong, because I see the XMC-1 response in wireshark.
Too sad that there is no "wake on lan".
|
|
|
|
Post by ÈlTwo on Nov 12, 2014 22:16:18 GMT -5
Solved the problem on my main PC, I had a Virtual Network on, once I disabled it the app works like a charm on my main PC now. Check your PC to see it it's a Firewall issue or if you have a virtual network.
|
|
edrummereasye
Sensei
"This aggression will not stand, man!"
Posts: 438
|
Post by edrummereasye on Nov 13, 2014 12:02:30 GMT -5
Hi, thanks for PC App und document! Is it possible to wake up the XMC-1 from deep sleep mode? Anyway the fist step (UDP broadcast '<?xml version="1.0" encoding="utf-8"?><emotivaPing />' => asnwer from XMC-1) works only one time for me (by my script) and then I have to restart my XMC-1 to receive the answer again. Any idea what is wrong here? I was thinking maybe they had some kind of timed lockout to prevent "ping of death" scenarios, and maybe had set it overly long...in most operational scenarios, you wouldn't send more than one emoPing unless you re-started your program (or were sending them manually due to lack of response)...but apparently it is responding, from your later post. Would still be interesting to see if it can be brought to its knees...  |
|
|
|
Post by Chuck Elliot on Nov 13, 2014 13:16:02 GMT -5
I was thinking maybe they had some kind of timed lockout to prevent "ping of death" scenarios, and maybe had set it overly long...in most operational scenarios, you wouldn't send more than one emoPing unless you re-started your program (or were sending them manually due to lack of response)...but apparently it is responding, from your later post. Would still be interesting to see if it can be brought to its knees... Isn't this rather pointless? a DOS attack on you XMC-1 is highly unlikely! In the "Full-Standby - Powered Standby - On" a requirement of Powered-Standby or manually pushing the Standby button is not much of a limitation. |
|
nuts
Minor Hero
50%
Posts: 36
|
Post by nuts on Nov 14, 2014 16:31:51 GMT -5
I was thinking maybe they had some kind of timed lockout to prevent "ping of death" scenarios, and maybe had set it overly long...in most operational scenarios, you wouldn't send more than one emoPing unless you re-started your program (or were sending them manually due to lack of response)...but apparently it is responding, from your later post. Would still be interesting to see if it can be brought to its knees... Its weird. If I split my script (first script to send "emoping", second script receive response) it works every time. If I do both in one script it only works once! I think it must be my fault but I cant find the bug. The standby limitation is not a big thing? Well I am not so sure .. I have to measure the power consumation in "Powered Standby" first and then we will see. |
|
|
|
Post by Chuck Elliot on Nov 14, 2014 16:58:54 GMT -5
Its weird. If I split my script (first script to send "emoping", second script receive response) it works every time. If I do both in one script it only works once! I think it must be my fault but I cant find the bug. I don't know the scripting system you are using. In my system, I send the ping on 7000 to 255.255.255.255(broadcast) and then wait for a data arrival event on 7001 to see the response. Both UDP ports are open before sending the ping. |
|
nuts
Minor Hero
50%
Posts: 36
|
Post by nuts on Nov 14, 2014 17:19:12 GMT -5
Mhm maybe my english isnt good enough to understand what you mean.
The UDP ports (7000, 7001, ..) always have to be open for communication with the XMC-1.
This cant be influenced by an application.
Or do you mean:
Open a socket to send "emoping" and open a socket (UDP Bind) to receive the response (thats what I did)?
P.S. scripting system is "autoit" for testing the API. Later I want to create some "useful" apps in python.
|
|
|
|
Post by Chuck Elliot on Nov 14, 2014 17:31:45 GMT -5
Mhm maybe my english isnt good enough to understand what you mean. The UDP ports (7000, 7001, ..) always have to be open for communication with the XMC-1. This cant be influenced by an application. Or do you mean: Open a socket to send "emoping" and open a socket (UDP Bind) to receive the response (thats what I did)? P.S. scripting system is "autoit" for testing the API. Later I want to create some "useful" apps in python. Here's what I do ( the ports ARE opened, or connected to by the app):
udpEmotivaTransponder.Protocol = sckUDPProtocol
udpEmotivaTransponder.Bind 7001
udpEmotivaPing.Protocol = sckUDPProtocol
udpEmotivaPing.RemoteHost = "255.255.255.255"
udpEmotivaPing.RemotePort = 7000
udpEmotivaPing.SendData ping ' ping packet previously built
------------------
'+
Private Sub udpemotivaTransponder_DataArrival(ByVal bytesTotal As Long)
'
'
'
Dim str As String
udpEmotivaTransponder.GetData str, vbString
'str has response packet
End Sub
|
|
|
|
Post by Chuck Elliot on Nov 16, 2014 20:24:52 GMT -5
30+ downloads. No comments/suggestions?  ? |
|
|
|
Post by geebo on Nov 16, 2014 21:51:54 GMT -5
30+ downloads. No comments/suggestions? ? Well, it just works. Not one issue since the naming problem I had. I've used it many times already and I appreciate you writing it for us. |
|
|
|
Post by ÈlTwo on Nov 16, 2014 21:56:46 GMT -5
Same here, since I got rid of the virtual network, it just works.
|
|
|
|
Post by Chuck Elliot on Nov 16, 2014 22:03:27 GMT -5
Thanks guys. I've got one. I think the menu controls are rather useless as there is no feedback of the operation being performed. The protocol has no feedback of what the OSD is displaying. There are also a number of set-up items such as Midnight-Mode and the Bass/Treble parameters that are not in the protocol. Once Emotiva releases their apps I will pester them. For now we're all thinking Dirac....Dirac....Dirac!!!!  |
|
hemster
Global Moderator 
Particle Manufacturer
...still listening... still watching
Posts: 51,951
|
Post by hemster on Nov 16, 2014 22:05:14 GMT -5
30+ downloads. No comments/suggestions? ? You did a great job Chuck! The latest version works great for me. I'm planning on adding a Zone 2 using a Sony wireless speaker I have in the closet. Should allow me to have music in any room in the house! Many thanks for your effort. Again, great job! I agree we can always embellish the app but it does what it does very well. |
|
|
|
Post by LuisV on Nov 16, 2014 22:09:26 GMT -5
Same here Chuck... no issues thus far as it simply works. How about an OS X version? |
|
?
