MrPLC Admin
  • Content count

  • Joined

  • Last visited

Community Reputation

164 Excellent


About pturmel

  • Rank

Profile Information

  • Gender Male
  • Location Atlanta, GA
  • Country United States

Recent Profile Visitors

5974 profile views
  1. GT Designer doesn`t login in Simulation mode

    This is a holiday weekend in the U.S., so many of the most helpful people will be otherwise occupied.  If nobody answers tomorrow, you should probably ask your Mitsubishi distributor for help.  (Or not wait for tomorrow.)
  2. RTU-DNET Delta

    With the resources I linked, you now know as much as I about this combination.  The documentation obviously is oriented towards scanning this DeviceNet slave from a Delta PLC--you'll have to re-interpret that yourself to conform to Kuka's requirements as the master.  I don't know anything about that. You will certainly need a PC to DeviceNet hardware interface compatible with the software for that RTU in order to configure it.  I assumed you understood that, but maybe not.
  3. Did you go offline to reconfigure it?
  4. help troubleshooting 8 valve festo block?!

    Assume we cannot identify the model from a small picture.  Link to documentation?
  5. Automation Direct ViewMarq and Control Logix

    Modern Logix processors do not have serial ports.  An add-on card would be required.
  6. RTU-DNET Delta

    Configure to do what?  It is a DeviceNet Slave (so needs a DeviceNet Master to control it) and, through that, is a Modbus Master for Modbus RTU slaves. You probably need to start here: (Or other translations.)
  7. I'm not familiar with the Fuji product line, but Rockwell expects all peers to use EtherNet/IP, either as I/O targets, or using Rockwell's supplemental tag read/write message services. Can you share a link to the product documentation for the Fuji model you are using?
  8. Are you using the same version of CCW as the original programmer?
  9. "See the code" ?  Do you mean "see the live data" ?
  10. On modern Logix hardware, you can monitor all connections via the built-in diagnostic web page.
  11. Are you sure the original programmer downloaded the source code to the controller?  If they deliberately did not, you will need to rewrite from scratch.
  12. There's several.  The embedded service packet carries multiple nested requests/replies.  Its first data word is the quantity.  Then, a word for each embedded request/reply containing the byte offset from the beginning of data for that embedded request/reply.  From there, decode a reply as usual (byte echo of service with high bit flipped, reserved byte, status byte, byte for extra status length...).
  13. The embedded service errors are between the PC and PLC, not in your PLC to device comms.
  14. The originator is the device making the request--the PC in this case. It is quite possible that the presence or absence of some data from your devices changes the data sizes returning from these requests to the PLC, and eliminating these size "errors".  Is this only RSLinx on the PC?  (I wouldn't expect Rockwell to screw up something so fundamentally their design.  Or maybe I would. )
  15. Spot checked some more.  Same pattern.  I think the originator's program is too dumb to forecast the expected return sizes to avoid large responses in return packets.  If a commercial package, can you name them so I can shame them?