Author Topic: Russound RNET Plugin v1.4  (Read 29333 times)

Offline kabdalla

  • Jr. Member
  • **
  • Posts: 85
  • Karma: +0/-0
Re: Russound RNET Plugin
« Reply #15 on: July 30, 2013, 11:57:33 pm »
Give this I_RNET.xml file a shot for the MCA devices.  I essentially guessed at the structure for the request status command and left the parsing of the reply from the controller as is since neither of those commands are listed in the MCA doc.

Offline big517

  • Hero Member
  • *****
  • Posts: 576
  • Karma: +1/-3
Re: Russound RNET Plugin
« Reply #16 on: July 31, 2013, 08:52:04 am »
Sure, i'll gladly give it another run! 
Are you noticing a lot of differences from the RNET doc I sent?  Were you working off an older doc originally?


UPDATE:

All Off worked.
Specific Zone ON did not seem to work, but making a volume adjust does, and will turn the zone on.

Too early to test extensively without waking up the baby ;)

Noticed this FULL BUFFER message in the log;
Code: [Select]
luup_log:596: Received full buffer from controller via serial F0 01 00 70 00 00 7F 00 00 04 02 00 00 07 00 00 01 00 0C 00 00 02 11 0A 0E 01 0A 00 01 00 00 00 51 F7 <0x2faa4680>
50 07/31/13 9:08:19.389 luup_log:596: Received full buffer from controller via serial F0 01 00 70 00 00 7F 00 00 04 02 00 00 07 00 00 01 00 0C 00 00 02 11 0A 0E 01 0A 00 01 00 00 00 51 F7 <0x2faa4680>
50 07/31/13 9:08:20.440 luup_log:596: Received full buffer from controller via serial F0 01 00 70 00 00 7F 00 00 04 02 00 00 07 00 00 01 00 0C 00 00 02 11 0A 0E 01 0A 00 01 00 00 00 51 F7 <0x2faa4680>
50 07/31/13 9:08:21.598 luup_log:596: Received full buffer from controller via serial F0 02 00 70 00 00 7F 00 00 04 02 00 00 07 00 00 01 00 0C 00 00 02 11 0A 0E 01 0A 00 01 00 00 00 52 F7 <0x2faa4680>
50 07/31/13 9:08:22.597 luup_log:596: Received full buffer from controller via serial F0 02 00 70 00 00 7F 00 00 04 02 00 00 07 00 00 01 00 0C 00 00 02 11 0A 0E 01 0A 00 01 00 00 00 52 F7 <0x2faa4680>
50 07/31/13 9:08:23.101 luup_log:596: Request returned in 0ms <0x2e663680>
50 07/31/13 9:08:23.102 luup_log:596: Request returned in 0ms <0x2e663680>
50 07/31/13 9:08:23.103 luup_log:596: Request returned in 0ms <0x2e663680>
50 07/31/13 9:08:23.192 luup_log:596: Received full buffer from controller via serial F0 00 01 71 00 00 7F 00 00 04 02 00 00 06 00 00 01 00 01 00 00 04 F7 <0x2faa4680>

« Last Edit: July 31, 2013, 09:09:31 am by big517 »

Offline big517

  • Hero Member
  • *****
  • Posts: 576
  • Karma: +1/-3
Re: Russound RNET Plugin
« Reply #17 on: July 31, 2013, 09:39:39 am »
Pause Play Stop work as well.

Source Selection does NOT work with the exception of Source1 (RADIO). 

Offline kabdalla

  • Jr. Member
  • **
  • Posts: 85
  • Karma: +0/-0
Re: Russound RNET Plugin
« Reply #18 on: July 31, 2013, 10:09:13 am »
That's what I get for trying this so late last night.  This should fix zone power and source.  Let me know how it handles the status (is the correct power on/off button staying lit? does the correct zone button stay lit?)

And to answer your questions, there are two sets of the RNET implementation for controllers apparently, one for CA-series (CAM, CAV, CAA, CAS) which is what my plugin supports, and another set for C-Series (MCA).  The biggest difference is the location of the byte which specifies which zone you're sending the command for.  And what I missed in the first MCA-specific file I sent you yesterday, is for zone power and source there are two bytes in the string that specify it, I only caught one (which is what the CA-series implementation uses).

The gaps in the MCA RNET protocol document is there is no description of what string to send for status request, and no description of what the controller should return.  On the files I'm sending you, I'm just guessing on those based on the structure of the commands they do detail.
« Last Edit: July 31, 2013, 10:17:57 am by kabdalla »

Offline S-F

  • Hero Member
  • *****
  • Posts: 1247
  • Karma: +61/-12
  • Clueless N00b
