No Response from Russound COntroller #1....HELP PLEASE

[mcu]

I have installed Girder 5 and trying to configure it to work, but all I get is Getting info from Russound, and then No Response from Russound Controller. This goes back and forth forever. I have downloaded the latest plugin 1.12 for Russound and still no luck

Please help!

[mcu]

anyone please???

[speedbump49]

I used the hyper terminal to confirm my serial cable and port was correct. If you have UNO keypad or Russound remote, just issue commands with it and monitor the line for readable text. See link below. Also, if you have any other software using the port, such as fax software, or old dialup stuff you will need to close them first. I also think you need a license now for russound plug-in, you should have 30 days to get it working after initial install. Check the license tab to see if Russound plug is enabled. If not email sales@promixis.com. Review this thread for other ideas:
http://www.promixis.com/forums/showthread.php?t=16641

Its working rock solid for me for some time now. Good luck!
-mw

[Rob H]

Oh, and what Russound do you have? I know the CAV6.6 is supported, but not sure about others.

[mcu]

i have the cav6.6

I can communicate with the russound using docklight, so I know my cable, port and russound are ok.

Any ideas?

Promixis Support, I don't mind buying your product, but I need the support to get this to work. So far, no one from promixis has even helped in a week.

PLEASE!

[Ron]

Are you seeing any errors? Do you have all other russound applications closed on that computer?

[mcu]

no errors, only the responses noted in the initial post. No other apps open.
I read some people say that its a license issue and others saying a version issue

please help

[Rob H]

How are you connecting to the RussSound? Are you sure you have the correct port selected?

Also, when you say there are no other errors, are you checking the Lua console?

[Manser]

Try to put this file into the folder \\Plugins\serial

[mcu]

I loded this and still get the same problem. Any other ideas? I can let you guys connect to the server via RDP or vnc if needed

[Rob H]

Did you see my post 3 messages up the thread?

[mcu]

I am sure cable and correct com port are set. even the correct front or back switch on the unit or else it would not work with docklight.

Below are the errors i saw in LUA console. Thank you very much for the help so far.


Serial: Russound RNET : ERROR: No response to last command
Recevied Message Type 5 F0 7E 00 7F 02 00 7F 05 02 01 00 02 01 00 C8 00 02 00 00 00 00 ~..................
Serial: Russound RNET : ERROR: No response to last command
Recevied Message Type 5 F0 7E 00 7F 02 00 7F 05 02 01 00 02 01 00 C8 00 02 00 00 00 00 ~..................
Serial: Russound RNET : ERROR: No response to last command
Recevied Message Type 5 F0 7E 00 7F 02 00 7F 05 02 01 00 02 01 00 C8 00 02 00 00 00 00 ~..................
Serial: Russound RNET : ERROR: No response to last command
Recevied Message Type 5 F0 7E 00 7F 02 00 7F 05 02 01 00 02 01 00 C8 00 02 00 00 00 00 ~..................
Recevied Message Type 5 F0 7E 00 7F 02 00 7F 05 02 01 00 02 01 00 C8 00 02 00 00 00 00 ~..................
Serial: Russound RNET : ERROR: No response to last command
Recevied Message Type 5 F0 7E 00 7F 02 00 7F 05 02 01 00 02 01 00 C8 00 02 00 00 00 00 ~..................
Serial: Russound RNET : ERROR: No response to last command
Recevied Message Type 5 F0 7E 00 7F 02 00 7F 05 02 01 00 02 01 00 C8 00 02 00 00 00 00 ~..................
Serial: Russound RNET : ERROR: No response to last command
Recevied Message Type 5 F0 7E 00 7F 02 00 7F 05 02 01 00 02 01 00 C8 00 02 00 00 00 00 ~..................
Serial: Russound RNET : ERROR: No response to last command
Recevied Message Type 5 F0 7E 00 7F 02 00 7F 05 02 01 00 02 01 00 C8 00 02 00 00 00 00 ~..................
Serial: Russound RNET : ERROR: No response to last command
Recevied Message Type 5 F0 7E 00 7F 02 00 7F 05 02 01 00 02 01 00 C8 00 02 00 00 00 00 ~..................
Serial: Russound RNET : ERROR: No response to last command
Recevied Message Type 5 F0 7E 00 7F 02 00 7F 05 02 01 00 02 01 00 C8 00 02 00 00 00 00 ~..................
Serial: Russound RNET : ERROR: No response to last command
Recevied Message Type 5 F0 7E 00 7F 02 00 7F 05 02 01 00 02 01 00 C8 00 02 00 00 00 00 ~..................
Serial: Russound RNET : ERROR: No response to last command
ScriptReset Start
Component Manager Shutdown Time 63.713963642716
ScriptReset Done Calling ScriptReset Callbacks, Time: 99.309828490019
Loaded LGTV Class
Loaded LGTV component
Russound RNET - WORK 1.2.2
Welcome to Promixis Girder 5.0.0 build 523
Recevied Message Type 5 F0 7E 00 7F 02 00 7F 05 02 01 00 02 01 00 C8 00 02 00 00 00 00 ~..................
Recevied Message Type 5 F0 7E 00 7F 02 00 7F 05 02 01 00 02 01 00 C8 00 02 00 00 00 00 ~..................
Recevied Message Type 5 F0 7E 00 7F 02 00 7F 05 02 01 00 02 01 00 C8 00 02 00 00 00 00 ~..................
Recevied Message Type 5 F0 7E 00 7F 02 00 7F 05 02 01 00 02 01 00 C8 00 02 00 00 00 00 ~..................

