Welcome to our new forum
All users of the legacy CODESYS Forums, please create a new account at account.codesys.com. But make sure to use the same E-Mail address as in the old Forum. Then your posts will be matched. Close

Profinet with Siemens IO

lsislsis
2015-10-29
2015-11-17
  • lsislsis - 2015-10-29

    Is anyone that can help with connection of Codesys Raspberry SL or Codesys Win SL and Siemens IM155-6 Profinet remote IO controller ?
    I am trying but when i scan for devices from Profinet master controller it found the remote IO controller but without Identification number or wrong number.
    I can put IP, Station name but nothing else.
    If i use the "profineta" configuration and diagnose software from Siemens in the same PC i can work all functionalities of remote IO.
    Waiting for help.

    Regards

     
  • eschwellinger

    eschwellinger - 2015-10-29

    Hi,
    did you install the device XML for this profinet slave to the device repository (this you should get from the device manufacturer)?
    BR
    Edwin

     
  • lsislsis - 2015-10-29

    I have install GSD file but the ptoblem i think is before this step because at scan for devices we have part responce.

     
  • eschwellinger

    eschwellinger - 2015-10-29

    could you add the screenshot of the scan result?
    BR
    Edwin

     
  • lsislsis - 2015-10-29

    Here we are.
    The IM155-6 remote IO is direct connected to PC.

    Regards

    IMG: Profineta.png

    IMG: Profinet.png

     
  • eschwellinger

    eschwellinger - 2015-10-29

    Hi,
    could you attach the Profinet GSDML.xml device description?
    BR
    Edwin

     
  • lsislsis - 2015-10-29

    OK I have news.
    When i made connection from local network i can see it with Scan for Devices and i can do inserting the devices in my project.
    I don't know why works like this and not in direct connection because Proneta software works same with direct or local network connection.
    But again the Remote IO bus not running as you can see.

    BR

    IMG: Profinet_Loacal_Network.png

     
  • lsislsis - 2015-10-30

    Nothing change.

    IMG: Profinet_Loacal_Network_New_GSD_3.png

    IMG: Profinet_Loacal_Network_New_GSD_2.png

    IMG: Profinet_Loacal_Network_New_GSD_1.png

     
  • eschwellinger

    eschwellinger - 2015-10-31

    Hi,
    did you update your existing project by rightclick to the slave -> upate device (after installing this XML to the device repository?)
    or remove the the slave and reinsert by scan or by hand.

    BR
    Edwin

     
  • lsislsis - 2015-10-31

    I have delete the old GSD from repository and after i have installing yours.
    Then scan for device and reinserting.
    No deference.

     
  • eschwellinger

    eschwellinger - 2015-10-31

    Hi,

    then we need to check this error code in the Profinet Spec:

    BR
    Edwin

    IMG: StationState.jpg

     
  • eschwellinger

    eschwellinger - 2015-11-01

    Hi,
    another remark,
    could could you check if a sendclock with 4ms would solve the problem?

    BR
    Edwin

    IMG: Sendclock.jpg

     
  • lsislsis - 2015-11-01

    I have do it before.
    Nothing change.

     
  • lsislsis - 2015-11-15

    Response from Siemens Support:

    On the subject of the password STATION STATUS: DB810104
    To Development center where I referred for further analysis of your subject, tells us that the above code is not the Format of error messages generated by the IM 155-6 (It is in the form of text messages).
    We estimate that this code generated by the software whenever CODESYS advised to return to the third question to manufacturer.

     
  • lsislsis - 2015-11-15

    Hi again.

    After install of new version Codesys 3.5.7.30 i can work with the modification of GSD file from you.
    Please tell me how can i work if i have different GSD files for different modules to use.

    Can i made the modifications by my self or i need to ask you for every new GSD file?

    Regards

     
  • eschwellinger

    eschwellinger - 2015-11-17

    Hi,
    let me check to which version this will be solved and how to apply the workaround.
    BR
    Edwin

     

Log in to post a comment.