Crossbow

Actually MEAU (Mitsubishi Electric Automation US) changed their software policy a few months back so that they now include 1 year of updates with the software. But being he's posting from Romania, not sure what the software plans are like at Mitsubishi Europe.

It's not Modbus that is limited to 32 devices. The limitation is RS485 topology. You should not have more than 32 devices on an RS485 network without repeaters. It's a signal strength issue.

The entire Proworx project (all files with the same name, various extensions). You can send a private message via this website or post it here publicly.

More info like what version of Windows would help. Personally I've never had a problem on any of the PCs I've loaded GT-Works on. On another note, 5.27 is way out of date. Current is GT-Works2 2.32.

Can you post or private message the Proworx project? I'll take a look at it and see if I can find anything.

Never seen such a thing. What type of PLC and what version of Proworx?

No. Everything connected after the pulsed contact will run once, not just one line... That would include all of the logic in your picture. But it will only run once on the rising edge of address MB153.

If you've already tried the modules and cables, I would also look at that rack. There are eletronics on the backplane unit that may have gone bad or be a loose solder connection.

Sterling Services (www.sterlingservices.com) usually has a really good assortment of old Modicon parts. I've bought and sold with them in the past.

I'm with Colin, it's not for PLC to PLC communication. In the US we call it FX2NC-ENET-ADP, and it's manual states as follows: The FX2NC-ENET-ADP is an Ethernet adapter of 10BASE-T specifications for the FX1S, FX1N, FX2N and FX2NC Series. The FX2NC-ENET-ADP enables upload, download, monitor and test sequence of programs via Ethernet from a personal computer (GX Developer or MX Component and the virtual COM port driver installed).

Don't know anything about IEC 1031, but IEC 1131 (now 61131-3) covers PLC programming languages. All the |P| contact does is activate for one scan, so all the logic after it will happen once. Not one line, one entire scan of the PLC program.

Seems like if the error was at step 159, it's the preset for the counter. Did the preset get set to a negative number? I would look at the number in D130 and see if it's valid. Counters can be preset 0 to 32,767.

As long as the condition in front is true, the next object will execute. So in your example if you turn on MB153 both of those lines become active.

There are some good suppliers of obsolete and used PLC product in the US, such as www.plccenter.com or www.sterlingservices.com. I would expect that you could find some good surplus houses on that side of the ocean as well.

RS485 serial is typically limited to 32 devices. I would assume the same limit in the Modbus serial commands.

I would look at the inputs to the PLC as possibly losing power (such as X0, X1, etc.) if they are not backed up by the UPS. Also, you cannot make the FX2N PLCs talk to each other over Ethernet. That Ethernet module is a serial to Ethernet gateway, useful for programming and data collection with a PC only. They cannot talk to each other. The best way to make them talk to each other is install an FX2N-16CCL-M CC-Link master on one and FX2N-32CCL CC-Link slave modules on the others. However, if you use the FX3U PLC with the FX3U-ENET module, these PLCs can talk to each other over Ethernet. As another note... If you have the software, connect to the PLC and see what the error is. In GX-Developer, you go to the Diagnostics menu and pick PLC Diagnostics. It will tell you what the error is and how to correct it. There is extensive help on PLC errors in the help files of GX-Developer.

Why pull the unit? It's a simple problem to fix. An address beyond the limits of the PLC is being accessed. Check the step number in the program referred to by the error, see if it is using indirect addressing (V or Z pointers) and see why the pointer has exceeded the valid PLC memory range. Not worth the time to replace the whole PLC. Scroll down to step 159 and post us a screen shot so we can see what that step is.

They'll work just fine. You can use any extension unit on any PLC. Doesn't matter the input or output type, as that module will have it's own common terminal, so it can be wired differently from the base PLC.

The EM241 modem module is the easiest method since there's a wizard built into the software to configure it, and there's no cables to mess with. And it has support for things like SMS messages to cell phones for alarms. Used one on a water treatment system to call the manager in high water alarm and for remote dial-in maintenance.

The WS model has some basic web server functions. I've never seen one without the WS in the part number. I know they were replaced by the TSXETY410 and TSXETY510 a few years ago. So the 110WS is really old.

Most vendors have begun to use USB for their programming connections. Mitsubishi offers USB connection on the FX3U, Q02H and above, GOT1000, MR-J3 servos, and A700 VFDs. So you wouldn't need a serial port for those. As for a PC without, the USB-Serial adapter recommended for Mitsubishi products is the Keyspan USA-16HS or USA-19W. I've also had good success with the CP Technologies CP-US-03. The Keyspan is like $35 from CDW and the CP one is about $10 from TigerDirect.com. I know some Dell Lattitude laptops still have serial ports. Not the cheaper Inspiron ones though.

GP2501 is not a valid part number for a Mitsubishi PLC or HMI product. Are you sure you are in the right forum?

No driver I've ever seen for that. Those units didn't have a huge library of third party drivers. You might want to consider the Mitsubishi E-Series. Even the current GOT1000 units do not have Modbus or any driver for Schneider Electric equipment.

SD210 through SD213 are the clock locations, and are allocated in hexadecimal by bytes. SD210 upper YEAR (last 2 digits) SD210 lower MONTH SD211 upper DAY SD211 lower HOUR SD212 upper MINUTE SD212 lower SECOND SD213 upper YEAR (first 2 digits (19 or 20)) SD213 lower WEEKDAY (0-Sunday, 6-Saturday) But when using DATERD instruction, such as [ DATERD D100 ], the data is stored as seperate words in decimal, and the order is: D100 - Year (4 digits) D101 - Month D102 - Day D103 - Hours (24 hour mode) D104 - Minutes D105 - Seconds D106 - Day of Week (0-Sunday, 6-Saturday) If you wish to modify the clock, the format for DATEWR which updates the clock is the same as DATERD.

You don't need the addresses. Use the DATERD command to copy the real time clock into 7 data registers of your choice. Use DATEWR to copy it back if making changes.