CtrlX cannot enter startup parameters

[Ofir]

Hi,

I need urgent assitance!!

I've added EtherCAT slave to my application.

When I'm trying to enter data in the startup field as marked below it does not work. If I click once on the field it does not provide the option to change the value. 

If I double click on it, window will open to enter data but after changing the value and trying to click ok nothing happens - the window will not close.

[CodeShepherd]

As it looks like you the used data is a byte array you have to correctly set the parameter you like to insert as there is no intuitive help for creating such arrays. Could you share a picture on the window that opens on double click with all your inserted data?

[Ofir]

Hi  CodeShepherd,

Thanks for your reply.

First please note that the data type is determined by XML file of the EtherCAT slave we are using. (see below).

I'm not next to the system right now but when you double click and the window opens the data that is showing is :

data type "byte array", bitlength "72", Value:"16x00,16x00,16x00,16x00,16x00,16x00,16x00,16x00,16x00"

If you try to change the 00 to other value , when click Ok to close the window nothing happens, the window stays open.

I noticed that this issue occurs with other fields as well - The main the difference is that with other fields, you can click to edit the value directly from the table I captured in my previous post while this specific value does not give you this option. (When you click once on other fields, the value becomes "selected" and you can edit it).

[CodeShepherd]

Could you please add the device description file that you are using?

[Ofir]

Hi,

Attached.

[CodeShepherd · Accepted solution]

Working fine at my side. Which version of ctrlX WORKS are you using? I am using 1.16.0.

ctrlX IO Engineering insert startup parameter TigoMaster

ctrlX IO Engineering startup parameter TigoMaster

[Ofir]

Thanks for your testing!!

I will double check my ctrlX version and test again.

[Ofir]

Thank you very much!!

Indeed using version 1.16.x the issue is solved.