Great video, I'm just doing a similar test. One question, in the case of an M580 PLC with DAS MBTCP, is it only necessary to declare the Device Group or must the Device Items also be declared?
The both the device group and device items are optional. If not specified, the default device group using the global configuration attribute values from the DAServer is assumed.
Good work! I am testing the direct communication MODBUS to read a data 3x00034 in float, for example. The TAG that is created in "Tagname dictionary", is ITEM:300034, for data 3x00034? Is correct? thank you!
Yes you got that right if you are using extended Modbus addressing which has the following ranges. 0x Coil 000001-065535 1x Discrete Input 100001-165535 3x Input Register 300001-365535 4x Holding Register 400001-465535 Just as a reference, standard Modbus address range is as follows. 0x Coil 00001-09999 1x Discrete Input 10001-19999 3x Input Register 30001-39999 4x Holding Register 40001-49999
Hello I have a communication problem between my OI MBTCP server and a schneider M340 PLC with an NOC0401. I have a problem with latency and refreshment of the supervision. when I go to the diagnostics I have the SUITE LINK which displays SUSPEND and it displays RESUME about 15 to 30 seconds later. And it happens about every 2 minutes. Do you have a solution please? thank you so much
Do you have a Modbus simulator like MDBus? If you do try hooking the Modbus client as Modbus TCP on the M340 network and watch if there is any packet drops.
Are you able to read other data from the same PLC/RTU into you Archestra DA Server MBTCP? Why I am asking this is to make sure that your communication is setup correctly and there is not communication/networking issue. I would like to recommend doing ping test but make sure that all ICMP packets are allowed in your network. If there are some data that is coming through using the Archestra DA Server MBTCP driver, then the problem would be with how your data point is setup. If that is the case, make sure that the Modbus address you are polling is actually available. Some if not most of the Modbus devices I work with does not have a full suite of Modbus address like for holding point from 40000 to 49999. Make sure that that the modbus address you are polling is correct. Another thing I would check would be the data format. The Archestra DA Server MBTCP acts all weird when you are polling a floating point, Make sure your data is setup correctly and be aware if your Modbus address is ZERO or ONE base. Communication issue can be tough but hang in there. Drop me a comment again if you need more clarity or need to bounce off some ideas with me. Good luck!
Hello there, I am trying to connect Archestra System Management Console(Smc) to Red Lion Data Station (DSPX) using Crimson 3.0 through Modbus TCP IP, but the SMC doesn't reach the device IP address. Please any clue would be much appreciated.
Here are few things you can try on the ArchestrA side. 1) Network Testing. Try pinging the RedLion from the Wonderware server. Make sure that you are pinging from the Wonderware Archestra server. 2) Monitor SMC Log. Have look at the ArchestrA communication log file. That will give you a clear indication of what is going on. To access this log file, from your ArchestrA System Management Console (SMC) windows, expand ArchestrA System Management Console---Log Viewer---Local. If there are too much logs, apply filter which can be access by clicking the "funnel with yellow pencil" icon (it is in the series of icon right below the pull down menus like File, Action, View, Help). You can see a demo of where the Log Viewer is from the vide link below. ua-cam.com/video/zjbzbJy5dzY/v-deo.html&feature=shares If the above two steps does not yield any result for you and you are absolutely sure about your network settings on the ArchestrA side (including firewall, group policies, IT mambo jumbos garbage settings or cybersecurity), I would check the RedLion setting. Try hooking up the RedLion directly to your computer/laptop and try polling the Modbus registers from the RedLion using any Modbus simulator like MDBus. If that checks out okay, then it must be the network cable/connection between the RedLion and the Wonderware ArchestrA. I hope it helps!
Great video, I'm just doing a similar test. One question, in the case of an M580 PLC with DAS MBTCP, is it only necessary to declare the Device Group or must the Device Items also be declared?
The both the device group and device items are optional. If not specified, the default device group using the global configuration attribute values from the DAServer is assumed.
Good work!
I am testing the direct communication MODBUS to read a data 3x00034 in float, for example.
The TAG that is created in "Tagname dictionary", is ITEM:300034, for data 3x00034?
Is correct?
thank you!
Yes you got that right if you are using extended Modbus addressing which has the following ranges.
0x Coil 000001-065535
1x Discrete Input 100001-165535
3x Input Register 300001-365535
4x Holding Register 400001-465535
Just as a reference, standard Modbus address range is as follows.
0x Coil 00001-09999
1x Discrete Input 10001-19999
3x Input Register 30001-39999
4x Holding Register 40001-49999
Hello
I have a communication problem between my OI MBTCP server and a schneider M340 PLC with an NOC0401. I have a problem with latency and refreshment of the supervision. when I go to the diagnostics I have the SUITE LINK which displays SUSPEND and it displays RESUME about 15 to 30 seconds later. And it happens about every 2 minutes. Do you have a solution please?
thank you so much
Do you have a Modbus simulator like MDBus? If you do try hooking the Modbus client as Modbus TCP on the M340 network and watch if there is any packet drops.
Hi Rabi
I am having trouble acquiring data from PLC smc shows bad in quality parameter can you help me in this
Are you able to read other data from the same PLC/RTU into you Archestra DA Server MBTCP? Why I am asking this is to make sure that your communication is setup correctly and there is not communication/networking issue. I would like to recommend doing ping test but make sure that all ICMP packets are allowed in your network. If there are some data that is coming through using the Archestra DA Server MBTCP driver, then the problem would be with how your data point is setup. If that is the case, make sure that the Modbus address you are polling is actually available. Some if not most of the Modbus devices I work with does not have a full suite of Modbus address like for holding point from 40000 to 49999. Make sure that that the modbus address you are polling is correct. Another thing I would check would be the data format. The Archestra DA Server MBTCP acts all weird when you are polling a floating point, Make sure your data is setup correctly and be aware if your Modbus address is ZERO or ONE base.
Communication issue can be tough but hang in there.
Drop me a comment again if you need more clarity or need to bounce off some ideas with me.
Good luck!
i have done installed driver modbus oi.mbtcp in my laptop but in smc doesn't appear mbtcp, how th solution sir?
Hello there,
I am trying to connect Archestra System Management Console(Smc) to Red Lion Data Station (DSPX) using Crimson 3.0 through Modbus TCP IP, but the SMC doesn't reach the device IP address. Please any clue would be much appreciated.
Here are few things you can try on the ArchestrA side.
1) Network Testing. Try pinging the RedLion from the Wonderware server. Make sure that you are pinging from the Wonderware Archestra server.
2) Monitor SMC Log. Have look at the ArchestrA communication log file. That will give you a clear indication of what is going on. To access this log file, from your ArchestrA System Management Console (SMC) windows, expand ArchestrA System Management Console---Log Viewer---Local. If there are too much logs, apply filter which can be access by clicking the "funnel with yellow pencil" icon (it is in the series of icon right below the pull down menus like File, Action, View, Help).
You can see a demo of where the Log Viewer is from the vide link below.
ua-cam.com/video/zjbzbJy5dzY/v-deo.html&feature=shares
If the above two steps does not yield any result for you and you are absolutely sure about your network settings on the ArchestrA side (including firewall, group policies, IT mambo jumbos garbage settings or cybersecurity), I would check the RedLion setting. Try hooking up the RedLion directly to your computer/laptop and try polling the Modbus registers from the RedLion using any Modbus simulator like MDBus. If that checks out okay, then it must be the network cable/connection between the RedLion and the Wonderware ArchestrA.
I hope it helps!
@@RabiGurungXybernetics Thank you very much Rabi, I will do that if I can't get it to work, I will try OPC application in Archestra.
You're welcome! Let me know if you need any help with the OPC application in Archestra. Good luck and I hope it works out for you.