Siemens S7-1200 Profinet

agwells
2018-08-14
2020-12-04
  • agwells - 2018-08-14

    I am setting up a system using Codesys V3.5 on a Raspberry Pi as a Profinet controller getting data from a Siemens S7-1200 enabled as an I/O device.

    I have imported the GSDML file from the Siemens TIA development environment and all the expected data blocks are identified and the PLC and Codesys say that everything is OK but I am not getting any data from the PLC, all values are at 0.

    I have looked at the network using wireshark and I see LLDP packets from the PLC but no data, I am not new to PLCs but I am to Profinet so I understand that this is my error, but if anyone can point me in the right direction of things to check then I would be very grateful

     
  • sho - 2018-09-05

    Is the PNIO status of the device 0x81813F02 (DCP no RealStationName)? If so, there could be a mismatch in device names. Your project should reflect what you get through the LLDP/DCP packets from the device.

     
  • dFx

    dFx - 2018-09-28

    Did you checked that Inside TIA portal you are sending values in profinet IO addresses ?

     
  • rayapati - 2020-05-01

    Hi
    I am also getting the same error-
    Station Status : 81813F02 - DCP no RealStationName
    My environment is Codesys and raspberry pi 3b+ as PLC. For this i am using codesys raspberry pi sl runtime package in demo mode.

    Earlier i saw the communicaton between PLC and IO device.
    But today i saw this the error it was mentioned .
    Can any one suggest whaty could be the reason.

    Regards
    Rayapati

     
  • rayapati - 2020-05-01

    Hi
    I am also getting the same error-
    Station Status : 81813F02 - DCP no RealStationName
    My environment is Codesys and raspberry pi 3b+ as PLC. For this i am using codesys raspberry pi sl runtime package in demo mode.

    Earlier i saw the communicaton between PLC and IO device.
    But today i saw this the error it was mentioned .
    Can any one suggest whaty could be the reason.

    Regards
    Rayapati

     
    • asivakov - 2020-12-04

      The reason can be in watchdog timer - function to detect hunged slave and restart it. Try to set bigger value, if you ain't use RT. Also, pay attention, device name of slave on master side should match with device name of slave it-self - this is necessary.

       

      Last edit: asivakov 2020-12-04

Log in to post a comment.