Reciever and DM.

[farbs]

OK.
I have G5 up and running and all is well.
It is setup the same way as G4 was as far as the plugins and serial control.
So I have included the Lua that I am using for it and the link to the protocol.
I would like to get feedback if possible so I can have an On and off state and possibly what input it is switched to.

and a link to the rotel protocols.
The model I have is the RSX 1056
http://europe.rotel.com/downloads/rs232-protocols.htm

[Agonostis]

I just got an RSX 1057. The commands appear identical except for different Device ID.

I would love to help test anything made here.

[farbs]

just a little reminder;)

[Promixis]

we have added a new transport system to G5, and need to finish it up first. then we will help you get this working with that.

[farbs]

OK, thanks:)

[farbs]

Thought i would just ask how the new transport is going and if it is ready:)

[Rob H]

It's definitely getting there.

I'm going to port my Denon and LGTV plugins to it soon to get a better feel for what's needed from a superclass

[farbs]

Possible to help out with this one yet to get going with the DM?

[Rob H]

We're still working out the kinks

[Francois]

OK.
I have G5 up and running and all is well.
It is setup the same way as G4 was as far as the plugins and serial control.
So I have included the Lua that I am using for it and the link to the protocol.
I would like to get feedback if possible so I can have an On and off state and possibly what input it is switched to.

and a link to the rotel protocols.
The model I have is the RSX 1056
http://europe.rotel.com/downloads/rs232-protocols.htm

Not sure if this is what you're looking for, but I'm able to use the G4 scripts I've posted for my RSX 1055 with G5 (I see quite a few serial communication errors as reported in another thread, but it does work fine nevertheless). If you look into these scripts, you should be able to adapt them to other Rotel receivers.

Eiffel

[farbs]

Thanks, but the rotel is working really well. I just wanted to take advantage of the new Device manager (as I have set up G5 the same way I had it set up in G4) and get feedback to net remote so you know what state the amp is in.

[farbs]

Hi guys, any closer to having having a look at this one?
Also with the latest build I seem to be having some intermittent issues with the receiver just not responding sometimes. The only way to fix is to manually turn the unit off or on, then all the queued commands execute and it works again??
Are you able to take a quick look at the file?

[Rob H]

That mostly looks okay, but you shouldn't have IncompleteResponseTimeout and NoResponseTimeout set to the same value. NoResponseTimeout should always be larger than IncompleteResponseTimeout, e.g. 200 in your case.

[farbs]

Hi,
Sorry to be pain but the receiver is still doing the same thing.
Also would like to get all the devices over to the device manager but don't know where to start?:confused:

[rpalmer68]

Hi,
Sorry to be pain but the receiver is still doing the same thing.
Also would like to get all the devices over to the device manager but don't know where to start?:confused:

Exactly what I've been doing! And yes it is hard to work out where to start.

Have at look at my Meridian threads, these might help you at least get things started, then RobH is a wealth of information from there!

My files, I've tried to keep tham as simple as possible!
http://www.promixis.com/forums/showthread.php?p=112792#post112792

Discussions/questions/problems along the way
http://www.promixis.com/forums/showthread.php?p=109202#post109202

Happy to help if I can, but I'm certainly no expert in this areas yet!

Good luck
Richard

[Rob H]

Hi,
Sorry to be pain but the receiver is still doing the same thing.

Try increasing the NoResponseTimeout a bit more - e.g. to 1000.

Is it just certain commands that don't get a response? Or does it seem to be random? On some devices you only get a response if the command you issue actually makes a change e.g. if you change the input source to the one that the receiver already has selected then you may get no response.


Also would like to get all the devices over to the device manager but don't know where to start?:confused:
Let's get the serial device working first, then we can see about a provider. And, as Richard says, the Meridian threads should prove useful.

[rpalmer68]

farbs,

Does it happen when you send more than one command to the receiver quickly (like from a macro) or will just a single comand lock things up?


Richard

[farbs]

OK I've been playing around a bit noticed that if you send the receiver a command twice like off and then off again then it stops working. The main command that does it is off, the others seem a bit more sporadic. Strange thing is it was working fine until the upgrade to ver515.? Ive increased The noresponse timeout to 1000 also but didn't really help much.

[rpalmer68]

