Flex727

Ah, cool. Thank God for VisiLogic.

Are we talking about Data Tables? I've never seen Data Tables at all in U90 Ladder.

Glad you mentioned that Ausman. I was going to ask, and forgot, if the coil was always on or if he actually saw it turn on. I've been surprised on occasion at what coils are already set when I load software. It's usually a good idea to load a blank project and perform initialize & reset, prior to loading a new project in a PLC - even a brand-new PLC fresh from the factory.

Obviously there isn't enough information here to answer your question, but here is the approach I would take: - Search for MB 7 to see if it exists anywhere else in the program (other than the Reset in rung 4). If not, then: - While online (as you are above), try to turn off the bit. If it will turn off, then look at the logic in Rung 2 that turns on MB 3. If anything can turn on MB 3, even if only for 1 PLC cycle (which you would not be able to see while online), then MB 7 will be Set. - If neither of the above solves the problem, then now that you have MB 7 off, do some testing to see if you can get it to turn on again and note the conditions present. By the way, it is good programming practice to label every operand used in the program. Also, NEVER have a timer contact following the timer coil, as you are doing (twice) in Rung 4. It makes no logical sense and will not function properly. While not prohibited, it is usually poor practice to have ANY contacts following a coil (most PLC programming software won't allow it at all even though Unitronics does). Break the logic up into multiple rungs to avoid that. Think of a ladder rung as "conditions >>> actions". Keep all the conditions (contacts, compares, etc) to the left and actions to the right (coils, stores, etc).

Well, it would depend on exactly what you're trying to do.

There are many ways to do this. One way is to create a 1 hour timer and use it to increment an MI or Counter.

Nicely said, @Ausman! Forum members - this is terrific advice.

SI 0 provides the scan time for the PLC.

Even if only 2 pulses per second, what is the length of each pulse? Couldn't it still be missed unless a HSC is used?

JohnR, I think the problem is that you need the actual Enter key when trying to enter a numeric variable and similar items. If that's the case, the only answer may be repair or replace (likely replace).

Also, not sure why you need MB 6, but you also have two networks in that ladder rung. Don't do that. And to further Ausman's point, MB 100 and MB 101 aren't doing anything. If they are used elsewhere, just use SB 1, as they are both always on. Place those subroutine calls on a ladder rung by themselves. I don't see which I/O module you're using, but if it's truly a 14-bit module, the correct linearization is 3277-16383, not 3286.

I can probably help you. Email me at blanier @ arc-controls . com and we can discuss (remove spaces).

I guarantee you the linearization block handles negative numbers just fine. Post your code if you'd like someone to take a look at it.

You are correct. I was thinking of the SM35.

I think that means a second serial port - there's one built in.

Where did you see this? I don't do many projects with Samba, but I don't think that's true.

The V1210 supports UniCAN right out of the box, but I think you have to buy a module for the Samba. I also don't think you can run both UniCAN and Ethernet simultaneously on the Samba, but you'll need to check me on that.

Did you consider MODBUS RTU?

If your test setup runs fast enough for you, then that's obviously better info than my estimate. The right code can overcome one of the Sambas being off, but the permutations might get overwhelming. A UniStream will definitely be able to maintain a MODBUS TCP connection to 10 Sambas simultaneously.

Perhaps this will flesh out more what I was trying to say: V1210 Master to Samba 1-4 Samba 1 is slave to V1210, master to Sambas 5 & 6 Samba 2 is slave to V1210, master to Sambas 7 & 8 Samba 3 is slave to V1210, master to Sambas 9 & 10 Samba 4 is slave to V1210 only This still leaves an open socket on each of your Sambas and allows very rapid communication to all the Sambas from the V1210 (with the right code in each Samba). Another consideration (still doesn't solve all problems, but makes things a little easier) is the V700. It has 8 sockets instead of just 4. And finally, the UniStream has unlimited sockets, so that is another option.

Yes, but be aware that the process of disconnecting the V1210 from one Samba and connecting to the next can take time, maybe a couple of seconds. If speed is of the essence, then have the V1210 stay connected with up to 4 Sambas, and have those Sambas stay connected with all the others, and have them relay the message. That can happen very rapidly (probably less than 100 or 200 milliseconds, perhaps much less).

Your description is not precise enough to know if this will or will not work. However, I'll reiterate what was said above. Each V1210 & Samba PLC has 4 sockets for ethernet communications. Each socket is one communications channel to communicate with one device at a time. Each of these sockets can be setup independently as master or slave to any 4 ethernet devices simultaneously. You cannot maintain simultaneous communications with more than 4 devices using MODBUS TCP from any single PLC. You can, however, communicate with up to 4 of the Sambas from the V1210, while having each of those 4 Sambas communicate with up to 3 other Sambas in any way you wish.

The files are there - I downloaded them (thanks @Ausman!). On a desktop, just click (left button) one at a time and it will allow you to download the file to the location of your choice. If you're on mobile, then I'm not sure what to do.

True when there is no battery, or a dead battery.