Onkyo Network Commands (non serial)

1,559 views
Skip to first unread message

Nahshon

unread,
Apr 7, 2010, 11:17:31 AM4/7/10
to CommandFusion
After 3 weeks of waiting the Onkyo TX-NR 5007 is ready for collection.

I just need to clarify certain things I have read here but cannot find
now. . .

Jarrod said that one can talk to this unit with Command Fusion over
the network. (It has an ethernet port)
Someone asked about network commands not too long ago and you
suggested a firefox plugin/addon I think for looking at headers. Could
anyone please clarify?
I am assuming we need to encapsulate each command with HTML data and
the tool above gives the relevant HTML info is this correct?

Here is what the onkyo protocol says about the network:
http://www.vandermehrn.com/lc/onkyo/

I would like to keep the Denon on the serial port if I can and use the
network for the Onkyo.
Any feedback would be appreciated.

Regards
Nahshon

Jarrod Bell

unread,
Apr 7, 2010, 11:37:04 AM4/7/10
to CommandFusion
I believe the Onkyo ethernet protocol is identical to the RS232
protocol, plus some wrapper bytes.

See this post on the group:
http://groups.google.com/group/commandfusion/browse_thread/thread/f7b0c8102b329d3/fa33e954003f06e0?hl=en&lnk=gst&q=onkyo#fa33e954003f06e0

So no need to do anything with HTML data.

Jarrod

Fiasco

unread,
Apr 7, 2010, 11:54:06 AM4/7/10
to CommandFusion

I could be wrong but can't the onkyo handle only one connection at a
time? I also remembering reading about an issue where a improperly
terminated session can block control.


On Apr 7, 10:37 am, Jarrod Bell <jar...@guilink.com> wrote:
> I believe the Onkyo ethernet protocol is identical to the RS232
> protocol, plus some wrapper bytes.
>

> See this post on the group:http://groups.google.com/group/commandfusion/browse_thread/thread/f7b...

Nahshon Williams

unread,
Apr 7, 2010, 2:13:12 PM4/7/10
to comman...@googlegroups.com
Fiasco,
Yes according to this document (bottom)

http://www.vandermehrn.com/lc/onkyo/

only one connection is allowed at a time (the same is true for RS232 on
a GC100-12 so I have nothing to lose)
As for the blocking control and session termination, I am not sure. This
is my first network onkyo.

Fiasco

unread,
Apr 7, 2010, 2:18:19 PM4/7/10
to CommandFusion
GlobalCache has an iTach w/ serial that can handle 8 sessions at once.

I have an Onkyo 875 connected via a GUC-232A serial->USB cable which I
use
for control via eventghost running on a PC.

I have a GC100 unit in my bedroom for control of the TV/stereo there
and the one connection
limit is a pain in the rear.

> >>> Nahshon- Hide quoted text -
>
> - Show quoted text -

Jarrod Bell

unread,
Apr 8, 2010, 1:48:40 AM4/8/10
to CommandFusion
The iTach RS232 ports still only allow one connection at a time. They
are working on a firmware update to allow multiple connections to a
single RS232 port however, so keep an eye out on their site for it.

Jarrod

Fiasco

unread,
Apr 8, 2010, 9:38:54 AM4/8/10
to CommandFusion
Do you know if they will update the firmware on the GC100 units as
well?

> > > - Show quoted text -- Hide quoted text -

Jarrod Bell

unread,
Apr 8, 2010, 10:51:09 PM4/8/10
to CommandFusion
I dont believe so, sounds like the actual GC-100 hardware was not
capable of these features, so no firmware upgrade will help.

Jarrod

Nahshon Williams

unread,
Apr 20, 2010, 7:21:36 PM4/20/10
to comman...@googlegroups.com
I can confirm that the correct format for the Onkyo network packet is
exactly as specified in Jarrod's link below.
The commands are instantaneous (compared to the GC100-12). Very fast!
Fiasco there have been no drop outs but I have not tried feedback yet.
Very stable connection. Thanks for the recommendation of Onkyo. They
have toggle commands!

