Grv-cseri-4 (rs232)

groov EPIC
1

Good day,

I am needing some assistance into a small challenge I am currently encountering.

I have connected a scale indicator (transmitting RS232) to the CSERI-4 (configured for RS232).

Configured all the connection strings and comm-handles and connected to the indicator.

When connected to the CSERI I receive a string as per string 1 image below, whole lot of random.
(Baud Rates and all parameters are correct, wiring is correct and routing works)
There are to versions of the scale indicators connected, a older model that transmits the same string as the newer model yet the older one works perfectly with the CSERI. Newer on I received non-sensical data. A below

string 1
string 1960×1280 324 KB

When I take the new version out of the CSERI-4 and connect it to a RS232 to USB convertor and place it in port 0 of the USB then I can can receive the sting correctly.

In the CSERI it does not work but through the convertor to USB it works perfectly. As per string 2

string 2
string 2960×1280 300 KB

I do not understand why the CSERI hardware cannot work with this scale vs connecting it through the USB convertor.

I would appreciate if anyone can provide some insight.

2

Have you configured the serial module in groov Manage?
You need to set the type of protocol you are expecting and save it before PAC Control strategy opens the comm handle. You only need to do it one time, but I wonder if that step got missed?

3

Hi Beno

Setup as below.
Manage

Its the most peculiar finding. With the port configured.

I plug in the older unit ,(RS232,9600,N,8,1) into port 1 - I get the string
I then plug the newer version, (RS232,9600,N,8,1), I get garbage

Change my commhandle to point to the usb and fit the convertor. Both units work through the convertor

Check on my laptop through the convertor, both units work, string is received.

Plug it back into the CSERI, older one gives sting and newer on garbage.

4

Tried various ports, moving the module to different slots, same results

5

What does your SetCommunicationsHandle function look like?

here is an example that I have where the name of the device in the IO module is called: Rs485_WN, and the communicationsHandle is called: chModbusMaster_EpicSlot3Ch3_WN

SetCommunicationHandleValue(“@Rs485_WN:baud=9600,parity=n,data=8,stop=1”, chModbusMaster_EpicSlot3Ch3_WN);

6

Hi,

“@Scale_Agg:baud=9600,parity=n,data=8,stop=1” for the CSERI

Regards

7

Ah. Thanks for the extra information, it sort of confirms what I suspected… its a hardware issue.

Your old unit is outputing RS232 as per the specification. Your new unit is not.
The USB to serial adapter is not built to specification so works with both.
The groov serial port is built to the specification.

This blog should make it clear:

tl;dr You will need a level converter for the new unit to bring its output up to the RS232 specification.

8

Beno, thankyou very much for the insight.

I suspected something like this but needed confirmation from someone with the necessary technical knowledge. Guess they make RS234 spec parts.

I appreciate the engagement

9

TTL (What I suspect your new unit is spitting out) to RS232 converters are common and cheep, well worth giving one or two a go before getting too deep in the rabbit hole.

You might need an oscilloscope to check the voltage swing as most multi-meters cant move that fast and give an accurate voltage.

We’d all appreciate it if you could stop back and update the thread with what you find and how you get it going.

10

Thankyou Beno.

I currently am running it through the USB port using the Gearmo RS232 to USB convertor.

Will use it like this for now and ultimately convince the end user to replace the scale devices with something better