51 lines
3.4 KiB
Markdown
51 lines
3.4 KiB
Markdown
|
|
||
|
|
FB2021
|
||
|
|
![[Pasted image 20250213154732.png]]
|
||
|
|
|
||
|
|
![[Pasted image 20250213154910.png|638]]
|
||
|
|
|
||
|
|
![[Pasted image 20250213154847.png|634]]
|
||
|
|
|
||
|
|
(3) is our trigger if the data changed, with this is possible to SET the (1)
|
||
|
|
(1) is the TG10 Trigger to send the data with FB189
|
||
|
|
|
||
|
|
But the FB189 has a automatic mechanism to re-send data with the ENABLE_REPEAT
|
||
|
|
|
||
|
|
![[Pasted image 20250213155258.png]]
|
||
|
|
|
||
|
|
You can check this counter (2) to see the number of re-send like "IDB2021_Autefa_Vetro_Line_25_Communication_DB".TG10_TG11.SEND_COUNTER
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
Here's a detailed table of telegrams exchanged with AUTEFA, including their required information and validation conditions:
|
||
|
|
|
||
|
|
| Telegram | Direction | Purpose | Main Content | Required Information & Validation |
|
||
|
|
|----------|-----------|----------|--------------|----------------------------------|
|
||
|
|
| TG10/TG11 | VETRO → AUTEFA | Production Information | - Filling line<br>- Active batch ID<br>- Active batch target (thousands + units)<br>- Active Article Variant ID<br>- Next batch ID<br>- Next batch target<br>- Next Article Variant ID<br>- Next+1 batch information | - Filling line must be valid (11-16)<br>- Active batch targets must be >0<br>- Article Variant ID must exist in SKU list<br>- Batch IDs must be 12 characters<br>- Targets must be split into thousands/units |
|
||
|
|
| TG20/TG21 | AUTEFA → VETRO | Line/Product Change Request | - Filling line<br>- Tray Loader (21-28)<br>- Requested Article Variant ID<br>- Accept/Reject status (TG21)<br>- Error code (TG21) | - TL must be available<br>- Article Variant ID must match current/next batch<br>- Conveyors must be in automatic mode<br>- No bottles required signal must be present<br>- Error codes:<br> 0 = No error<br> 1 = Conveyors not in auto<br> 2 = Bottle type mismatch<br> 3 = No bottles required |
|
||
|
|
| TG30/TG31 | AUTEFA → VETRO | End of Batch | - Filling line<br>- Batch ID<br>- Article Variant ID<br>- Tray Loader | - Valid batch ID<br>- Active batch must be running<br>- TL must be assigned to line<br>- Article Variant ID must match current batch |
|
||
|
|
| TG40/TG41 | VETRO → AUTEFA | Speed Update | - Filling line<br>- Line speed (1-100 in steps of 10) | - Speed must be between 0-100<br>- Speed changes limited to ±10 per update<br>- Line must be running<br>- No alarms active |
|
||
|
|
| TG50/TG51 | VETRO → AUTEFA | Activate Next Batch | - Filling line<br>- Batch ID to activate<br>- Article Variant ID | - Next batch must be defined<br>- Article Variant ID must match next batch<br>- Current batch must be completing<br>- Line must be ready for changeover |
|
||
|
|
| TG60/TG61 | VETRO → AUTEFA | Request Unloaded Bottles Count | - Filling line<br>- Batch ID<br>- Unloaded bottles count (TG61) | - Active batch must be running<br>- Counters must be operational<br>- Regular updates (typically every 60s)<br>- Count split into thousands/units |
|
||
|
|
|
||
|
|
Additional Notes:
|
||
|
|
- All telegrams have:
|
||
|
|
- Fixed 100-byte length
|
||
|
|
- 40-byte standard header containing:
|
||
|
|
- Message length
|
||
|
|
- Telegram number
|
||
|
|
- Client ID
|
||
|
|
- Timestamp
|
||
|
|
- Error codes
|
||
|
|
- Data integrity checks
|
||
|
|
- Network timeout handling (10s default)
|
||
|
|
- Retry mechanism (3 attempts)
|
||
|
|
|
||
|
|
Communication Rules:
|
||
|
|
- Even-numbered telegrams are requests
|
||
|
|
- Odd-numbered telegrams are responses/acknowledgments
|
||
|
|
- Each telegram requires acknowledgment within timeout period
|
||
|
|
- Repeated telegrams must maintain same header info
|
||
|
|
- Error handling must be implemented for all scenarios
|
||
|
|
- Data type conversions handled on VETRO side
|
||
|
|
- Article Variant IDs used for simplified bottle type identification
|