Filter
Top Products
4. CONTROL OF VIX DRIVES 71
Reporting System Information During Code Development
Whilst developing a program using EASI-Tools, it is likely that certain blocks of code when
downloaded to the drive will return an *E error code. To analyse the cause of the error you
can make use of EASI-Tools Status report window which, when read, will report back the
cause of the error. For example, selecting status report ‘User’ following a *E may report
back ‘Label of this name not defined’.
Within EASI-Tools a system variable can be read using the status report window or using the
report command directly from the terminal window (For example 3R(ST)). Using this style of
report an immediate response will be returned which will not be saved within the program
code. If you wish to save the response, use the single byte version of the report command,
that is 3R(ST1), 3R(ST2), 3R(ST3) or 3R(ST4) depending upon which byte of the variable
you wish to capture.
If the indexer is waiting on a trigger command, you can still send an interrogation command
such as 1R(RB), 1R(DF1), 1R(ST1), 1R(UF1), 1IS, 1O, 1A ......and a report will be returned.
However, if a buffered command is sent, such as G or 1A10, then all future interrogation
commands are buffered, apart from 1R(RB), 1R(DF), 1R(ST) and 1R(UF).