[Expansion error 400]

Just now, Guilherme said:

It's necessary install this Module?

No. There's two different types of I/O modules available - "Snap-In" modules and "Expansion" modules. Depending on your project requirements, you can have either or both. Sometimes the Snap-In modules can work lose and cause problems, so that is why I was asking.

[Expansion error 400]

I'm not saying that's the problem, but that's the first thing I'd check. Try wiggling the cable at both ends and along the length while the PLC is in operation to see if you can induce the problem. If not, then you might look for a source of electrical interference, such as a nearby VFD or other poorly shielded RF source.

Do you also have a Snap-In module installed?

[Expansion error 400]

You must buy the cable from a Unitronics distributor. It looks like an Ethernet cable, but it's pinned differently and well-shielded. They have multiple lengths available - from 0.5m up to 20m. They're not very expensive, as I recall.

[Expansion error 400]

Have you tried replacing the expansion cable?

[Can I Catch Expansion Errors?]

3 minutes ago, sgull said:

(goes high if the block is removed)

But how would you prevent the PLC from going into STOP Mode? If it did go high a few cycles before going into stop, then perhaps you could activate SB 300? That would reset the PLC without the module and it would run. Worth testing.

[Can I Catch Expansion Errors?]

1 hour ago, Edwinn said:

I was looking for a software approach.

Sadly, I think there is none for that problem on these PLCs, but if there is, I'd like to hear it too.

[Can I Catch Expansion Errors?]

3 minutes ago, Edwinn said:

Is it also not possible to automatic reboot after the connection error?  So the PLC boots again without the expansion...

Once again, a relay connected to a spare output on the I/O module could be connected to the PLC power supply to force a power cycle when the output drops. You would need to figure out how to wire the relay so that it would only be a momentary drop because that output would not come back after the reboot until the module is reconnected.

[Thermocouple Reading of 32767]

10 hours ago, TozoM8 said:

Analog input one is 6-7-8.  3-4-5 is analog 0. 

Good catch!

[Can I Catch Expansion Errors?]

13 hours ago, kratmel said:

Sometimes, someone sw off some protection circuit for maintence and do not sw on after.

Then V1040 started, but without part of IO. Only local E46B present.

In this case you could do the opposite of what I suggested earlier. Have a spare INPUT on the expansion module that is jumpered out to be always on. If the PLC is powered up without the expansion module the lack of signal from the input would activate an alarm signal (presumably connected to the Snap-In module).

[Can I Catch Expansion Errors?]

I suppose you could have a spare output keeping a relay closed and when that output turns off it sounds an alarm, or otherwise notifies an operator.

[Can I Catch Expansion Errors?]

I think not. I can't see how it would be possible for anything good to happen with the PLC running without the necessary I/O.

The best course of action is to determine why the cable is being removed and put a stop to it.

[Thermocouple Reading of 32767]

32767 is a fault code. This is what the spec sheet says:

[Visilogic - Some inputs locked at <0>]

This looks like what happens when you FORCE an input while online with VisiLogic.  I thought that was cleared out with a PLC reboot, but perhaps I'm mistaken. Go online with VisiLogic, click on the Input, RIGHT-click in the popup window on the grayed out button labeled SET, then click Cancel Force.

[Picture move]

5 hours ago, Etienne said:

There is no image slider function?

Not that I'm aware of. You might post the request in the "We're Listening" forum and see if they'll put it on the agenda. I think it would be a good improvement.

[Picture move]

I usually use the List of Images Variable. You can also have multiple images and unhide them in sequence.

[flashing light output]

This is how you would do it with a self-resetting timer:

[flashing light output]

I usually just use SB 3 for convenience, but you can use a self-resetting timer to implement any flashing frequency you desire.

[Today's lighthearted relief...add yours as necessary.]

We're very much hoping that the vaccine reverses the order of those pics.

[Averaging an analog input]

You're right, averaging can get really complex in a hurry, but the specific task you have seems pretty easy. Try this:

[initialization in last screen used in the HMI]

29 minutes ago, edgar.guerra said:

the error I was making applies to all lines of ladder code?

Yes, most of the time it doesn't cause a problem, but it's unpredictable. One line of code for each ladder rung. Notice all the compile warnings you are getting. 

One other problem, do not place the contact for a timer in the same rung as the timer coil. It doesn't cause a compile warning, but it is very poor form.

 

[initialization in last screen used in the HMI]

A big problem you have is that you are placing multiple logic threads in a single ladder rung. DO NOT DO THAT! Notice that the three lines of code I posted above are in three different ladder rungs. Put each line of code in a different ladder rung. That's the whole point of Ladder Logic - each ladder rung is one line of code.

[initialization in last screen used in the HMI]

SB 2 needs to be an inverted contact.

[initialization in last screen used in the HMI]

1 minute ago, edgar.guerra said:

How do I configure that MI 0 to be the allocated memory of the screen I am currently on

Copy the code I posted above except change T 0 and MI 0 to unused operands. Looking at your program, you can use T 30 and MI 100.

[initialization in last screen used in the HMI]

It doesn't work because you didn't use include the code I posted above.

[initialization in last screen used in the HMI]

Let me see your code. What you posted above doesn't look anything like what I showed you.