Author
Topic: New Onkyo device (Read 4913 times)

So, I recently picked up a new Onkyo receiver that has an Ethernet port instead of the serial. This makes it much easier to hook up to my LinuxMCE system but I now need to create the new device and I have two questions.

First, how can I copy the old device to a new one? All the same items apply and I was hoping to shortcut things a little bit.

Second, it appears that the same connection type can be used since it supports both serial and network connections but how do I send binary data? The string values are the same but there is a bunch of header/footer information that needs sent in a binary format.

there is no way to copy an existing template unfortunately, other than manually. and i dont think its possible to have a single template describe two connection methods.while i have not done so myself, there should be a way to send hex values in ruby.

In web admin, go Advanced -> sqlCVS. Check in both DCE and IR repositories. Then, create a trac ticket that contains the sqlCVS Batch IDs, as well as your contact details (batch IDs can be found out here http://schema.linuxmce.org/sqlCVS/?site=batch/view). Think that's it.

OK, so after a brief hiatus, I'm back at work on this device. I have all the codes researched and configured (I wrote a Perl script to send these commands to my receiver) and have just created the device in LinuxMCE.

Could you post the contents of your /var/log/xx_Generic_Serial_Device.log, where xx is your device #.

The most common reason that this error occurs is that your device data is incorrect.

For ethernet devices, you need to make sure that the TCP Port device data is defined, and that the correct port is specified. You also need to make sure the device has an IP Address specified, so that it knows where to connect to the device.

So, I forgot the TCP Port. I knew I was missing something there. I fixed it but I still got errors. I think I might have it working now. I made some changes to the selected checkboxes on the template. I'm at work right now so I can only monitor the logs. I'll test as soon as I get home.

Works great! Needed to do some bit fiddling to get it all working since I have to send binary commands. So far I have power on, off, and volume up, down working. As soon as I have something complete, I'll check it in.

Just a small tidbit of information regarding network controlling receivers. All of the receivers I have looked at til now have one BIG problem when controlled via network. Their "standyby" power usage sky rockets from <1W when not using network controll or HDMI control, to >50W when using it. This is standby power usage. Just something to look out for.

I don't even know if I can turn off the network control. My unit does chew through some power in standby mode, that's for sure. My almost airtight cabinet gets warm even when in standby. I put a computer chassis fan on the back of my cabinet to ventilate due to this.

Yes, Thom, it was rather simple but there are a few "gotchas" along the way if you don't know no better. My biggest problems are getting my binary strings correct. The Onkyo network protocol is annoying to begin with and then having to properly escape all the non-printable characters is fun too!

I will most likely be done with this by this weekend so I would love to ask, any pointers on doing a DHCP auto-detect script for this? All I need is to find something that exists already that I can steal.