Set Up: Modbus TCP/IP Multi Client/Server Enhanced Network Interface Module for ControlLogix

  Рет қаралды 25,499

ProSoft Technology

ProSoft Technology

Күн бұрын

Пікірлер: 14
@lianakriebel
@lianakriebel 4 жыл бұрын
For anyone wondering...I imported the ProSoft device settings to my PLC, but then after that I found out I needed to change my read/write array sizes and starting points. That's easy to do on the ProSoft side, but on the PLC side I found that you need to change the array size. (If you're changing starting points, I found the PLC didn't care and still wrote to/read from the correct spot on the ProSoft device.) To change the read/write array sizes on the PLC side, I went to the User-Defined Data Types and scrolled down to the MNETCDATA field. Once here, I resized my arrays to match my changes in my ProSoft. (Note: I was using Studio 5000 for my development environment.)
@lianakriebel
@lianakriebel 4 жыл бұрын
Just so we're clear...at 4:39, there's no way to communicate over DINT? The MNETC is hard-programmed to use INT instead of DINT?
@prosofttechnologyinc
@prosofttechnologyinc 4 жыл бұрын
Hi there! You do indeed need to use INT in the I/O tree. This matches the size of a Modbus register, 16 bits. Having said that, as is the case with Modbus, it is still possible for us to read and send DINTs, we just read or send them two Modbus registers (16 bits) at a time, then on the PLC side the integrator can use a COP or CPS to transfer the two INTs into a DINT or vice versa. But they will always be initially in INT form as Modbus does not have a DINT register type. If it helps, we have a video on handling 32 bit values in our modules at: kzbin.info/www/bejne/i17GZZKBe5iIZ5Y&
@DreiK96
@DreiK96 8 жыл бұрын
Hi, I'm currently configuring MVI56E-MNETC with AB Control Logix L73. I got a query regarding communication timeout when the slave lose comm's. The situation is that after comm's failure, the previous data on assigned registers keep the values when the slave last got comm's. I wish to seek your help on how to clear all the data to "0" when a slave lose comm's. Thanks!
@prosofttechnologyinc
@prosofttechnologyinc 8 жыл бұрын
+Andrei K The data can be zero’d out, but you would need to set up logic that, upon seeing a slave had lost communication using our Command Error Pointer, would trigger our cold boot bool. However, doing so also reboots the module, resulting in a break in communication, so the recommended course of action would be to instead create logic that disables whatever existing logic is looking at the “stale” values whenever our command error pointer indicates the corresponding slave for that data is down. If you have any questions, please call our technical support team at 661-716-5100. Thank you!
@nikog2243
@nikog2243 3 жыл бұрын
Hello, can I use this module to get data from four Modbus RTU servers using Modbus RTU/Modbus TCP converter?
@prosofttechnologyinc
@prosofttechnologyinc 3 жыл бұрын
Hi there! While the module always communicates using Modbus TCP/IP (MBAP) on port 502, port 2000 can be used for Encapsulated Modbus RTU communication, thereby allowing the use of the MVI56E-MNETC with most Modbus RTU to TCP converters. For more specifics, please reach out to your local support team, who can discuss this with you further: www.prosoft-technology.com/Services-Support/Customer-Support
@nikog2243
@nikog2243 3 жыл бұрын
@@prosofttechnologyinc thank you. Who is my local support team for Russia?
@prosofttechnologyinc
@prosofttechnologyinc 3 жыл бұрын
@@nikog2243 That will be our EMEA team; here's their info: +33.5.34.36.87.20 ; support.EMEA@prosoft-technology.com
@sc6515
@sc6515 5 жыл бұрын
Hi everyone. If I would want to connect a HMI device (of other company) to one or two Allen Bradley PLCs over modbus tcp/ip protocol and using the MVI56E-MNETC module, Do I have to connect the HMI, all PLCs and the MVI56E-MNETC module to a simple ethernet switch, as in the video? Thank you.
@prosofttechnologyinc
@prosofttechnologyinc 5 жыл бұрын
Hi there! You would want to use a switch or hub for that application. If you have any additional questions, feel free to call ProSoft's Tech Support team at 661-716-5100. Thank you!
@sc6515
@sc6515 5 жыл бұрын
@@prosofttechnologyinc Thank you for your attention. Probabily I was not very clear with my question, can I use a simple etherner switch or hub to connect a HMI display (of other company) with one or two Allen Bradley PLC, over the modbus tcp/ip protocol and using the MVI56E-MNETC module?
@prosofttechnologyinc
@prosofttechnologyinc 5 жыл бұрын
​@@sc6515 Yes, you can!
@sc6515
@sc6515 5 жыл бұрын
@@prosofttechnologyinc Ok. Thank you so much for your answer and for your videos in youtube.
Set Up: Modbus TCP/IP Setup Tutorial for CompactLogix MVI69E & L-MBTCP
12:29
Set Up: MVI56E-MNET Modbus TCP/IP Communications Interface Module
21:32
ProSoft Technology
Рет қаралды 75 М.
Мясо вегана? 🧐 @Whatthefshow
01:01
История одного вокалиста
Рет қаралды 7 МЛН
Арыстанның айқасы, Тәуіржанның шайқасы!
25:51
QosLike / ҚосЛайк / Косылайық
Рет қаралды 700 М.
Мен атып көрмегенмін ! | Qalam | 5 серия
25:41
We Attempted The Impossible 😱
00:54
Topper Guild
Рет қаралды 56 МЛН
Understanding Client, Server & I/O Messaging for Ethernet Networks
14:21
ProSoft Technology
Рет қаралды 39 М.
COM16. ModbusTCP Client via Allen-Bradley CompactLogix PLC
34:05
Electrical Automation Hands-On
Рет қаралды 18 М.
Set Up: ControlLogix Modbus Master/Slave Module using the MVI56E-MCM module
18:27
Understanding Modbus Serial and TCP/IP
12:07
ProSoft Technology
Рет қаралды 1,3 МЛН
TCP Fundamentals Part 1 // TCP/IP Explained with Wireshark
1:17:24
Chris Greer
Рет қаралды 456 М.
PLX31 EIP MBTCP Training Webinar 26 10 2017
55:02
Simon Kembo
Рет қаралды 9 М.
Set Up: Modbus Communications Tutorial for CompactLogix MVI69-MCM
29:05
ProSoft Technology
Рет қаралды 29 М.
How TCP really works // Three-way handshake // TCP/IP Deep Dive
1:01:10
Мясо вегана? 🧐 @Whatthefshow
01:01
История одного вокалиста
Рет қаралды 7 МЛН