dCS 955 Serial problems

adys

Hi all

I am stuck for a few days with D/A convertor controlling.

It looks very simple, but from some reason it does not work

I tired everything I know to control it, with no succes...

I checked the cables, the port, I connected the computer to the unit to get responde, send strings via "control a Device" from Netlinx studio - nothing works...
The unit is not reponding in any way, not even a single byte back to me (and I asked it nicely)


The unit have rs232 address "01"

and the command I send is "1,114,1,0,0"
like this: send_string dvDCS955, "1,114,1,0,0"

The commnad is RS_REF_MODE to set the reference input to AES_1
Its 114 in the table in page 85



The baud rate is 1200, and I declare it as :
SEND_COMMAND dvDCS955,'SET BAUD 1200,N,8,1 485 Disable'


here is the protocol, its starts at page 77.

http://www.dcsltd.co.uk/manuals_pro/955manual.pdf

If someone can help I will be very thankfull, and I promise to bless him



Thanks

Ady

Marc Scheibein

The SEND_STRING itself looks good...

Where in your code do you define the Baudrate? This should be done in the DATA_EVENT[] of the device, like:

DEFINE_EVENT
DATA_EVENT[dvDCS955]
{
ONLINE:
{
SEND_COMMAND dvDCS,'SET BAUD 1200,N,8,1 485 DISABLE'
SEND_COMMAND dvDCS,'HSOFF' // hardware handshake off if not required by the unit
}
}

You should not use a fully wired cable, only wire the required lines 'cause of the non-standard pinout of the 9-pin male connector of AMX.

adys

Thank Mark

Yes its in my online
And we are using 3 wire cable (2,3,5) (straight cable BTW)

ericmedley

Does switching the device manually produce any string back to the AMX serial port (yellow light)?

Assuming that the device volunteers feedback, then you might try switching the TX and RX lines. Once you get the yello led flashing, check to see what the string coming in looks like. If it makes sense, then you've got the right baud rate.

this is a favorite topic of mine with the newer techs around here. They are very interested in getting the connection right the first time. I tell them that as far as rs-232 is concerned you've got a 50/50 chance of hitting it right. Some manufacturers say that thier 'RX' means 'My device recieves here' others mean 'put your device's RX in here. or in other words, what I mark as 'RX' is really my 'TX'.

I tell them, hook it up. If it doesn't work, flop the RX and TX. If it still doesn't work, call me.

good luck!

adys

no

This device is not sending nothing as output...

And I tried to croos the cable too, and nada.

But I see the yellow blink with the red
but listening on the port with netlinx studio bring nothing.

What does it mean?

Ok - update
I called support - guess what?

The manual is not up to date

The baud should be 4800
and the command needs to be 113 ( I don't have it in the manual at all)

and now I get back some [168] value respnse, but the device does nothing....

update 2:

the command working only when there is a signal on the audio input...!

So now thanks to the support its working

Jimweir192

Have you tried using the global address instead $F0?

Jimweir192

Yellow & Red activity suggests either a fast response byte or a cable short... either way you should be able to see the return string...

Have you got the original software? I often use an app called PortMon to sniff the strings to&from devices, very useful...

adys

Thanks, its solved. look at my update in my previus reply.

Good to know about PortMon , I will check it.