Flex727

I've heard of Ignition that is a SCADA/database system. It looks like the OP needs help setting up MODBUS communications with a SCADA system. @Akash, please tell us what PLC you are using and what MODBUS protocol you are using.

That's calling an HMI screen, not a subroutine. You can't have a Toggle coil hanging on the left rail. I suppose you could, but it would uselessly toggle on every scan.

What is this, @Ausman? This cannot work. @Nico, this is awful coding and I don't even know where to start. Tell me in words exactly what you are trying to do (for example, "I'd like to turn O-84 on and off with a single button on screen", or "I need to have two separate buttons, one for OFF & one for ON", or...) and I would be happy to show you the proper way to do it. You claimed that you were calling the "02 Elevator Test" subroutine, but I sure don't see it. A general principle to keep in mind for the future - only one logic thread per ladder rung (rungs 2 & 4 each have two logic threads).

And this one?

Have you reviewed this thread?

Try this thread:

Based on the spreadsheet in the post linked to by kratmel, you might try 9.7.60 if 9.8.31 doesn't work. Not sure if you can open a 9.8.09 project with VisiLogic 9.7.60 though. Of course the other option is to upgrade the PLC firmware. It isn't all that difficult.

Try 9.8.31. I don't know all the firmware versions and associated VisiLogic versions, but I suspect this one might work.

By the way, when you opened the project in your VisiLogic 9.8.91, it should have warned you that you were opening an older version project in a newer version of VisiLogic and also told you the version of VisiLogic the project was last saved with. Don't ignore that warning!

I'm not sure exactly what you're asking, but you can set any number of timers you wish using the same ML that you loaded from the master timer. You could easily load from master and set all 13 timers in the same ladder rung.

And just to add to and clarify: the firmware update isn't required because you changed the program - it's required because you tried to load the PLC using a newer version of VisiLogic. We recommend not doing that.

I do this frequently. Have a 'master" timer that you set on your HMI, then perform in ladder "Load Timer/Counter Preset" (under the "Store" menu) to an ML. Then perform "Store Timer/Counter Preset" to all the timers you want to set from the master timer. Easy peasy.

Are the iPhone and PLC on the same subnet?

Is this an internal network or over the internet?

Assuming you're using VisiLogic, take a look at the example projects that came with your VisiLogic installation.

In rung 2 you are continuously calling the MODBUS Configuration FB. You need to replace SB 142 with SB 2.

Which version of VisiLogic are you using?

Unless you've initialized another socket to Port 20256 for another purpose, or you've initialized Socket 1 for a different purpose, you're all ready for Remote Operator. Just connect to the PLC via Port 20256. Be sure you know the IP address and PLC Name and it should connect right up. I'm assuming this is all LAN and you're not trying to connect over the internet. By the way, no need for a SET coil for SB 168 - just assign the Power-up to SET.

All of the serial port parameters can be set on the V120 PLC within INFO Mode. It's a bit cumbersome, but it's all there.

When using Ethernet, you have 4 sockets available to you for simultaneous connections. Just use different Port numbers for each connection and they'll be fine. The default configuration for Socket 1 is set for VisiLogic comms (also Remote Operator) - Port 20256, and Socket 2 default is Port 502 for SCADA. If you are using Socket 2 for your SCADA then you are good to go.

The STORE function should work for that. You can store a value into either the Preset or Current for the timer.

Timers count DOWN and the Out Bit will turn on when the Current value reaches zero.

Geez, how did that get by me? Thanks Fernando!

I don't always start using the latest version of VisiLogic right away. Has this been added, or are you thinking of UniLogic?

When I program that function I get 1.65126 for MF 1 using 819 stored in MI 6. Do a search on MF 1 , MI 6, & MI 610 to confirm none of those values are being overwritten anywhere else in the program. Also, if those ladder rungs are in a subroutine, make sure that subroutine is being called in the Main Routine.