Serial Port help

For the life of me I cannot get the serial communications in Logic to work either on the unit itself or in simulation mode on the PC.

I can't event get logic to do this basic step:

Code:

OpenSerial(1,1,9600,8,1,0,0);
WriteSerial('UK001'#13);
CloseSerial(1);

The unit (Paradox alarm panel PRT3) is connected to my laptop on COM1 via USB Serial Adapter and i can manually send the UK001 command via a terminal and it will respond as intended.

I am so confused as to why this simply wont work from logic.

 

From the tinkering I have done with serial, you need to add the magic line

Code:

waitUntil(clientSocketConnected(1));

 

The write doesn't wait until it's done, so when you close the port straight away it will cancel the write in progress.

Open the port in the initialization section. You don't need to close it.

You don't need to wait after you open the port as it happens straight away (unlike TCP connections that take time). The waitUntilCLientSocketConnected is for tcp connections only, not serial.

 

You might find the code here helpful

http://www.cbusforums.com/forums/showthread.php?t=4314&page=2

 

I read that and modified the handler to work on serial cheers.

Works like a treat in a PAC but i think the rs-232 port on my spectrum is cooked.

I cannot get it to output a single byte. From the 3.5mm jack, when plugged into the PC via USB-> serial i can interact perfectly with the PRT3 module.

Connected to the spectrum does nothing at all. Screen is only a year old.

 

I have checked it many times as I do alot of serial comms work with PLCs. It is a very easy mistake to make. However, I have proven that the cable installed works as I can use a 3.5mm gender bender to allow me to plug an rs232 -> 3.5mm stereo jack into it and using putty and hyperterminal I am able to send and receive commands from the PRT3 module.

When it is plugged into the spectrum, I get nothing. I have even changed the spectrum from master to slave, tried changing the Tx/Rx lines in both master and slave mode and still get nothing.

 

Yeah, I have found the RS232 transcevers or ect or something is bad in the Spectrums, I have had more than one unit where the serial doesn't work out of the box, some of them are fine some of them just arn't. This is using the 'official' serial cable too.

 

What a bugger. You'd think on ~$1000+ piece of hardware a simple RS232 transceiver would be bullet proof.

I have a few TCP RS232 modules kicking around so I will use one of those and run the code from the wiser instead now I guess.

 

I might book a time with Keenan at Schneider Brisbane and get him to verify that my port is buggered and if that's the case, I'll get it swapped under warranty and try again with the new one.

 

It is one of those things I guess, as a design person myself I feel your pain, at the end of the day, if it doesn't get captured under the warranty process then it is likely to get lost. Unfortunately this does depend on a lot of people in the middle, like the wholesaler and the Schneider/Clipsal Warehouse ect.