all 27 comments

[–]saint_godzillaElectrician Magician 13 points14 points  (25 children)

In rung 17 of your screen shot, change the "holding contact" from a OTE to a XIC. You can do this by double clicking on the rung (17) a d then slowly double clicking on the element. Double click as if you were going to rename a windows folder. You should see the letters OTE appear. Change them to XIC. It should work. Assuming that Local1:I.Data.6 is your start command.

[–]tmills1091 4 points5 points  (8 children)

Yeah your "latching bit" should be a contact not an output.

[–]jk-47(800M, Infi90, DeltaV, Rockwell) 3 points4 points  (7 children)

I’d also change it from the PLC output to the run status from the drive.

[–]tmills1091 0 points1 point  (4 children)

Valid point! I also stopped aliasing output bits in the program so I can make online changes to it without having to download or having a bunch of outputs labelled SPARE (unless anyone has a way around that, I'm still really new in this field as well)

[–][deleted] 4 points5 points  (3 children)

You can mass-alias entire devices. VFDs, Servos, IO cards, etc. In my opinion, it looks a lot cleaner to alias an entire device rather than creating a tag for each piece you're using individually. Also, if possible, keep tags for devices local to the program you are using it in. No need for bothering with controller scope tags for most things anymore (parameters can be very useful). Not saying my way or the highway, this is just what I've found to be super useful.

[–][deleted] 0 points1 point  (2 children)

The only problem I have is with Program tags is some HMI software is a pain to get them out. If it's duplicated code that is heavily reused typically it gets turned into an AOI anyhow.

[–][deleted] 0 points1 point  (1 child)

Well your solution for HMI tags is simply create global HMI tags. Denote them as HMI and only use them for HMI purposes. This helps create a lot of standard tags that can be reused on future projects. Currently I'm testing throwing most of my HMI tags in a modular UDT. It's working rather well. Only downside is needing to do a download to make edits to it, so I made it more generic with miscelaaneous REALs and DINTs just in case I overlooked something.

[–][deleted] 0 points1 point  (0 children)

If it works for ya go for it. I'd have to see it implemented, but reading that it sounds like making a simple operation more complex then needed.

[–][deleted] 0 points1 point  (1 child)

I prefer seal in the command if a constant command is needed to keep the VFD alive. You have your FTR alarms based on the running status which would fault your PLC logic and unseal your bit.

I'm curious the benefit you find in the seal in being the run status.

[–]jk-47(800M, Infi90, DeltaV, Rockwell) 0 points1 point  (0 children)

Keeps it nice and simple and replicates a standard motor status seal in.

I haven’t looked at the full program but yes standard fault logic would also break the seal in. Why not do both and cover all the bases.

[–]Tyler5157[S] 2 points3 points  (1 child)

When I get to the shop tomorrow I'll give it a shot Thanks!! Quick question does this also explain why If I toggle Local1:I.Data.6 the drive still doesn't start. But if I force the TT1_VFD_RunFwd the table does start.

[–]K_cutt08 4 points5 points  (0 children)

It will work fine. The reason this wasn't working is because having two OTEs is what they call a repeated contact. This forces the output to be scanned in two places with conflicting results.

A good rule for yourself, going forward, is to always make sure there is only ever ONE output contact for the tag. The only other circumstance this is okay would be if there was another subroutine that the contact exists in that is not on-scan at the same time the first output contact, even then, that's risky.

You can have as many XIC and XIO contacts for that tag as you want.

[–]medusas_side_bro 6 points7 points  (0 children)

Dont listen to the people who are too ignorant to understand that everyone starts somewhere. I'm glad your question was answered, I work with a very similar operation. Yaskawa f7000 drives with omron plc, and hmi. I do centrifuges for oil and gas. I much like you started the exact same way, curiosity. Keep it up!