tgorupMFT

MrPLC Member
  • Content count

    13
  • Joined

  • Last visited

Community Reputation

0 Neutral

About tgorupMFT

  • Rank
    Sparky

Contact Methods

  • ICQ 0
  1. Mickey, that post you're refering to was the one I looked at, and for the OSR, it was already in the program and I'm not sure if I should take it out?
  2. NewCounter.bmp Ok, thanks for the replies, here is what I got so far, could you take a look at it and see what you think. The thing is, in all those examples they were using the input, is it ok for me to use the output to start the timer like I did.
  3. Ok, one of the triggers for that output is that prox, and that's the only thing that is flickering. It's not an every time thing just enough to throw the counts off. The shortest cycle time for the table to turn again is about 1 min. So a few second timer would work great. Could you show me where to put the timer in? Thanks.
  4. Counter.bmp Hi I have a problem with a counter on our robitic cell, the cell has a table that turns to unload and when the unload program is called the counter adds two each time. The problem is the prox switch that sees which side of the table is there sometimes flickers, and when it does the counter will count twice, I added a pic of the line for the counter above...
  5. Never mind, I just seen a post on the AB knowledgebase that states the firmware revisions 1.04 - 1.07 cannot be upgraded by the Firmware Upgrade Utility. :(
  6. I had a PanelView go out the other day and bought a used one off of Ebay, when I try to load my program to it, it tells me it's not compatiable with this ver.. So I go to upgrade the firmware on it and I can not connect to it, It always tells me to reset the Panelview but it never sees the reset. Im using a 1747-UIC to try and connect to it, could that be whats holding me back. Thanks in advance...
  7. Dh485 Network Damage?

    Ok, Im not sure which one is the phoenix plug, so this is what I did. On machine 1, I unplugged the DH485 plug and hooked up the UIC and I could see that machines SLC and Panelview, if I then plugged up the DH485 plug I get a bunch of garbage info comming up in linx and nothing connected, not even the SLC or Panelview that was just connected. On Machine 2 it did not matter what was plugged in or unplugged, if I have the UIC plugged into the AIC I can not see anything at all. Those were the only 2 machines I tested.
  8. I hope someone can help me out here. Here is my equipment configuation. We have 5 AB SLC 5/03's all connected to 1747-AIC Link Couplers that are all networked together. Then the office PC was connected to a 1747-UIC. At one time everything was working fine, from the PC you could see and talk to all 5 SLCs and 4 panelviews. A person working behind the office shorted out the Cat5 cable that was connecting the pc to the DH485 network, and now no matter which 1747-AIC I plug into, in linx various slcs pop up saying connected for a sec then have a red x on them. The weird thing is the PLCs are still able to talk to each other and our equipment is working fine. I did replace the 1747-UIC USB adaptor, from the wire shorting out it did screw that up, but still cant see anything from it. Could all the Link couplers gone bad? Im lost here.
  9. What do I need to do to, if I can add more timers. They go up to T4:51, is there anyway to get more? Thanks
  10. help with a fault on SLC-5/03

    Thanks everybody for the help. I did add the above code into the program but I'll have to wait and see if it works out, I was able to get the system back up and running by doing a "load from eeprom". Thanks again for all the help. Tom
  11. help with a fault on SLC-5/03

    Ok, here is what it said. Major Error Halt S:1/13= 1 Math Overflow Trap S:5/0= 1 Error Description A minor error bit is set at the end of the scan. Refer to S:5 minor error bits.
  12. Hope someone here can give me a hand, I'm new to this stuff and do not have any real training, so go easy on me. Ok, here is my problem. I got 5 AB SLC 5/03 systems running that are networked together by DH-485 link couplers. 4 of them are robotic cells the other is a parts conveyor. All of a sudden one of the robot PLCs will fault and shut down. It only happens when its time for it to unload into the parts conveyor, before then everything is fine. We had this problem once befor and the SLC 5/03 CPU was swapped out and it worked again, well I tried that this time and still the same thing happens. Does anybody have any suggestions? Thanks