CS8C configure profibus dio in iomap.cf

    • New

    Hello,

    I have a CS8C controller with a TX60 robot arm and would like to use it without MCP. The controller has remoteMCP on it.

    To do that there needs to be a configured iomap.cf. In it, I uncommented the code and made it as follows:


    Code
    remoteMoveHold = io:BLOCKA_IX1



remoteEnablePower = io:BLOCKA_IX0


    The thing is, the controller says that io:BLOCKA_IX1 is not a dio. I tried various things, like "BLOCKA_IX1", without the "io:" part, as well as "BLOCKA-IX1" to no avail.

    The question I have is, is it possible to configure a profibus dio for a remoteMoveHold and remoteEnablePower and if so, how?

    Thanks!

    • New

    Update:

    It seems to have something to do with STARC, SRC or MCP versions. The other robot works fine, and this one does not work even if I put usrIn0 as input.

    I would have done a STARC and SRC version update if Staubli did not destroy the technical support library and with it the compatibility tables.

    • New

    Hi ,

    The syntax is definitively without the io: prefix.

    The setting of iomap file has nothing to do with STARC or MCP version.

    The SRC version affects only the iomap file. For SRC versions <s7.xx the file is called iomap.cf and for version s>=7.xx it is called iomap.cfx.

    Since you've got a message in the errror logger, you probably have SRC version <s7.xx


    Can you post the content of error logger (/log/errors.log) to check if one can see more valuable info on your issue ?

    REgards.

    • New

    klausi

    Of course I can, here is the relevant part, ignore the dates, they are not set properly yet.


    • New
    Quote

    The question I have is, is it possible to configure a profibus dio for a remoteMoveHold and remoteEnablePower and if so, how?

    How does it work?


    The principle is very simple: the keys of the Stäubli MCP are simulated by digital or analog inputs. A configuration file allows the assignment to each key of a signal replacing the key when the runtime license is activated. The input signals can be originated from the BIO or MIO boards, a field bus or even a Modbus TCP "software" configuration.



    The "Remote MCP" software is activated when the Stäubli MCP is replaced with the plug delivered with the controller. As soon as the Stäubli MCP is reinstalled, the software is deactivated and the Stäubli MCP takes control of the arm without the need to reboot the controller, thus making maintenance operations easier.

    • New

    Hi aknezevi


    I confirm the explanation of Galet.


    This indeed stange that you cannot link to usrIn0/usrIn1.

    Maybe, they are out of order. Do you see these inputs in ControlPanel->I/O->UserIO ?

    Have you tried with fIn0/fIn1 ?

    • New

    Hi,

    Your SRC is 6.6.4 so your file is correct.


    I try on emulator with this configuration in the iomap.cf : remoteMoveHold = b2In0

    and have the result, in the logger : RemoteMoveHold linked to b2In0 !


    On modbus :

    I try on emulator with this configuration in the iomap.cf : remoteMoveHold = mbItem1

    and have the result, in the logger : RemoteMoveHold linked to mbItem1 !


    So, the comment at the begining of file is correct :

    // To activate a io mapping, remove the comment marks '//'

    // and replace the description with the name of a system input or output,


    Perhaps, on the real controller (I don't have it), you need do configure other signal to for safety reason.

    Have a nice day...

    Edited once, last by Galet ().

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