MrPLC Member
  • Content count

  • Joined

  • Last visited

Community Reputation

14 Good

About Mark-

  • Rank

Contact Methods

  • Website URL

Profile Information

  • Gender Male
  • Location Houston
  • Country United States

Recent Profile Visitors

5585 profile views
  1. Vista support for NS-Runtime

    Are you asking someone to commit a crime?
  2. OK, I asked because the specification is where I find solutions to most returned error codes. Word search (and patience) is your friend.
  3. You are welcome. Do you have the CIP specification to read?
  4. I do not know if that is the issue. I see the result "connection in use or duplicate forward open" and know I code so the connection serial number is unique across all connections.
  5. Are you using a different connection serial number?  
  6. You are welcome. You can use other port number yes. Is the slot (controller) part of the connection path?
  7. Ping from PLC

    And to add not all devices support/reply to "ping" request.
  8. DF1 Protocol For Bit Read

    You are welcome. From the DF1 manual: For higher addresses, setting this byte to FF expands this field to three bytes total. Use the second and third bytes for the expanded file address (low address byte first).
  9. You are correct. Two reads, both using the same CIP sequence count value (1). The controller sees a duplicate read and responds with the same reply as the first message.  
  10. > The problem we are facing is the PLC doesn't send out a response of more than 240 bytes, You are only requesting data for 11 reals. Ask for more tag data and I assume the device will reply with more data, up to the requested specified buffer size, in the large forward open request.
  11. A WireShark capture file, not a screen capture. Not the size request for the forward open. The actual data sizes in the read service request. Repeat the actual WireShark capture file from register session to unregister session. > I guess there is a limitation on the number of Multiple service packet requests? No.  
  12. Post a capture file. Screen shots do not show the data size you are requesting.
  13. DF1 Protocol For Bit Read

    There exist a finite number of reasons a command does not work. 10 02 01 29 0F 00 40 00 AB 02 20 85 FF 00 00 00 01 00 01 00 10 03 26 4B  
  14. DF1 Protocol For Bit Read

    > I'm just trying to understand the variation and how/why commands are changing. I assume you are reading the specifications? Do you have a binary file 32 in the the PLC?