PLCGurus.NET Live & Interactive Forum PLC Questions and Answers Siemens, SIMotion, Profinet Siemens S7-300 To CoDeSys WIN V3 PLC Via Profinet

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #4605
    Liam Bee
    Karma: 21
    Rank: Padawan

    Hi All,

    I’ve been messing about with a S7-300 and CoDeSys WIN V3 PLC (which is a soft PLC running in windows incase you didn’t know). I am trying to interface with the S7-300 via Profinet.

    I have everything configured as I would see correctly, but no data is passed between them. The WIN PLC is showing that communication is working and healthy (if I break the connection between them, the WIN PLC immediately reports a BUS fault).

    What I am unsure about is the “I-Device” configuration and if I have done that correctly. So here’s the steps I took:

    1. On the S7-300 in the hardware manager, turned on the option for I-Device
    2. Set up an input word (700 – 701). This was given submodule address 1000 automatically
    3. Set up an output word (700 – 701). This was given submodule address 1001 automatically
    4. Exported the I-Device GSD in to CoDeSys
    5. Created a Profinet slave device with the GSD file and pointed it to the ethernet port
    6. Mapped variables in CoDeSys and Step 7 to the relative locations for Read / Write data

    The above results in a connection being successfully established by the PLCs, but data is never communicated.

    I am trying to write a value of W#16#1000 to PQW700 in the S7-300, but nothing is ever received by  the WIN PLC.

    I know that the Soft PLC can see the S7-300, and I also know that I can definitely action network commands through this PLC as the same setup to a Schneider TM251 over Modbus TCP works without issue (although they are both CoDeSys based).

    It’s a long shot, but has anyone ever done this before? I only want it for a quick and dirty commissioning setup so I have something to test against



    Grace Burns
    Karma: 23
    Rank: Padawan
Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.

This website uses cookies.