Search the Community

Showing results for tags ' prosoft'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Found 7 results

  1. Hello! I have one Controlllogix project that communicates with a modbus slave through modbus TCP, using a Prosoft module model MVI56-MNETR. Does anyone know what happens to the data polled in case the network fails? Do all variables go to zero or do they freeze in their last value (or something else entirely)? I couldn't find anything in the Prosoft manual. Thanks for any help!
  2. Hi, Does anyone know the R485 pinouts for the RJ45 ports on this modbus card. I've read the manual it suggests the pin 1 is non-inverting and pin 8 is inverting, but that's with a DB-9 to RJ45.   Thanks, Stuart
  3. Any experts on DNP 3.0 protocol

    Hi everyone. I'm new to this community but finding a lot of useful information and active discussions going on in these forums.   To those who are familiar with DNP3 protocol and AB products, I was wondering if anyone know whether there is an alternative to Prosoft's current MV169-DNP used on Compactlogix RTU applications.  I've been searching everywhere and can't seem to find a substitute product.  Reason I'm asking is because prices are going up every year for their products (which are already quite costly) and having an alternative means we can be more prepared in case there is any change in the future. Thanks in advance!
  4. We have a contract to refurbish/upgrade a filling/bottling machine. We have the machine but not its control panel or PLC. We've built a new control panel based on the original drawings. We've changed the obsolete 1756-MVI/A serial comms modules to ProSoft MVI56E-MCM modules. These two comms modules are to talk to sixteen (16) Endress & Hauser Promass 63MT08-WOW00A9092B mass flow meters - each module talks to 8 of the 16 meters on separate RS-485 networks. My problem at the moment is that there seems to be no way of knowing the port configuration parameters (i.e. baud rate, data bits, stop bits, parity etc.) without having the original 1756-MVI modules. I should add that these meters are 'blind' with no built-in keypad or display for programming or querying the program. I've approached E&H in the hope that they would have a method of extracting the configuration from the meters but they are saying that the meters are so old that all their expertise and equipment for performing such a task is no longer around. I'm going to attempt to track down the original equipment manufacturer in the hope that they may have kept records. Other than connecting up to a meter and trying multiple combinations of settings in the hope that we hit on the right one, does anyone have any ideas on how we can make progress with this? Also, the meters use what appears to be E&H's proprietory Rackbus protocol. The original 1756-MVI modules could talk to them (presumably!). Any ideas if the new ProSoft modules will be able to?
  5. 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
  6. Greetings, I'm having a lot of trouble getting a Prosoft Modbus module to work in my CLX5000 platform. It worked when testing in a single chassis with a 1756-L61 processor and DF-1 comms to my laptop. Now that it's installed in a networked processor and Controlnet rack I can't get it to accept the Ladder Logic. But that's not the question... When attempting to get aid from Prosoft I got a load of fast facts insisting I had to schedule this module with RSNetworx. I don't have RS Networx and I believe my scheduling is correct as the rack was preexisting and the CNRB/E module in place. I can see the icon for the Prosoft module in my IO config tree with no faults indicated and I can inhibit the module getting the two slash yellow circle on the icon. I can also fault the module by checking "Use Scheduled Connection over ControlNet" or changing RPI outside of the default range. To my mind that suggests my Controlnet scheduling is fine and there's another setup problem. Does that sound reasonable or do I need to get RSNetworx and start fiddling? Thanx, Steve
  7. Hi I have a customer who wants to communicate some setpoint information from their Siemens S7 PLC to a CompactLogix L32E PLC. I have installed a Prosoft PLX32-EIP-SIE for ethernet-to-Siemens Industrial Ethernet comms. On receiving a setpoint in from the S7 I then close a loop with some speed feedback in the L32E with a PID. I don't have any access to a Siemens S7 (or software) to test that the comms is working before the unit is shipped, all I have is the CompactLogix hardware. I do have a second CompactLogix PLC / PanelView HMI, but I dont think that this will give me the comms to talk to the SIE port in the Prosoft. I was hoping to have a simple slider on the PanelView to change an integer value to simulate the setpoints coming from the S7. Does anyone have any idea how I might implement this with AB hardware / RSLogix / FactoryTalk?