Flex727

I still say it's vibration with the Snap-In module. I've seen it happen more than once and I got those exact same errors.

In the first picture (rung 5) you are checking the status of Socket 1 (Initialized, but not connected). You might want to do the same in the V700 using Request #22. In the bottom picture you seem to be checking the status of Socket 0 (rung 6). Not sure why. Changing over to the V700 shouldn't be a big mystery. Unitronics has clearly labeled the System Operands that no longer apply and provide a function that replaces those operands. Otherwise, everything works the same.

That date is the firmware date. not the current date. It's possible that your V200-18-EB6 Snap-In module is vibrating loose and losing its connection with the PLC. Either replace it if it's old and/or press down on it securely and run some tape around it to hold it in place.

You're piling too much stuff into one ladder rung. I've never tried to perform MODBUS Config before Socket Init, but it is likely important to perform the Socket Init first. Your ladder rung loses control over that order execution. Try breaking that rung into 3 or more separate rungs. I'll repeat something I've said before - Unitronics WILL NOT charge you by the rung. Break your code up into the basic simple instructions for both readability and to have more certainty that the code will compile the way you think it will. If that doesn't solve your problem, then you need to post the internal workings of each of your function blocks or post your .vlp file here.

I've never done it, but I thought you could run a full-blown webserver off the SD card in the Vision line. No question though that UniStream is more powerful in that regard.

I recently had a V570 that wouldn't communicate over Ethernet. I swapped out Ethernet cards with a known working card (and several other troubleshooting steps) and still no worky. Since then I began using VisiLogic 9.8.64 and updated the firmware on the PLC to the latest. Now it appears to be working. We shall see.

Did you install VisiLogic "As Administrator"? Do you run VisiLogic "As Administrator"? Does it do this when you open other projects, or only this one? Is this a new problem (i.e. was VisiLogic running fine and then suddenly developed this problem)? Which version of VisiLogic?

I don't know the answer to this either, but I've created many projects that hammer the clock on every scan, not to mention Data Tables, and other very complex functions. Never seen the slightest problem with things not keeping up. I do agree with @Ausman that a programmer should never have the PLC perform unnecessary steps, but it's more a matter of elegance and minimizing scan time than necessity to have a functioning PLC program.

Can't argue with this. "Slick and professional" is what I try to achieve with every project.

Another option for you that's a bit more straightforward, if a bit more cumbersome: If you can group your 60 Program IDs into some logical grouping, say 6 groups (each on a separate HMI screen) of 10 program IDs, you could just have pushbuttons for each program ID. Label each pushbutton with the program ID instead of having the operator enter it each time on the HMI (which can be a pain). Pressing the button turns on a bit that activates the cycle associated with that program ID.

Just to shortcut this a bit. I would enter the 60 Program IDs into a Data Table then use the "Find Row" function to compare the HMI entry to the Data Table column with the Program IDs. This function will return the row number which you can then use to key the 60 different cycles.

What would be an example of a "Program ID" that would be entered into the text box?

Strings are stored in a vector of MIs, two characters per MI. Not sure what you're trying to do here. Are you entering a string via HMI or are you storing already known string for use in the program?

Link the numeric input to an ML instead of an MI. Use a string input instead of a numeric input.

That driver is for use of the Mini-USB port on the newer PLCs. You will need a USB to serial converter (such as this one: https://www.amazon.com/Trendnet-TU-S9-USB-Serial-Converter/dp/B0007T27H8/) and the serial adapter that comes with the older PLCs. I don't have the part number handy for that old serial adapter, but Unitronics (support@unitronics.com) can help you. Found one laying around and it says MJ 10-22-CS25 on it.

Agree that he's probably talking about the OS, but if you're not updating the software I see no reason to update the OS.

This is a Godsend for those of us with large high-resolution monitors. +1 on @tmoulder's comment!

Why do you want to update the firmware?

Don't anthropomorphize PLCs. They hate that!

What is the purpose of MB 0? If the toggle button for MB 40 is hidden, you will not be able to change the state. Also, Why is your pushbutton assigned to MB 40 and then MB 40 directly controlling MB 53? Why not just assign the toggle pushbutton to MB 53?

The three most dangerous things in the world are: A programmer with a soldering iron. A hardware type with a program patch. A user with an idea.

Ha ha! You got it.

Because 7 10 11.

Yes, all you have to do is insert a net before Net 1 and Store zero into MI 1. test_analog-out_BL.U90

I've frequently found that direct saving to virtual drives can be problematic, and not just with VisiLogic. Because of that, I always save locally then copy to the virtual drive later.