Balluff BVS ID-M1280-F1 Series, Configuration Manual

Page: 229 / 342

BVS ID-M1280xF1-xx-xxx
english 55
•
•
•
•
Length in bytes Structure Value Description
2 UINT16 04
hex
User data length in bytes
2 UINT16 Result code
2 UINT16 The currently set Inspection ID
Result code type Result code Description
OK 00
hex
The inspection program change has been successfully
completed.
NOK Busy 16
hex
The application is currently in a mode in which requests can
not be processed (ready status is curently false).
NOK Inspection Error 1A
hex
An error occured while loading the inspection program due to
one of the following reasons:
Changing to an inspection program with ID 0 is not
possible via communication interfaces.
The inspection program with the given ID does not exist.
The maximum amount of inspection programs has been
exceeded, a change is permitted until inspection programs
are being deleted.
The inspection program is corrupt or the application ran
out of memory during load.
Example 1 (successful change):
A request to change to the existing inspection with the existing ID 5.
Message from the client to BVS ID : 31 00 02 00 05 00
BVS ID responds to it with: 31 00 04 00 00 00 05 00
The bytes "00 00" indicate that the inspection change was successful.
Example 2 (failed change):
A request to change to the non-existing inspection with the ID 7.
Message from the client to BVS ID : 31 00 02 00 07 00
BVS ID responds to it with: 31 00 04 00 1A 00 01 00
The bytes (1A 00) indicate that the change was not successful. The active inspection program is contained in
the last two bytes: (01 00), representing the active Inspection ID of 1.
For information about the reason of a failed Set Inspection ID request, the user is referred to the system
logs which can be viewed by means of the System Settings, tab System, of the Webinterface.
NOTE
