3.4 KiB
3.4 KiB
FB2021
!
!Pasted image 20250213154910.png
!Pasted image 20250213154847.png
(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
!
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 - Active batch ID - Active batch target (thousands + units) - Active Article Variant ID - Next batch ID - Next batch target - Next Article Variant ID - Next+1 batch information |
- Filling line must be valid (11-16) - Active batch targets must be >0 - Article Variant ID must exist in SKU list - Batch IDs must be 12 characters - Targets must be split into thousands/units |
| TG20/TG21 | AUTEFA → VETRO | Line/Product Change Request | - Filling line - Tray Loader (21-28) - Requested Article Variant ID - Accept/Reject status (TG21) - Error code (TG21) |
- TL must be available - Article Variant ID must match current/next batch - Conveyors must be in automatic mode - No bottles required signal must be present - Error codes: 0 = No error 1 = Conveyors not in auto 2 = Bottle type mismatch 3 = No bottles required |
| TG30/TG31 | AUTEFA → VETRO | End of Batch | - Filling line - Batch ID - Article Variant ID - Tray Loader |
- Valid batch ID - Active batch must be running - TL must be assigned to line - Article Variant ID must match current batch |
| TG40/TG41 | VETRO → AUTEFA | Speed Update | - Filling line - Line speed (1-100 in steps of 10) |
- Speed must be between 0-100 - Speed changes limited to ±10 per update - Line must be running - No alarms active |
| TG50/TG51 | VETRO → AUTEFA | Activate Next Batch | - Filling line - Batch ID to activate - Article Variant ID |
- Next batch must be defined - Article Variant ID must match next batch - Current batch must be completing - Line must be ready for changeover |
| TG60/TG61 | VETRO → AUTEFA | Request Unloaded Bottles Count | - Filling line - Batch ID - Unloaded bottles count (TG61) |
- Active batch must be running - Counters must be operational - Regular updates (typically every 60s) - 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