I am having trouble changing the baud rate on Ser0 on a PAC-S2 controller. I was under the impression from all the documentation that all 4 ports on the PAC-S2 could be either RS232 or RS485 and any combination of other comms settings I choose. For some reason, despite trying all the usual methods the port seems stuck on 19200bps.
For my application I was intending to use Ser0 and Ser1 on the S2 both as RS485 @38400bps for some modbus channels.
Using code I have already developed and tested successfully on my other PAC-R1 systems (some use SCM-485 modules, some use the PAC-R1 dedicated port ser0 with a RS485/RS232 converter) I have made what I believe are the necessary changes to the Communications Handle definition in the strategy. For this I have tried both methods appropriate for onboard controller serial ports:
Format 1: “ser:0,38400,n,8,1” and
Format 2: “ser:port=0,baud=38400,parity=n,data=8,stop=1” etc
The appropriate RS485 termination and bias settings were configured and PPP switched off in PAC Manager as usual. The RS485 side of things seems to be working fine also.
Despite doing this, when I start the chart and it spits out data, it is always set at 19200bps which I have been monitoring on Putty, RealTerm and a Modbus Slave emulator I am using. There is no doubt it is 19200. The runtime “inspect” window of the comms handle shows it is holding the config string as listed above.
As a sanity check I tried swapping over to using the other native S2 serial ports. All 3 other ports ser1, ser2, ser3 work as expected and accept the 38400bps setting and dish out data at 38400.
Has anyone else had this issue? Am I missing something in the documentation that says that there is something special about PAC-S2 ser0 or that it can only be 19200? Yes, I could always just push on and use ser2 and ser3 for the RS485 modbus channels but I feel there is something minor I haven’t caught here and someone out there can enlighten me.
Thanks in advance.