Now time for the regex :-(

That is the Power On command.
ISCP\x00\x00\x00\x10\x00\x00\x00\x08\x01\x00\x00\x00!1PWR01\x0D
I am only interested in the "!1PWR01\x0D"

The !1PWR and 01 change independently. (based on the command).
The last part of the command varies in length.

This is the Volume Up command.
ISCP\x00\x00\x00\x10\x00\x00\x00\x08\x01\x00\x00\x00!1MVLUP\x0D
As above I am only interested in the "!1MVLUP\x0D" (here there are no
numbers but letters).

Please see structure here: http://www.vandermehrn.com/lc/onkyo
Do I need to account for the "\x" in the regex?

Nahshon
--
You received this message because you are subscribed to the Google Groups "CommandFusion" group.
To post to this group, send email to comman...@googlegroups.com.
To unsubscribe from this group, send email to commandfusio...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/commandfusion?hl=en.

Jarrod Bell

unread,
Apr 20, 2010, 8:07:02 PM4/20/10
to CommandFusion
HI Nahshon,

You say those are the commands, but are they also what gets replied
for feedback parsing?

If so, you could use a feedback regex of something like:
ISCP.*!1PWR0(1)\x0D

That will capture the power value (0 or 1) which you can then assign
to a digital join via capture group.

In regex, hex characters are also defined as \xFF format. Regex tester
however will not work if you enter test data in \xFF format (the regex
tester will read that as 4 characters, rather than the byte FF).
So for testing in the regex tester, try setting the regex up like so:
ISCP.*!1PWR(01)\\x0D
Note the two backslashes in front of the hex data. This will make the
regex tester work, but when you define the final regex in System
Manager, remember to take out the additional backslash.

Jarrod

Nahshon Williams

unread,
Apr 21, 2010, 10:21:02 PM4/21/10
to comman...@googlegroups.com
Thanks Jarrod,
Complete oversight on my part, yes the response is the same as the command.
I tried your regex in the tester but it did not give a capture for the
following:

Regex: ISCP.*!1PWR(01)\\x0D
Test data: ISCP\x00\x00\x00\x10\x00\x00\x00\x08\x01\x00\x00\x00!1PWR01\x0D

Also attempted to get a guage working. (no luck yet on the onkyo)
however this works in the Regex tester.
Regex: ^ISCP.*!1MVL(\d*)\\x0D$ (yes I remembered to remove spare slash)
Test Data: ISCP\x00\x00\x00\x10\x00\x00\x00\x08\x01\x00\x00\x00!1MVL45\x0D

Tomorrow I will try .*!PWR(01).* (ignore both sides of the data) for
testing what do you think?
Should I use the hex tick box now? (in feedback manager?)

Nahshon

Jarrod Bell

unread,
Apr 22, 2010, 12:02:55 AM4/22/10
to CommandFusion
I just tried the first regex that you said didnt work, but it worked
perfectly for me in the regex tester.
But you want to also capture when the power is off, so you should use
this regex:
ISCP.*!1PWR0(.)\x0D

I suggest only entering exact data in regex when you need to (ie. if
you have two similar data strings you need to separately match).
There is no point ensuring that all those null bytes and header data
match. Just match the important stuff:
.*!1PWR0(.).*
(note in your message you left out the 1 after the exclamation mark)

Hex tick box should only be used when you are matching data that comes
in as hex bytes (eg. from \x00 to \xFF), and you want to assign it to
a numeric value (such as a gauge ranging from 0 to 255).

Also make sure you have the EOM character defined as \x0D in the
system properties. This will force incoming messages to be separated
by the \x0D character if a few messages come in really quickly.
This ensures each message is separately run through the feedback
parsing engine.

Jarrod
Reply all
Reply to author
Forward
0 new messages