mugs

MrPLC Member
  • Content count

    8
  • Joined

  • Last visited

Community Reputation

0 Neutral

About mugs

  • Rank
    Newbie

Profile Information

  • Country United States
  1. I am working on a "duplicate" of an existing system, however the new work cell will use a Control Logix in place of a PLC/5. One of the nodes in the cell has an SLC504 and was set up to communicate via peer to peer MSG over DH+. I have a DH+/RIO card on the Logix Rack and the ControlLogix code has a MSG Write (SLC Typed Write), which I think will work fine, but on the other side, in the SLC, I have a MSG Write and MSG Read with the target device as a PLC5. Anyone know if this will work? The only options for the device type are PLC5, Modbus, and 485CIF.
  2. Hi, I have an old version of Logix5 (v.3), and I need to open the attached file, which is V.5. Can anyone convert this for me?? MUGS.zip
  3. Am I missing something here?

    Ok, I have it now. The missing piece to the puzzle was the encoder that is attached to the indexing table, that I was told was a sensor... It all make sense now. Its counting positions 60ppr, each index, and does things before and after the dwell position, hence the different compare statements... Its amazing how something so simple, can kill you when you don't have any documentation... Thanks to everyone for your efforts, I really appreciate it.
  4. Am I missing something here?

    Hi Rodney, Thanks for the reply. I have the set up pretty clear, with regard to M470, etc. The part that doesn't seem right is the count input, which looks to be a not of M70 to an output (C660). My understanding is that this is the line that would increment the counter, but a not of M70, would basically disable the counter in run mode? Down from that it has M100, which is the index pulse, and M71 (run one shot) to reset the counter with an RST command. I would think that the index pulse should be incrementing the counter, with the not of M70, or the run one shot to reset it? I'm thinking that the instruction was originally written as a block, but this doesn't come through correctly in the mnumonics. Attached are the mnumonics from the machine for this section, which is all I have, along with the resultant ladder, which I input as new. Basically, what I am looking for is if someone can enter the code as a joined block, which I do not have the ability to do, then export the mnumonic code to see if it matches. I suspect that it will not, due to the intracacies of the block... Does this make sense? Thanks. Jim Mnumonics_C660.xls Ladder_Medoc.pdf
  5. I'm looking for a schematic of a PCX-KIT1 cable, which is used with a F2-20GF1 adapter to connect to a Melsec F2-60 PLC?
  6. Attached is a clip from the program I am looking at. It looks to me like M572 will come on, when C660 is between 9-25, 7-29, 8-18, 24-34, and 42-44, which corresponds to M101, M102, M103, M104, and M107. The thing I don't understand is that it also looks like the count bit only turns on when I am not running, so I don't understand what increments the counter. Also, it seems that C660 would be reset each time M100 comes on, which is every index, which doesn't make sense? All I had to build this was the mnumonics, which I am guessing are not translating correctly, but I can't figure it out? HELP??? RawLadderCmp.pdf
  7. PID tuning - forced hot air

    I'm almost complete with a forced hot air PID system, in a very low flow application. I used P and I. An older Omron, C200HS PID instruction, with P at 600 and I at 100, no D. The system works perfectly. My problem is that I am trying to control a downstream temperature at around 1000 degrees, but the heater cannot exceed 1300, and I have about a 300 degree loss between the two points. I'm trying to find a solution from a controls standpoint, while my partner is looking at reducing the massive heat loss. Its only over about 12", but its not easy, at least for us...
  8. I have an old Melsec F2-60, that we are going to upgrade with a new PLC. The problem is that I can't get in to it and only have a list of the mneumonic code writen out and some of it doesn't make sense. Specifically, there is a counter, C660, which is set up as an up counter, that is being used to check positions of an indexing table. They are using a compare F670-(K43), to check the positions. What doesn't make sense is that they have several compares, one for example has the K1 value set at 7, with K2 set at 25, and they are looking at 572, I believe it is, which is the zero flag. My understanding of the zero flag is that it is only on when the current value is >= k1, and ,<= k2. This would mean for example that the one station is enabled when the counter is 7 or higher, which makes sense for starting station 7 on start up, but not stopping it after 25 indexes. I suppose the question is if I am understanding the compare and counters correctly in my assumptions? I haven't started to interpret the SFT in there yet, but I'm sure I'll have more questions when I get there... Thanks.