Abstract:
This document describes connecting PM50 to Crimson 3.2 based devices over serial Rs485
Products: Graphite HMIs/Controllers, CR1000/CR3000 HMIs, Data Station Series.
Graphite HMIs/Controllers:
G07C0000/G07S000, G09C0000/G09C1000, G10C0000/G10S0000/G10C1000/G10S1000/G10R0000/G10R1000, G12C0000/G12C1100/G12S1100, G15C0000/G15C1100, GRAC0001
CR1000/CR3000 HMIs:
CR10000400000210, CR10000700000210, CR10001000000210, CR30000400000310, CR30000700000420, CR30001000000420, CR30001500000420
Data Stations:
DA10D0C000000000, DA30D0F000000000
Flex Edge Series:
DA50A0BNN0000020/DA50A0BNN0000030/DA50A1BNN0000030/DA50A0BNN0000040/DA50A1BNN0000030
DA70A0GNNNNNN020/DA70A0FNNNNNN020/DA70A0GNNNNNN030/DA70A0FNNNNNN030/DA70A1GNNNNNN030 DA70A1FNNNNNN030/DA70A0GNNNNNN040/DA70A0FNNNNNN040/DA70A1GNNNNNN040/DA70A1FNNNNNN040
Use Case:
Setup Connection between Crismon 3.2 based devices and PM50s using Modbus RTU or RedLion PM50Master Crimson communications drivers. This technical note explains how to map PM50's Count A variable to a Crimson tag for read/write and protocol conversion.
This technical note will be utilizing a data station DA10D as an example to communicate to the PM50 over Modbus RTU Rs485.
Required Software:
Crimson 3.2
Crimson 3.2 Device Rs485 Port to PM50 Wiring:
On any Crimson 3.2 devices for rs485 2-wire wiring requires any combination of TxA and TxB. Crimson 3.2 devices have two sets of TxA and TxB just FYI.
Below is the wiring diagram for Crimson 3.2 device's Rs485 2-wire connection to PM50.
Crimson 3.2 Device Pins ----------------------------------------- PM50 Device Pins
Pin 1 - TxB Pin 8 - B(Rs485-)
Pin 8 - TxA Pin 7 - A(Rs485+)
Pin 6 - Common Pin 9 - Common
Crimson 3.2 Configuration:
1. Open Crimson 3.2, select File then select New.
Select the model Crimson 3.2 based device, then select OK. In this example, we will be selecting a Data Station DA10D.
2. Once you select the model, Crimson will open to the first section on the left called Device Configuration.
- The device configuration is the section of Crimson where you can define the RedLion's network IP address via clicking on Ethernet 1 under Interfaces in the network tree.
Once you have configured the RedLion network if applicable, select the Communications section on the left-hand lower corner.
3. The communications section of Crimson 3.2 is where you can define the particular communications driver to talk to the PM50.
In the communication section, click on the Rs485 comms port, then look in the center window. Select Pick to pick a new driver to add to the Rs485 communications port. In this example we will go overusing the Modbus Universal Master driver and the RLC instrument PM50 Master driver.
Modbus RTU Universal Master Driver Setup:
Note: See further down on how to use the RLC Instrument PM50 Master driver instead
Once the Modbus Universal Master Driver is added on the Rs485 port, click on the Rs485 Communications port or Rs485 Mode for a DA10D, then look in the center window.
In the center window, leave the following settings unchanged
Driver Settings:
Protocol Type: Modbus RTU
RTU Framing: Detect Via Timing
Slave Timeout: 600ms
Move down further to configure the port settings. Make sure the Crimson based device and PM50 have the same Baud Rate, Data Bits, Stop Bits, and Parity Bits. Leave the port mode set to 2-wire Rs485.
Once the Rs485 port settings match the PM50, click on the device that shows up under the Rs485 comms port. In this example, the device is called PLC1. There are only two settings that needs to be changed here. Set the Drop Number to whatever the PM50 Node Address is set to. Below that, look for the setting called Ping Holding register and set that to 0.
Next, go to the Data Tags section on the left lower side as we are now ready to map PM50 registers to Crimson data tags for read/write.
Once in the Data Tags section look in the left-hand side Navigation pane and select the new option to create a new numeric Tag called Tag1.
Next click on Tag1 and you can rename data tags to something meaningful. In this example we are trying to read CountA out of the PM50, so we will name the tag CountA.
Once you rename your tag, look in the center window, under the Data tab, you will see the first option called Source. It will currently be set to internal. Click internal and a dropdown will appear. Find the device name that shows up under the Rs485 comms port in this example, its PLC1. Select the device to pull up a Modbus Register selection menu.
According to the PM50 product manual, CountA value is tied to Modbus Holding Register 400001 word as long 32-bit. This is the address we need to read in the Crimson device tied to the CountA tag.
In the Modbus Mapping window, select 04 Holding registers for the Data item and leave the element window set to 400001 as that is the register we need to read. Set the Data type to Word as Long since the PM50 is a long integer meaning 32bits. Select Ok.
Once the tag is mapped it will turn red color which means its set for read and write access. We are not ready to download this file to the Crimson 3.2 device and add a live watch on that newly mapped CountA tag.
RedLion PM50 Master Driver Setup:
Note: The setup process is the same, but the registers and mapping is now different.
In the communication section, click on the Rs485 comms port, then look in the center window. Select Pick to pick a new driver to add to the Rs485 communications port. In this example we will go overusing the Modbus Universal Master driver and the RedLion PM50 Master driver.
Select the RedLion PM50 Master driver, then hit OK.
Once the RedLion Master Driver is added on the Rs485 port, click on the Rs485 Communications port or Rs485 Mode for a DA10D, then look in the center window.
In the center window, make sure the driver settings match below:
Driver Settings:
Protocol Type: Modbus RTU
RTU Framing: Detect Via Timing
Slave Timeout: 600ms
Move down further to configure the port settings. Make sure the Crimson based device and PM50 have the same Baud Rate, Data Bits, Stop Bits, and Parity Bits. Leave the port mode set to 2-wire Rs485.
Once the Rs485 port settings match the PM50, click on the device that shows up under the Rs485 comms port. In this example, the device is called PM50_1.
Select the Model PM50 you will be utilizing. Then set the Station number to the PM50's Station number and leave the read of the settings default. You can leave the pin holding register at 551.
Go to the Data Tags section on the left side and map a new numeric tag. (See beginning of this technote in the Modbus RTU setup that goes over creating tags.)
The RedLion PM50 Master driver has all the PM50 points built in as a selectable option. For reading Count A, you can select PM50_1 under internal for the source setting on the tag to pull up that data item list. Select the appropriate PM50 Register that you need to read.
Downloading and Connecting Live to the Crimson 3.2 Device:
Once the above is completed, we are ready to connect, download, and watch that Count A value live.
You can save your Crimson 3.2 file via clicking File, then selecting Save As. Once you save your file, you can connect to your RedLion device via USB or Ethernet. In this example we will be using USB type A to B printer cable.
In the Crimson 3.2 file, click Link, then select Options. In the Options windows, make sure USB is checked, then hit OK.
Once physically connected to the RedLion, click Link again, and this time, select Send. This will start the download process. Crimson 3.2 will not return any success messages. Good indication that the download completed is when the window that pops up goes away. That means the download is complete.
Once the RedLion is programmed, we can on now perform a live watch on that mapped CountA tag to check for live data. Go to the Data tags section, right click on the Count A mapped tag and select Add to Watch List. This will add the tag to the watch window and pull it up.
In the watch window that shows up, you first have to select the option View Online. Once you select view online, this will start the connection process of reading Count A live. Once live, the lower left corner of just the watch list window will change from Showing Simulated Data to Showing Live Data. Once it shows Showing Live Data, check the center column value field for data. You want to see good here whether that is 0 or something larger or smaller. Bad indication of either no communications established is when the tag value returns N/A. This means there is a connection issue between the RedLion Crimson device and PM50.
Disclaimer
It is the customer's responsibility to review the advice provided herein and its applicability to the system. Red Lion makes no representation about specific knowledge of the customer's system or the specific performance of the system. Red Lion is not responsible for any damage to equipment or connected systems. The use of this document is at your own risk. Red Lion standard product warranty applies.
Red Lion Technical Support
If you have any questions or trouble contact Red Lion Technical Support by clicking here or calling 1-877-432-9908.
For more information: http://www.redlion.net/support/policies-statements/warranty-statement