Our full technical support staff does not monitor this forum. If you need assistance from a member of our staff, please submit your question from the Ask a Question page.


Log in or register to post/reply in the forum.

RS422 communication between a CR1000 and CR216


AMuchembled May 6, 2014 09:10 AM

I want to make a RS422 communication between a CR1000 and CR216 according to the diagram below :
PC(Loggernet) -> (RS232)CR1000(COM1) -> REDLION ICM5 (RS232/RS422) -> REDLION ICM5 (RS422/RS232) -> (RS232)CR216

RS485 modules are not Campbell modules (MD485), but Red Lion ICM5 modules.
I tested two RS422 modules to ensure their proper functioning me.

Connection to the PC and CR1000 to RS422 modules :OK
PC(Loggernet) -> REDLION ICM5 (RS232/RS422) -> REDLION ICM5 (RS422/RS232) -> (RS232)CR1000

Connection to the PC and CR216 to RS422 modules :OK
PC(Loggernet) -> REDLION ICM5 (RS232/RS422) -> REDLION ICM5 (RS422/RS232) -> (RS232)CR216

Connection with the CR1000 to CR216 : OK
PC(Loggernet) -> (RS232)CR1000(COM1) -> (RS232)CR216

Then I uses the software NETWORKPLANNER to configure the two datalogger after the first pattern and LoggerNet to connect.
It is impossible for me to connect to the central CR216. Configuration RS485 modules must not be identical.
Can anyone inform me, thank you.


EarlyBird May 6, 2014 09:41 AM

The MD485 as its name implies is a multi drop system and requires one MD485 at the PC(Base) and one for each logger.

The only reason for using RS422/485, that I can think of, is to extend the cable length from say 20m to 1000m. As your CR1000 is next to your PC connected by RS232 there is no need for RS422/485 to be used for this logger. Using your existing Redlion units connect to the CR216 and use a RS232 cable on another com port on your PC to connect to the CR1000. Or buy another Redlion and follow the MD485 layout. Here is the link.

http://s.campbellsci.com/documents/eu/manuals/md485.pdf

You could also make the CR1000 a 485 recorder and the CR216 a 485 sensor. But that is another can of worms! as we say.


AMuchembled May 6, 2014 02:28 PM

I solved my problem.
Communication works.
After several checks and I realized that the RS232 connection of COM1 was incorrect.
Thank you.

Log in or register to post/reply in the forum.