Flex727

Just use contacts for digital inputs and coils for digital outputs.

Is there some reason you need Immediate Reads and Writes instead of the regular kind?

Using an SD card to store the values may be a bit cumbersome and slow. You can easily have a Data Table in the project with 1000 rows and read or write whatever data you need to or from the table.

There is no need to reset total sessions or acknowledgments, though you can if you are using the numbers for some purpose.

Yes, I noticed that change somewhere around VisiLogic 9.5 or 9.7. It only happens with certain color combinations. I'd like to see it fixed also.

Oops, one more: 5) You need a CONNECT FB in your master PLC.

It looks like you have a number of problems that are easily resolved. 1) In the master, use a polling timer so that you are not trying to exchange data on every PLC cycle. I know MB 201 will prevent that, but a few extra milliseconds generally helps with MODBUS IP. I usually poll at 100ms intervals, but you can go much faster if you absolutely need to. 2) In the slave you do not need to configure socket 2 - you are scanning on socket 3. 3) Also, you are using SB 149 to gate your SCAN_EX FB - this will prevent the SCAN_EX FB from being executed. You should be using SB 146. 4) You do not need the SCAN_EX FB for the SCADA in your slave PLC.

Glad to hear and thanks for letting us know.

You have several alternatives. You can use latched bits and SET & RESET them appropriately or you might see if a TE timer would serve your purposes better (with slightly different triggering logic), or there might be other options depending on your overall logic.

Does something turn off MB 71 when the output reaches max value? If not, you are incrementing then decrementing on each PLC cycle, thus leaving the output unchanged.

I haven't encountered this particular error, but an important consideration is that VisiLogic MUST be installed "as Administrator" and the program file MUST be "Run as Administrator".

Sure you can - easily. When you have the ladder displayed, look just above the ladder window and you'll find a drop down labeled "Data Tables". It has all the ladder commands you'll need to store, manipulate, and recall data from the data tables. You'll need to create your data table first with the properties you need for your application.

Look on that toolbar that runs vertically between the two primary panes in VisiLogic. When you have an HMI screen displayed on the right side, you will have nearly everything you need for adding display elements to you HMI screen. One of the icons will say "ASCII String" (Near the top, under "Text") when you hover over it with the mouse. Click that icon (not click and hold) then draw the box on the screen to the size you want (you can change it easily afterwards). There is also a dedicated Password entry box a little further down, under "Numeric".

I haven't tried it, but you can assign an indirect operand for Y-Min and Y-Max. I would presume you can calculate your own scaling using those operands.

Just want to clarify - both INPUTS and OUTPUTS can be forced, but I believe the rest of my statement about other memory operands stands. Thanks for the heads up, @Ausman!

Are you calling that subroutine in the Main Routine? As I said before, FORCE is only for INPUTS, not MBs. You can only manually SET or RESET a bit if it is not being activated by a Direct Coil in the ladder. Also in your picture in net 1, you have a SET coil (MB100) being activated by a Direct Contact (MB78). You cannot manually Reset MB100 as long as MB78 is on. Bottom line, only INPUTS can be forced, no other memory operand can be made to take on a value manually if it is being assigned in ladder on every scan. You cannot override the ladder logic from VisiLogic.

You can never manually Set or Reset any bit that is being activated by a Direct Coil. The only way this can happen is if the coil is in a subroutine that is not being called by the Main (or other) Routine. Post your code here and we can help you.

I meant more specifically, what is the problem you're trying to fix here?

@JMorel, can you restate what it is you're trying to do?

As I said, Force is only for Inputs, as in memory addresses that start with "I".

In your picture, you cannot change the value of MB111 manually since it is being activated by a Direct Coil on every PLC scan. In order to affect the value of MB111, you must change MB100 or MB40.

Force is for INPUTS, Set & Reset are for Memory Bits. A Bit that is manually Set or Reset will remain Set or Reset until there is activation of a Set or Reset Coil in the ladder.

Thanks, Cara.

Did you Cancel Force on the Input when you were done?

Was the Remote Operator software installed "As Adminstrator" and is the installed program being run "As Adminstrator"?