Zitat von T.Mmop im Beitrag #3
The problem is we would now have to do this for each individual signal of which we have many.
Is it not possible for the software to read these signals from the AUXDATA file where the signals are named and defined.
For example we have the following output signals defined as:
N_OX1 "CLR ADV TXFR"
N_OX2 "CLR RET TXFR"
N_OX3 "CLR TO UNCLAMP"
is KIDE not able to take the signal number and name and use that to define the signal? OX being for the output and WX being for the input?
K-IDE's way is in oposition to that. You define Signals as REAL variables and then use it in your source as "named signals". K-IDE will generate the list of variables in AUXDATA to allow access for the endcustomer.
Zitat von T.Mmop im Beitrag #3
Another thing noted is that I am unable to define the signal in IDE with spaces, but the robot is able to read signal name with spaces?
most of our signals are named with spaces in the characters, and if i now define the signals without spaces in KIDE it overwrites our existing signal names on the robot when monitoring
As K-IDE uses REAL variables as signal names, spaces are not allowed that names. Please keep in mind: named signals are used to allow easier programming. They are not mainly used to be viewed in status windows. Therefore the names should fit to the AS naming convention (15 chars, a-z, underline, dot).
Zitat von T.Mmop im Beitrag #3
When i use CRTL+SHIFT+F5 to download from the robot, Only the items in bold is what was downloaded.
None of my signals are read from the robot backup, including the internal and system signals.
To receive signals from the robot as signals and not as REALS, the robots AS data must contain the "AS documentation" that tells K-IDE which REALS variables are difined as signals.