[mcu]

was just reading through russounds troubleshooting manual. It says there that I should be using null modem, but everywhere I read on the forums here suggest straight trough. Which one is it?

[Rob H]

Not really sure about the cable, however you're clearly receiving some data from the Russound (over and over again). It is an horrendous protocol though (and I'm not hugely impressed by the quality of the documentation, so I'm not entirely sure what that data means - my best guess is that this is an event from

Target Controller 7E (not sure what this means - not mentioned as a specidal value), Zone 0, Keypad 7F (the controller itself)

Source Controller 02, Zone 0, Keypad 7F (again the controller itself)

The message type is 5 ie an event

Beyond this point I get a bit confused - the bytes 02, 01, 00 seem to be an acknowledge message, but I'm not clear what it is acknowledging. Can you search for the line LogLevel = 4 in the file and change the 4 to 0 so I can see exactly what is being sent and returned.

I need to see the whole log from the time you start Girder up. I'd also suggest that you power down the RussSound. Unfortunately I don't have a Russsound here which makes this slightly tricky.

[mcu]

if you would be willing, i would let you login to my server using VNC and you can play around with it. Please PM me in private and send me your AIM, ICQ, Yahoo!IM or MSN and I will send you the user/pass

Thanks

[speedbump49]

To MCU, when was the last time you turned the CAV6.6 off and on?

[mcu]

i've tried to turn it off and on yesterday to see fif that would help at all

[speedbump49]

oh and how about rebooting the pc?

[mcu]

oh yes...i tried this also. did you use a null modem or straight cable for yours?

[mcu]

Anyone else please???

[mcu]

GUYS??? ANyone ?

[Rob H]

I've just seen this in the source :-


Status = {'7E','00','00','00','00','7F','05','02','01','00' ,'02','01','00','C8','00','00','00','##','00','00' }, -- undocumented PING, ## = on/off, ping is every 60 secoonds

This is not an exact match for the data you're seeing, but it looks fairly close - presumably one of your controllers (#2) is sending this?

I did ask you earlier to

Can you search for the line LogLevel = 4 in the file and change the 4 to 0 so I can see exactly what is being sent and returned.
but perhaps you missed that

Could you try it and post the log again?

[mcu]

Hey Rob

Thanks for the help, but you lost me there. Please check your PM for a sec

Thanks

[Rob H]

Here, try this version the Russound plugin - it goes in plugins\serial

[mcu]

ok i understood about going into the lua after i posted my last response. I change it from 4 to 0. My logs now look like this

Serial: Russound RNET : Command queued: F0 00 00 7F 00 00 70 01 04 02 00 00 07 00 00 7C .....p........| at postion 1
Serial: Russound RNET : Simple Send: F0 00 00 7F 00 00 70 01 04 02 00 00 07 00 00 7C F7 .....p........|
Serial: Russound RNET : RUSS EVENT Plugin nil nil Master 0 Waiting Getting info zone 1 on controller 1
Serial: Russound RNET : RUSS EVENT Plugin nil nil Master 0 No Response from Russound controller #1
Serial: Russound RNET : Simple Receive: Data Code: 0
Serial: Russound RNET : Simple Receive: Data 30 0 Code: 32768

[Rob H]

Does it do the same for all zones and controllers? Or does it keep trying controller #1 zone 1?

[mcu]

always zone 1 on controller1

[Rob H]

Okay, that seems to indicate that it doesn't think you have a controller #1 which is odd since I believe that's the CAV6.6 itself. Perhaps it's a configuration issue on the CAV? It looks as though you or your installer might have configured the controller in the CAV itself to have an id other than 1. This might have happened if it had been previously installed in a system with more than one RNET device.

See the manual in the section on Installer Programming

[mcu]

ok so i installed girder4 and guess what....everything works fine! I mean it gets a response and status is OK

whats going on with Girder 5?

[Ron]

I've ordered a new Russound for the office once that comes in we can help you more effectively.

[Rob H]

ok so i installed girder4 and guess what....everything works fine! I mean it gets a response and status is OK

whats going on with Girder 5?

That's very weird, I know that Mike (who wrote the Russound plugin) did it with G5 so we know it works there. The only major functional difference between G4 and G5 as far as serial plugins goes is that multicharacter terminators work differently - in G4 any the terminators are treated as a set but in G5 they're treated as a sequence ie if you had '\r\n' as a receive terminator then in G4 that would match either \r or \n but in G5 it will match only \r\n together.

One thing that might help is if you could install PortMon (http://www.microsoft.com/technet/sysinternals/processesandthreads/portmon.mspx) which will monitor serial port activity and monitor the port under both G4 and G5 and I can try to see what the differences are if you post the logs.

I can't remember if I asked you before, what's the serial hardware between your PC and the Russound? ie native serial port, USB-serial adapter etc.?