OK I've been playing around a bit noticed that if you send the receiver a command twice like off and then off again then it stops working. The main command that does it is off, the others seem a bit more sporadic. Strange thing is it was working fine until the upgrade to ver515.? Ive increased The noresponse timeout to 1000 also but didn't really help much.

Does it happen if the two commands are sent a few seconds apart or only if the 2nd is sent immediately after the 1st?

R

[farbs]

The timing between the 2 commands don't make any difference? So it could be a second or 10 minutes.
It has really got me this one. Usually I end up figuringout but this has got me stumped. Also My other 2 serial plugins are working fine (Plasma TV And DVD Player)

[Ron]

What version did you upgrade from?

[farbs]

From 514 previously 513 and before that 510

[Ron]

and 514 was working for you?

[farbs]

When I upgraded from 514 I had lotsa problems like nothing showing up in component list so I dine a completely fresh install and plugged everything back in and that's when the problems started.

Serial: Rotel 1056 : Simple Receive: Data 05 10 02 1A .... Code: 1
Serial: Rotel 1056 : Simple Receive: Data 05 10 08 20 ... Code: 1
Serial: Rotel 1056 : Simple Receive: Data C5 20 4F 50 54 55 53 20 20 20 20 20 34 35 20 00 00 00 00 00 18 00 00 D8 Å OPTUS 45 ........Ø Code: 1
Serial: Rotel 1056 : Simple Receive: Data C5 20 4F 50 54 55 53 20 20 20 20 20 34 35 20 00 00 00 00 10 18 00 E4 CC Å OPTUS 45 .......äÌ Code: 1
Serial: Rotel 1056 : Simple Receive: Data 05 10 02 1A .... Code: 1
Serial: Rotel 1056 : Simple Receive: Data 05 10 03 1B .... Code: 1
Serial: Rotel 1056 : Simple Receive: Data C5 20 4F 50 54 55 53 20 20 20 20 20 34 35 20 00 00 00 00 10 08 00 E4 BC Å OPTUS 45 .......ä¼ Code: 1
Serial: Rotel 1056 : Command queued: 10 4B 23 .K# at postion 1
Serial: Rotel 1056 : Simple Send: FE 03 C5 10 4B 23 þ.Å.K#
Timer (pcall): ...Files\Promixis\Girder5\/plugins/serial/Rotel RVR.lua:63: bad argument #1 to `sub' (string expected, got nil)
stack traceback:
[C]: in function `sub'
...Files\Promixis\Girder5\/plugins/serial/Rotel RVR.lua:63: in function `ReceiveResponse'
...gram Files\Promixis\Girder5\/plugins/serial/init.lua:338: in function <...gram Files\Promixis\Girder5\/plugins/serial/init.lua:333>
Serial: Rotel 1056 : Command queued: 10 4B 23 .K# at postion 1
Serial: Rotel 1056 : Response pending, que size 1
Serial: Rotel 1056 : Command queued: 10 4A 22 .J" at postion 2
Serial: Rotel 1056 : Response pending, que size 2
Serial: Rotel 1056 : Command queued: 10 4A 22 .J" at postion 3
Serial: Rotel 1056 : Response pending, que size 3


I've posted some files if this helps from when it stops working

[Ron]

Okay, nothing changed on the C++ side there, so the change must have been on the scripting or physical side.

[farbs]

Also I didn't make any changes to the lua files that I put back in the plugins/serial folder. And also the the other two are working OK.

[Rob H]

Ah, I see what the problem is with the string.sub - you're not checking the value of the code parameter.

ReceiveResponse = function (self, data, code)

if math.band(code, serial.RXCHAR) > 0 then
fchar = serial.bytetohex (string.sub (data,1,1)) -- get the first char of the receive

if fchar == "C5" then -- valid receives start with C5

volume = ""
input = ""
raw_command = tostring(data)
volume = string.sub(raw_command,21,22)
input = string.sub(raw_command,2,9)
gir.TriggerEvent("rotelosd",18)

end
end
serial.Classes.Queued.ReceiveResponse (self,data,code)

end,

[farbs]

Well once again Thankyou! as that has done the trick!:)
Now to get everything moved to the DM (and start all over again)

[farbs]

OK guys, thought I would bring this back out and ask for some help in getting my equip over to the DM. Where do I start? The lua files and protocol are at the start of the thread. Also would like to have feedback for net remote as in states.
Thanks in advnce:)