Modiconbob

MrPLC Member
  • Content count

    50
  • Joined

  • Last visited

Community Reputation

2 Neutral

2 Followers

About Modiconbob

  • Rank
    Sparky

Contact Methods

  • Website URL http://www.deltaautomation.com

Profile Information

  • Gender Male
  • Location Richmond, VA
  • Country United States

Recent Profile Visitors

2976 profile views
  1. modicon 484 automate

    Yes, there are several options available.Wasan is correct, and this unit/technology is over 40 years old! The P180 was never able to record/copy the program, it was only a programming console. The P190 had both capabilities. To back up the existing program, it will require a J470 interface, a cable and PC/computer that is capable of running a DOS program. I have all of that equipment and we perform these operations still to assist clients in upgrading their processes. You may contact me directly via email to discuss some options to get this operation done for you. bobculley@deltaautomation.com   Thanks, ModiconBob    
  2. Modicon 484

    Yes, there are several options available. Crossbow is correct, this unit/technology is over 40 years old! The P180 was never able to record/copy the program, it was only a programming console. The P190 had both capabilities. To back up the existing program, it will require a J470 interface, a cable and PC/computer that is capable of running a DOS program. I have all of that equipment and we perform these operations still to assist clients in upgrading their processes. You may contact me directly via email to discuss some options to get this operation done for you. bobculley@deltaautomation.com   Thanks, ModiconBob
  3. The Proworx32 should be used to update the traffic cop/ memory map in the PLC for sure.  That should correct how the STAT block responds to the card, eliminating the error.  
  4. Communication

    Yes, the baud rate is excessively high. What cable are you using? I am assuming that you have no duplicate addresses. What is the terminating resister value? What is the resistance across the network cable?
  5. Modicon 984

    That is correct. But even on the "master" rack  you do NOT need to kill power to replace an I/O card.
  6. The original 200 series with the "knurled pins" allowed for maximum I/O flexibility, but some folks didn't use common sense when setting them as you found out!
  7. Crossbow, you are correct! NXT will NOT communicate with a 484. A 484 is asynchronous and also needs a hardware asynchronous to serial convertor (Modicon J470).
  8. Modbus Plus to PC

    Collinsd70, you are correct. They work well but are costly!
  9. Once the processor has lost its' memory, the comm addresses default back to 1 for MB & MB+. Once the program is reloaded and the processor is started to Run, the addresses will be set by the newly reloaded program.
  10. What address are you attempting to connect? If the unit is defaulted, it has returned to address 1.
  11. Modicon 984

    You do not need to kill power to replace an I/O card. You can replace it "hot".  You only need to kill power on the processor, remote I/O interfaces, power supplies etc. The J890 gets updated from the processor on power up. nothing to reload there. Also, no programming changes for replacement card.
  12. OK. Sounds great! I think the other way, I think the Modicon is the best....of course I worked for them for about 20 years too! LOL You are welcome to contact me directly at my office via email bobculley@deltaautomation. Thanks! Bob
  13. Be certain that your communication parameters are set up correctly. (serial parameters,UBS, ethernet, etc). To just download, go to direct to online (dto), once online, you should be able to download the program. Let me know if you need more help.  I can get on the phone with you if needed. Good luck.
  14. What type of trunk cable (RG-6-RG-11-quad shield?) are you utilizing? How many drops are on the sytem? Do you have a rough idea of the total length of the cable? What test equipment have you used to trouble shoot? Bob www.deltaautomation.com bobculley@deltaautomation.com
  15. Set the port that you are communicating to the programming terminal as a slave.