|
|
Post by Chuck Elliot on Nov 5, 2015 15:14:18 GMT -5
The protocol now has a method for directly setting the video and analog sources outside of the preset buttons(T; 1-8).
Would this be a worthwhile addition to the PC App?
|
|
|
|
Post by wilburthegoose on Nov 5, 2015 18:57:54 GMT -5
Definitely yes!
|
|
|
|
Post by geebo on Nov 5, 2015 18:59:09 GMT -5
|
|
|
|
Post by etc6849 on Nov 13, 2015 19:34:10 GMT -5
Hi guys, quick question. I'm building a module for my home automation system to control my new to me XMC-1.
All UDP commands work except set_volume. Any ideas what I'm doing wrong? I do have a subscription to volume notifications.
xmc-1 command sent: <?xml version="1.0" encoding="utf-8"?><emotivaControl><set_volume value="-39" ack="no" /></emotivaControl>
But I see that the volume doesn't actually change as the notification below shows. What's really weird is sometimes it works (maybe 1/10 set_volume commands)! Volume up/down works great, but I really want discrete values, and think I'm just missing something in the syntax.
<?xml version="1.0"?>
<emotivaNotify>
<volume value="-55.0" visible="true"/>
</emotivaNotify>
|
|
|
|
Post by Chuck Elliot on Nov 13, 2015 19:40:09 GMT -5
Hi guys, quick question. I'm building a module for my home automation system to control my new to me XMC-1. All UDP commands work except set_volume. Any ideas what I'm doing wrong? I do have a subscription to volume notifications. xmc-1 command sent: <?xml version="1.0" encoding="utf-8"?><emotivaControl><set_volume value="-39" ack="no" /></emotivaControl> But I see that the volume doesn't actually change as the notification below shows. What's really weird is sometimes it works (maybe 1/10 set_volume commands)! Volume up/down works great, but I really want discrete values, and think I'm just missing something in the syntax. <?xml version="1.0"?> <emotivaNotify> <volume value="-55.0" visible="true"/> </emotivaNotify> The first invocation of the set volume command acts as a "wake-up" to the OSD and front panel display. you need to do it twice. Trims are the same. Attachments:Control Delay.pdf (44.19 KB)
|
|
|
|
Post by etc6849 on Nov 13, 2015 21:21:03 GMT -5
Thank you! That explains why it worked a few times before (cause I was clicking very fast). This seems like a firmware bug since it's not covered in the 7/29/2015 protocol document (unless I'm using an old version). No other device I've ever worked with has been that finicky, but it's just this one command, so and the work around is no big deal. The first invocation of the set volume command acts as a "wake-up" to the OSD and front panel display. you need to do it twice. Trims are the same. |
|
|
|
Post by etc6849 on Nov 13, 2015 22:34:46 GMT -5
Another question: I don't see a command for "surround" sound mode in the 7/29/2015 documentation? Seems all the other sound mode commands are there (stereo, direct, etc...).
|
|
|
|
Post by Chuck Elliot on Jan 17, 2016 17:56:29 GMT -5
I have been waiting for firmware 3.2 which is going to fix a lot of little problems in the remote protocol.
I have passed issues that I have found, such as no commands to adjust bass and treble trims, to Ray at Emotiva and he has confirmed several.
As soon as the firmware is out I will test and issue an update.
|
|
|
|
Post by etc6849 on Feb 7, 2016 11:05:30 GMT -5
Hi Chuck, It sounds like you have a great engineering contact at Emotiva, could you please talk them into adding a command to swap side and rear speakers? Discrete commands would be preferred, but I'll take whatever I could get. All processors seem to do this except the XMC-1 (my old Marantz AV8801 did this). It's an issue when you use WASAPI and send 5.1 (which bypasses the Windows 7.1 soundcard settings). Plus most of use with towers for surrounds only have space to put them in the rear... Thanks! I have been waiting for firmware 3.2 which is going to fix a lot of little problems in the remote protocol. I have passed issues that I have found, such as no commands to adjust bass and treble trims, to Ray at Emotiva and he has confirmed several. As soon as the firmware is out I will test and issue an update. |
|
|
|
Post by wilburthegoose on Feb 7, 2016 16:53:03 GMT -5
I'd also love a command to toggle through all the inputs like we have on the remote.
|
|
|
|
Post by etc6849 on Feb 7, 2016 19:32:57 GMT -5
For me, I can do this through software as my home automation system tracks the selected input (even it was set by using the XMC-1's front panel or IR remote). I can just have the module I made to go to "next input" and it just does it. I can see this being an issue if things are out of sync, but I also have it query the XMC when it comes on if I remember right. I haven't tried Chuck's app, but thought it was "two-way" as well so maybe a button could be added that does something similar? I'd also love a command to toggle through all the inputs like we have on the remote. |
|
|
|
Post by Chuck Elliot on Feb 7, 2016 22:46:14 GMT -5
I'm not going to go back into the code until 3.2 firmware is out.
I will look through suggestions then!
|
|
|
|
Post by wilburthegoose on Mar 5, 2016 13:46:15 GMT -5
Strange - just did a Windows Update (Windows 10 home, 64-bit), and now the app's scan feature doesn't find my XMC-1.
It does show up as a "device" from Windows Control Panel.
Any idea what I should look at to solve the issue?
Thanks!
|
|
|
|
Post by Chuck Elliot on Mar 5, 2016 14:31:36 GMT -5
Scan you network using an ip scanner. I use this one: SlitherisThe XMC-1 reports itself as a Micro-Chip Lynus IP. Attempt to Ping the address associated with the above. Example: In a DOS box: ping 192.168.1.108 Be sure the Windows Firewall allows UDP traffic. |
|
|
|
Post by wilburthegoose on Mar 5, 2016 15:16:51 GMT -5
You're absolutely right. Darn thing isn't on the network.
|
|
hemster
Global Moderator 
Particle Manufacturer
...still listening... still watching
Posts: 51,951
|
Post by hemster on Mar 5, 2016 15:19:02 GMT -5
Strange - just did a Windows Update (Windows 10 home, 64-bit), and now the app's scan feature doesn't find my XMC-1. It does show up as a "device" from Windows Control Panel. Any idea what I should look at to solve the issue? Thanks! You've likely already done this but... a reboot (or better yet, a cold start) wouldn't hurt after an upgrade to a new OS. |
|
|
|
Post by wilburthegoose on Mar 5, 2016 15:42:13 GMT -5
Thanks - it's not the PC or the app - the XMC-1 has gone rogue  (it's not currently connected to my home network) |
|
|
|
Post by Chuck Elliot on Mar 5, 2016 16:00:59 GMT -5
You'll find it? Power cycle is a good idea.
PS: Still waiting for firmware 3.2 which will straighten out a number of interface issues in the protocol.
|
|
|
|
Post by wilburthegoose on Mar 5, 2016 16:06:04 GMT -5
I went to the menu settings on the XMC-1 and the DHCP settings were wacky (default gateway was a 10.* IP address, which I sure don't use at home).
Gave it a static IP, shows up in Slithers as device name - "Microchip" and OS as Linux.
Getting a "can't parse" from XMC-1 now. Parser error 139.
I'll do a cold boot (unplug it) and see what happens.
PS - The Emotiva app on my iPhone works. IIRC, I'll double-check the device name to make sure there aren't any spaces.
|
|
|
|
Post by Chuck Elliot on Mar 5, 2016 16:22:45 GMT -5
Did you just upgrade to 3.1a firmware too?  ? |
|
(it's not currently connected to my home network)
?