Tinker

MrPLC Member
  • Content count

    18
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Tinker

  • Rank
    Sparky
  • Birthday 03/03/53

Contact Methods

  • Website URL http://
  • ICQ 0

Profile Information

  • Location Home of the Indianapolis COLTS
  • Country United States

Recent Profile Visitors

1300 profile views
  1. 1747_DNS

    Well it turns out that all of these problems were caused by bad media. You gota luv devicenet............
  2. 1747_DNS

    1747-SDN
  3. 1747_DNS

    Fat fingers on my part.
  4. I have a 1747-SDN that is doing many different things that leads me to think it needs to be replaced. First the voltage is 33 VDC for supplying the flat media and I wounder if this is to high. Second I was installing a PE on the Flat media with the system down and when I got done and turned the system back on the problems started. I removed what I had done to see if had an effect on the system and it did not. Some background, about 7 months ago the system died and all I did to get going again was reset the card and it was off and running until now. I can not get into the the card and if I do it is a short period until I loose communications again. Each time I remove power and re aply it gives me something different that it did before. Some of the combination of the highlighted below will come up.
  5. Pin out

    Thank you....
  6. Any one know the pin out for the SLC500 RJ45 connection. I just need to know how this one end is wired so I can make a 2' cable to reach outside the cabnet. TIA
  7. Devicenet Messaging

    Question: Should these just be true rungs to the MSG?
  8. AB Cable needed

    Thanks for the help Ken and Bob. I went with the PC Card 1784-PCD with the 1787-PCABL cable. All is working great and much faster than using pass through on the SLC503. I ran out of memory on an 8k SLC503 so the next project is to swap it out with a 16k SLC503 and then back to the messaging project.
  9. What I have is a 1784 PCMK series B card for the lap top and I want to connect to the probe connection on the 1787-PLUG10R. What items do I need to make this happen?
  10. Devicenet Messaging

    Well it is the weekend so I must work on things such as motor installation and fixing guide rails and the like so I will start on the first part of next week and get back to you when I am done. Thanks for the information BobLfoot
  11. Devicenet Messaging

    Option 3 - A,B,C,D,E,F & G to A,B,C,D,E,F & G This would allow me to go from any one to any other one. The system I am working with was installed so communications could take place but no one has ever attempted to do so until now. I have just been working for this company for a few months and I an just now trying to piece together what was done and why.
  12. Devicenet Messaging

    net eni? I an not familiar with that one.
  13. Devicenet Messaging

    Thanks for the information Ken and rpraveenkum. What I want to do is DH485 useing program MSG instructions. I whish to talk from one CPU500 to another. There are 7 SLC 5/03 PLC's on the network at this time. I have been studying MSG instructions but fail to understand how to send a bit to tell one 503 that a conveyor on another 503 has stoped running and I want it to shut down the conveyors that it controls. Clear as Mud?
  14. Devicenet Messaging

    Did I say something wrong? I can reword the question if I need to, sometimes I do not state things just right.
  15. Devicenet Messaging

    OK Ken thanks for the help. Once again my overworked mind failed me.. I am trying to work with a DH485 system (see Atch). However the Master/Slave idea sure did get my mind running with some ideas. There is only one 1747-SDN on my network and it is on Node 1. Any way how about the DH485 route, any ideas anyone?