Is this the proper syntax for a communication handle where a S1 controller is the main controller that is talking to a groovEpic PR1 used as just a brain to bring in serial communication from a scale using the GRV-CSERI-4 Module?
@WT_601A_TRAILER_1_SERIAL:baud=9600,parity=n,data=8,stop=1
I don’t think it is possible to use the CSERI module directly from another controller.
As a work around, enable Node-Red and install the node-red-contrib-serialport node and import the flow I have at this post:
You will need to configure the TCP port and serial port in the flow and open the TCP port you pick on the firewall of the EPIC.
This will allow you to create a TCP connection from the S1 to the EPIC which will relay the communication to the serial port.
We decided to handle the communications to the scale using Ethernet.
I have successfully tested the logic for this using a PR1 over the E1 port. Here is the communication handle. tcp:192.168.0.51:10001
The final configuration requires us to use an existing S1 controller. I have loaded the logic I used in the PR1 to the S1 and configured the E2 Ethernet port to be on the same network as the weight indicator. Using the same communication handle, I get an error when opening the communication port.
I suspect it has something to do with opening port 10001 in the firewall on the S1 but cannot find where that is done.
A reboot of the controller fixed it…odd but maybe I didn’t reboot after assigning the ENET2 port network settings.
When adding the secondary address on a PAC I am pretty sure you need to power cycle the controller. I don’t think a reboot (through PAC Manager) is enough. Glad you figured it out.
