We have a “control PC” that double-checks production data received serially from a controller thereby avoiding doubles and other production errors.
What does your GT controller send?
This Log string will be used, not only as production log, but as product identification between the controller and the “control PC”.
Messages GT Controller to Control PC
LOGSTR# is the string selected in fileview, usually a number with leading zeroes. is the carriage return character (ODhex)
a) Production start: start,logstring,filename
Message: start,LOGSTR#,filename,< CR>
The control PC will answer back with ok or stop. See below
b) Key not found in database:
Message: ERROR,0,KEY NOT FOUND< CR>
c) Record produced: logstring. The point in time this is sent depends on whether the “@1st inkjet” in the machine display was checked or not. If checked at the first inkjet, otherwise at the last object declared in the machine.
Message: LOGSTR#< CR>
d) Error in reorder point: please note that it will send whatever text you entered in description
Message: ERROR,text in description< CR>
e) Product error: ERROR,Logstring,Errordescription,
Message: ERROR, LOGSTR#,error,. Set when stop button is pressed
e) Product Stop message: operator presses stop button
– Machine end message
If the operator presses the red button and stops the controller with products on the belt, the products will be reported as:
Message: ERROR, LOGSTR#, UNVERIFIED PERS
Message: ERROR, LOGSTR#, UNVERIFIED NOT PERS
Product # at a certain point in the machine
| Machine end
| | Inkjet
| | | PD1
Product # 1 2 3 4 5 6 7…
In above example, the report would contain:
ERROR, 3, UNVERIFIED PERS<MIC_CR>
ERROR, 4, UNVERIFIED PERS<MIC_CR>
ERROR, 5, UNVERIFIED NOT PERS<MIC_CR>
ERROR, 6, UNVERIFIED NOT PERS<MIC_CR>
Messages Control PC to GT Controller
m) Everything ok after start production. If this message is not received, the GT controller will not enter production
n) Exit. If this message is received, the GT controller will exit production with a hard stop
o) Stop. If this message is received, the GT controller will stop the feeder, stay in production
p) Restart. If this message is received, the GT controller will restart the feeder. Comes after message stop
q) Anything else is treated like a stop and what is received is logged for further examination.