Understanding of numbers in IOSYS.INI

  • After reconfiguring post the files iosys.log and pfbms.log (don't post screenshots!, post the files).

    I attached the ini and the log files. I hope you can help me.(i saved it after reconfig)

    Thanks in advance!:)

  • AD
  • The pfbms.log show's normal start from the Master CP. No errors. Say's nothing about slaves....

    iosys.log show's 1 Byte Input mapped.


    In a picture from the NCM-Manager, it shows mapping from 32Byte INPUTS and OUTPUTS.




    Code
    [DRIVERS]
    PBMASL=11,pbmsInit,pfbmsdrv.o
    [PBMASL]
    INB0=3,0,x32 ;$IN[1]-$IN[256]
    OUTB0=3,0,x32 ;$OUT[1]-$OUT[256]


    Maybe, you have seen this doc:

    tn092-3.pdf (exorint.net)


    Turck uses a Plug-in module from EXOR. Has no Hardware-DIP-Switches for Mac-ID.

    In the NCM-configuration, you use MAC-ID 3 for the modul.

    You're sure, the modul has MAC-ID 3 ?


    Wired hardware really correct?

  • Try to change the line in pfbms.ini to:

    WAIT_FOR_SLAVES=1


    But if it is true, that the Turck Panel uses the EXOR hardware, then I doubt that you will be successfull with controling the panel with the Kuka bot. Had a short look onto the documentation of EXOR, they use a special FB for communication to the panel. So I think the panel will use a higher protocol, not only I/O. But Kuka Profibus only supports simple I/O protocol.


    Edit: After reading some sheets from Turck: It may be possible that you must configure the display with Codesys before using the profibus module.

  • Thanks for your help sjx  hermann !


    I attached the files again. I changed everything what you told me. Change the mode id in TX_VIsual pro(As you said hermann i have to configure firstly in the turck system which is visual pro).If you would like to use turck, u have to write the program in codesys, but the visualization and the dp slave communication side is in the visu pro.

    The pfbms.log show's normal start from the Master CP. No errors. Say's nothing about slaves....

    iosys.log show's 1 Byte Input mapped.

    I write in what you advice me and now its correct!(see in the attachment)

    i reconfig everything again and the robot write me the same problem.
    I contacted the turck, if we set everything up with them and the system still doesn't work, I'll be forced to contact KUKA...

    i am blessed for your help guys and thank you for not giving up!

    Cheers!

  • Maybe you have to go a step back....


    In such a situation, I usually test the KUKA side first with a test.

    I'm doing a project where I connect master and slave of the CP5614.

    Then i am sure that I have no hardware or driver problems on KUKA side. Cable will also be tested.

    You can do it by exchanging the moduls in the NCM Project and activate the slave in the pfbms.ini.

    exchange the adress in iosys.ini to 127

    Edited once, last by sjx ().

  • Dear sjx,


    I am getting losing my faith! :D :'(

    I tried to do a new project where the robot(CP5614) is a slave and the hmi plc is the master(as you said try to exchanging the moduls), but i got in my mind the profibus dp module is a plug in slave modul which can't be a master that's why i cant exchange them... :'(


    I hope i understand right what you advice me. If don't, would you explain it better? :)


    Thanks is advance!

    Cheers

    Files

    • error.zip

      (3.16 MB, downloaded 1 times, last: )

    Edited once, last by Mate_271 ().

  • SJX made a different approach.

    Make a connection from Master connector to Slave connector on Robot. Then configure the robot as master to the slave part of the robot.

    The HMI is not used at this test configuration. It is only a test if cabling and principle work flow of configuring is correct.

  • I tried to do a new project where the robot(CP5612) is a slave and the hmi plc is the master(as you said try to exchanging the moduls), but i got in my mind the profibus dp module is a plug in slave modul which can't be a master that's why i cant exchange them... :'(

    CP5612? I'm not aware that KUKA ever used that card -- KRC1s and KRC2s used the CP5613 (rarely) or CP5614 (usually). What card does your robot have installed? The "stock" CP5612 from Siemens, as I recall, is a single-port card.


    As I understand it, a Profibus port cannot operate as Master and Slave at the same time. Hence why the CP5614 has two ports -- one acts as a Master, the other as a Slave. If your Profibus card has only one port, I don't think there is any way to accomplish what you are attempting.

  • CP5612? I'm not aware that KUKA ever used that card -- KRC1s and KRC2s used the CP5613 (rarely) or CP5614 (usually). What card does your robot have installed? The "stock" CP5612 from Siemens, as I recall, is a single-port card.


    As I understand it, a Profibus port cannot operate as Master and Slave at the same time. Hence why the CP5614 has two ports -- one acts as a Master, the other as a Slave. If your Profibus card has only one port, I don't think there is any way to accomplish what you are attempting.

    I am so sorry SkyeFire, i write it wrong. its CP5614.. :/ Others knew it because we are discussed it many times earlier, but i appreciate your help.



    SJX made a different approach.

    Make a connection from Master connector to Slave connector on Robot. Then configure the robot as master to the slave part of the robot.

    The HMI is not used at this test configuration. It is only a test if cabling and principle work flow of configuring is correct.

    Thanks hermann for your explanation, it looks like I'm still in my infancy with the configuration... :/ I will test it!

    Edited once, last by Mate_271 ().

  • Dear Forum,


    I find tihs pdf, which I hope will help a lot to everybody(How to make profibus communication) http://fs1.gongyezaixian.com/d…2015-4/20150410083344.pdf


    To this topic:


    In this pdf describe in details too(side 130 in pdf) how to make that test configuration what you told to me hermann and sjx. The terminator in master side is on and the terminator in slave side is off. I run that transfer configurator program and make a transfer entry(side 131) and modify iosys.ini-> pfbms and pfbms.ini, but i don't understand clearly how should i make it properly.


    I attached the necessary documents (which hermann teached to me :D )

    Logs show we got some error, which the pdf shows too, but does not describe the solution. :(


    I hope you can help me what i am doint wrong!:( Thanks in advance guys!


    Cheers,


    Mate

  • The terminator in master side is on and the terminator in slave side is off. I run that transfer configurator program and make a transfer entry(side 131) and modify iosys.ini-> pfbms and pfbms.ini, but i don't understand clearly how should i make it properly.

    On each end of the Profibus the terminator must be on. So if you only have a connection from master to slave of the robot on master AND slave terminator has to be on.

    Don't use mapping, set MAPPING_USED to 0. With mapping you multiply the fault sources (I never ever used mapping).


    Use following entry in iosys.ini for connecting I/O in both directions.

    Code
    [PBMASL]
    INB20=127,0,x1
    OUTB0=3,0,x1
    OUTB20=127,0,x1
    INB0=3,0,x1

    In pfbms.ini [SLAVE] section setting

    Code
    STANDBY=1

    makes slave connection more robust.

    Post your NCM-Manager project.

  • Wow hermann, really appreciate your help!


    I am going to change every value to that what you write to me. 1 more thing what i don't understand.


    sjx told me this earlier:

    You can do it by exchanging the moduls in the NCM Project and activate the slave in the pfbms.ini.

    exchange the adress in iosys.ini to 127

    And now you advice too this to me. Although the pdf advice the transfer configuration, then it doesn't necessary for us. I attach the NCM managger ldb file, but i couldn't exchange the moduls, because the gsd file which is attached to the NCM managger project can be slave only.(UniOP) Can you help me how should i exchange them? As i understand i should exhange the UniOP to CP 5612A2(but as i said it can be slave only :( ) or should i add a slave CP5614 modul and delete the UniOP slave?

  • SOLVED!!

    Everything what i have done was good. The error came from the HMI PLC. As is said earlier it has a visualization program(TX VisuPro), where we just run the program and all KRC error just disappeared... Thanks for your help guys, i will watch the comments and if i can help too i will!!!


    Cheers

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account
Sign up for a new account in our community. It's easy!
Register a new account
Sign in
Already have an account? Sign in here.
Sign in Now