Re: Russound RNET Plugin
« Reply #19 on: July 31, 2013, 10:27:37 am »
The suspense is killing me! My CAA66 came yesterday and it's DOA! 
My forum account was apparently hacked by a leprechaun. And he's drunk all of the time. If a post of mine seems a little off kilter, it's probably because he made it.

Offline big517

  • Hero Member
  • *****
  • Posts: 576
  • Karma: +1/-3
Re: Russound RNET Plugin
« Reply #20 on: July 31, 2013, 10:33:14 am »
Trying Now.

@S-F  that sucks!!!   Did you buy it off eBay, or new?

Offline big517

  • Hero Member
  • *****
  • Posts: 576
  • Karma: +1/-3
Re: Russound RNET Plugin
« Reply #21 on: July 31, 2013, 10:52:14 am »
POWER ON/OFF Works from within the device, but not on the front page for some reason.

Still a problem with Source Selection.  Can only choose Radio, and then everything locks up.  Have to delete plugin again.

Also want to note it's constantly polling the device, and choking the system.  Take a look at system log.
Maybe reduce the polling to every 2 minutes, or have an option to not poll automatically

Code: [Select]
Mem Available85912kilo bytes
CPU Load (1 minute)1.34
CPU Load (5 minute)1.09
CPU Load (15 minute)0.82
« Last Edit: July 31, 2013, 10:56:14 am by big517 »

Offline kabdalla

  • Jr. Member
  • **
  • Posts: 85
  • Karma: +0/-0
Re: Russound RNET Plugin
« Reply #22 on: July 31, 2013, 11:14:57 am »
@S-F: That does suck, sorry to hear that.

@big517:
That is really strange since those two power buttons map to the exact same action...there should be no difference between them at all.

As for the CPU issues, my guess is what the plugin is sending to the controller requesting status is what is causing the CPU issue as my CPU doesn't get below 80% idle (0.11 0.20 0.22).  It's probably completely wrong for that implementation of RNET and it's processing a bunch of junk coming back.  You can likely alleviate that issue by commenting out all the status request commands but then, obviously, you'll get no status.  If you can find the proper commands and responses for that implementation of RNET (or ask Russound for them), I'm happy to make the change.

I'm baffled by the source issues.  Only thing I can think of here is that this implementation now has two controller bytes, one for "controller" and one for "source controller".  This isn't the case in the CA-series implementation (only one controller byte) and there is no description I can find for what "source controller" is.  If you ping Russound support, ask for these descriptions, too.
« Last Edit: July 31, 2013, 11:21:17 am by kabdalla »

Offline big517

  • Hero Member
  • *****
  • Posts: 576
  • Karma: +1/-3
Re: Russound RNET Plugin
« Reply #23 on: July 31, 2013, 11:28:49 am »
Was that information not contained in one of the documents I posted?  Maybe in the Zip file?

Offline kabdalla

  • Jr. Member
  • **
  • Posts: 85
  • Karma: +0/-0
Re: Russound RNET Plugin
« Reply #24 on: July 31, 2013, 11:40:40 am »
It isn't included for the C-series implementation of RNET.  The two documents that reference it are:

Russound_Controllers_Protocol_v1_00_04.pdf
Reading RNET V1_00_03.pdf

Both of which apply to the CA-series implementation (and what I used to develop my plugin).  The C-series implementation appears to be RNET V1_00_07 based on that command document provided here (Russound RS232 hex codes v1_00_7.pdf).

If you can get a Russound_Controllers_Protocol_v1_00_07.pdf document, that is what I need.

Offline big517

  • Hero Member
  • *****
  • Posts: 576
  • Karma: +1/-3
Re: Russound RNET Plugin
« Reply #25 on: July 31, 2013, 12:35:08 pm »
Reaching out to Russound now.

Offline legend99

  • Full Member
  • ***
  • Posts: 151
  • Karma: +1/-0
Re: Russound RNET Plugin
« Reply #26 on: July 31, 2013, 03:51:38 pm »
Thanks Kabdalla!   ;D

Offline big517

  • Hero Member
  • *****
  • Posts: 576
  • Karma: +1/-3
Re: Russound RNET Plugin
« Reply #27 on: July 31, 2013, 04:18:10 pm »

Offline kabdalla

  • Jr. Member
  • **
  • Posts: 85
  • Karma: +0/-0
Re: Russound RNET Plugin
« Reply #28 on: July 31, 2013, 04:27:26 pm »
I wish I had good news but it looks like the only thing added/updated is the RIO command string list.

Offline big517

  • Hero Member
  • *****
  • Posts: 576
  • Karma: +1/-3
Re: Russound RNET Plugin
« Reply #29 on: July 31, 2013, 04:42:40 pm »
Quote
If you can get a Russound_Controllers_Protocol_v1_00_07.pdf document, that is what I need.

So that RNET Serial Hex 1_00_07.pdf is NOT helpful then?