PendantAutomation

I still need to get the alias tags into the array, correct? Would I map that by moving Input DINTs and Output INTs into the arrays? (using 32pt input cards and 16pt output cards)

Yes using 5000.

I have (176) workstations with local controls to each. Each has (2) photo eyes, a solenoid, and an MDR zone control. Therefore I have (176) of one photo eye, (176) of the other, and so on. My tags are all labeled with respect to the workstation. E.g. "solWorkstation1". My question is, is there a way I can use the same AOI in a loop and index the workstation number like I could if these numeric values "xx1" were elements in an array such as "xxx[1]" becoming "xxx[indexer]?

I was also looking for ideas in how to program the sort. For instance, using two counters on a sort/pass basis, or a FIFO for the first two lanes... Those ideas would be helpful if someone has done much of this. What works best?

I am looking to see if anyone has ideas/code for programming a round robin sort on a conveyor system. Say three lanes where it is 1:1:1 ratio, then if we add in a 50% lane full eye. How would you go about giving priority to other lanes that were not at the 50% mark?

The best use of a Data Block is data organization and transfer. For instance, with a data block you can store all data for a given system in one location. Below: DB1 Pump 1 Data Block Status | BoolRun Command | BoolRun Minutes/Hours | DIntDischarge Pressusre | IntSuction Pressure | IntTemp | IntOnce you have created the Data Block you can easily view all data in one location while online in the PLC. Not to mention if you had to send this data to a SCADA system you could just send DB1 instead of all the individual points. I know Siemens WinCC v7 SCADA package allows you to build faceplates that provide functionality with data blocks for ease of use. For instance you would build one faceplate and insert the data above like I have shown in the data block. Then tell the faceplate to poll DB1. The faceplate will automatically apply offsets as you specify for the data. I.e. Status would be DB1 offset 0.0.Run Command would be DB1 offser 0.1, Run Miuntes would be DB1 offset 1, and so forth. This way you can duplicate faceplates in a minute or two rather than 30 minutes.

Hi we're custom building a large MCC that has a 3000A bus. So far ABB, T8 is the only Molded Case Circuit Breaker that I can find that goes to 3000A. Does anyone have another mfg. in mind? Would need to be capable of having a flex shaft handle as well.

Thanks! In chatting with their tech support, the NX100 controller cannot be fully controlled from a PLC. You only get basic commands such as, Robot Active, Alarms, Faults, Warnings, Resets, etc... In order to get full control and make the Motoman a 100% slave, it needs to have the DX100 or DX200 controller installed. Thanks for your help and I hope this post helps someone else out in the future!

Am I missing something obvious, or is there no FIFO in Step 7? Can someone shoot me in the right direction with regards to setting up a FIFO in Step 7 v12/v13?

I have a project that currently has a PC using C++ to send commands over to a Motoman Robot for palletizing. My customer wants to get rid of the PC since no one on the plant floor can troubleshoot if the PC goes down. They're asking that I put a PLC in in lieu of the PC, and control from there. The PLC and respective code is no problem, where I'm stuck is gathering info on what protocol I can use on the Motoman. My goal is to make the Motoman as "dumb" as possible and control everything from the PLC. Can anyone tell me what protocol I can use with the Motoman, details below: Robot Type: EPL80Controller Type: NX100Software Version: NS4.02 A(JP/US)-00

No problem, glad I could help. Good luck!!!

Yes, all IS wiring shall be no less than 2 inches from non IS wiring. The conduit does not need to be blue, but identifiers within the panel should be. I.e. Terminal Blocks, wiring, and wire-way.

What most people are referring to when they use the term "noise," is actually eddy currents produced by a magnetic field within close proximity. In it's purist form, what happens is that a magnetic field creates mutual inductance into an adjacent conductor. Eddy currents are defined as any current that flows opposite to the standard current flow at any given point. Keeping that in mind, transformers are built to keep the magnetic field in as close proximity to the transformer as possible. Knowing transformers are not 100% efficient, one of these reasons is flux leakage, which is what you're concerned with. Flux leakage is not something you should need to worry about when locating your CCT's in your panels. The real culprit of disaster is heat. The reason VFD's and CCT,s need room between them and wiring ducts is for cooling purposes, not necessarily noise. If your wiring duct is mounted at a safe distance that your transformer is not going to pass unnecessary heat onto the wiring duct, then you should have no flux leakage issues to worry about either. As a general rule of thumb, we mount anything larger than 750va outside of the panel. Especially if we have VFD's inside. No sense in added heat in a panel with drives.

If you use a conduit listed in NEC Article 501 and the E-Stop housing is listed for hazardous locations, then you can take the 24vdc (or 120vac) straight to the device. Another way: you can use an intrinsically safe barrier inside your enclosure, and take the IS wiring to your E-Stop. Doing this will not affect the E-Stop Sensitivity Relay at all. Just make sure you use N/C monitored contacts on your E-Stop, a N/O contact on your IS Barrier (which will be energized under regular conditions thus making the contact close) and the standard SIL 2/3 wiring diagrams on the E-Stop relay. I recommend Phoenix Contact P/N 2865434 for the IS Barrier.