Schneider Electric support forum to share knowledge about product selection, installation and troubleshooting for EcoStruxure Panel Server, PowerTag, Com'X, Link150…
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Link copied. Please paste this link to share this article on your social media post.
2013-08-1601:22 AM
Com'X200 Custom Device Type
Just like for the EGX300, the Com'X can talk to anything that talks Modbus.
So let's see how this is done! For our test, we connected the following:
PM5350 - we wanted to add the Pulse out
CWLP Modbus Temperature/Humidity/CO2 sensor from Veris
Interestingly the Com'X200 will allow you to create multiple devices using the same modbus id. A really welcome feature that was not allowed in the EGX300 as now you can have the "standard" information and you can create a second device for the additional stuff. Once in Energy Operation, you can obviously group everything together.
PM5350 Custom Device Type
First I added the standard PM5350. Couldn't be easier:
Go to the Device Settings tab
Select the Com'X200 device in the tree on the left
Click on Discover Connected Devices at the bottom of the tree
Click Start in the new windows
Done!
Next, let's create our new Custom Device:
Again, select the Com'X200 in the tree
On the right pane, go to the Modbus Serial section
In the last drop down, select "Create a new device"
In the new screen, in the Device Type drop-down, go to the end of the list and select "Modbus RTU generic slave".
In the Configuration Pane, enter the Modbus ID (Slave Id)
Select the Usage
Click on Create
A new Modbus RTU slave will appear in the tree under Modbus Serial; Select it.
On the right pane, the configuration settings for your new device type will appear. In the Slave section, click on New Frame
There, the configuration is very similar to the EGX300 except that the numbers start from 0 (not 1), which means that when you read a register list together, remember to put your starting address as register address - 1. As defined in the PM5350 register list, enter the DO1 pulse count register address - 1: 9674
Click on Edit Frame
Click on New item
Enter the Custom name, Format, and Custom Unit
Click Ok, Save Changes and you will start seeing the current value in the Measurement Table section right after the Slave section on your right pane.
CWLP Through Modbus TCP Custom Device Type
For our CWLP, we wanted to add some extra spice, so we connected it to a networked EGX300 (note that it could have been done with an EGX100 too).
Select the Com'X200 in the tree
Then in the right pane, look for the Ethernet section. In the drop down, select Create a new device.
Select the device type and click on Create
Thew new EGX300 will appear in your tree. Select it
Enter the IP of your EGX in the Configuration --> Host section
Click Save Changes
Go to the Modbus Serial section of your EGX300 and again select Create a new device
Select Modbus RTU Generic Slave
In the tree, select your new Modbus RTU Generic Slave object
Just like the PM5350, you can create your new frames and enter the registers (remember - 1)
Last comment, you will notice while entering the items that you can convert the communicated values to what it really is. You can also use that to work out the decimals displayed.