Search the Community

Hello friends, I hope you're all doing well. I'm reaching out because I find myself in need of some assistance with a situation. As someone new to programming, I recently undertook the task of creating a lengthy program. However, there's a concept I failed to consider and I could really use your expertise on this matter. You see, I've been working with input and output expansion modules, and what caught me off guard was that these modules automatically assigned addresses within a certain range. For instance, X0 was assigned to X15, and X20 to X34. Regrettably, I didn't anticipate this, and I ended up assigning the new device numbers to these expanded modules. I'm wondering if any of you have encountered a similar situation or if you have any advice on how to handle this issue. I'm open to any insights or suggestions you might have. Thank you all for your time and assistance.

hai, anyone know what the meaning of "ERR" in unpaired content in the picture?

Hello! What i am about to do is connecting an external SCADA system to a Mitsubishi PLC via OPC server. I have already made some FBs and included their instances in a program in GX Works2, then started a GX Simulator2 and connected it to an OPC Server. From the OPC configurator I have defined some tags with their corresponding device addresses (e.g. D12345). I am using structured variables which device addresses i am entering in the OPC configurator. Tried to make some full rebuild compiling and at first was happy that the devices remain unchanged. The main problem is that after some time this devices change which completely ruined my experiment. Maybe there is some point that I am missing or there is just no way to use a fully functional SCADA connected that way to the Mitsubishi PLC (by OPC)? The question is is there a way to tell a particularly used instance of a function block to have exactly the same device addresses ever. 

PAROCK1 for HMI/SCADA View File Now a software solution is available for your Modbus (MB) needs in Rockwell/Allen-Bradley Control Logix or Compact Logix (Clgx) family processors, instead of a traditional 3rd party hardware like Prosoft MVI-56, Molex SST-SR4-CLX-RLL etc.  It is an Add-on instruction (AOI) for PLC/PAC firmware v16 or later, (other solutions are available for pre v16 systems).  For hardware interface, use PLC’s channel 0 (serial) or TCP/IP Interface module(s) to have as many MB TCP/IP devices or serial devices.  (Some limits apply based on system configurations, Comm. settings depending on HW used.) Connect any MB Client/Master or Server/Slave device(s) to your CLgx PLC, including flow computers, analyzers, VFDs, Power Monitors, Level gauges, Smart I/O, etc.  All the MB public/native function codes are supported.  32-Bit integers/floats as single entity are supported with byte and word level swapping. A separate utility automates the data mapping to your PLC logic.  Features -Serial Master (BASIC required Option); TCP; Slave; Redundancy; More than 5000 accumulative registers; MB CFC (Custom/Private Function Code) Support; Data mapping too – Between PAROCK1 & your PLC logic; Packaged with Rockwell; TCP/IP Interface Module; Volume Discounts; Annual Support Requirements -Rockwell/AB-CLgx processor with v16 or later.  Contact PCI for earlier versions. -If using CPU’s Chan0, you cannot use Chan0 for any other user mode activity. You can use it for non-user mode activities -TCP/IP Interface Modules from Rockwell/AB supported, are: -1756-EN2xx ControlLogix® Ethernet/IP communication modules, firmware revision 5.007 or later -1756-EWEB ControlLogix Ethernet/IP web server module, firmware revision 4.006 or later -1768-EWEB CompactLogix Ethernet/IP web server module, firmware revision 1.002 or later -1769-L30ER, 1769-L30ERM, 1769-L30ER-NSE, 1769-L33ER, 1769-L33ERM, and 1769-L36ERM CompactLogix controllers, firmware revision 20.011 or later -1769-L24ER-QB1B, 1769-L24ER-QBFC1B, 1769-L27ERM-QBFC1B CompactLogix controllers, firmware revision 20.011 or later -1769-L16ER, 1769-L18ER, 1769-L18ERM CompactLogix controllers, firmware revision 20.011 or later Other Related Services/Items -Custom PLC Add-on instructions building -PLC upgrades, troubleshooting, applications -PC Windows, iOS5, Linux, Mobile devices Comm. Drivers -Custom development, Technology Transfer Services  -Other Non-AB communication drivers for serial or TCP  -Full control system integration, training, architecture design This driver can be conviniently used with Visual Studio in development of complete large scale complex HMI/SCADA Systems. It can be used to perform advanced reporting MES, analytics, IoT, Big data type apps. One example is available to download here For More Info Overview of Parijat Drivers: Click here  Additional supporting Info about Parijat Drivers:Click here Complete Related Driver options: Click here     Submitter Scadadoctor Submitted 03/10/16 Category Other PLC Demo Software