arthur
9ce6ae37be
- Em dashes: 1712 remplaces par tirets simples (86 fichiers + _index.md, en-tete section Limagrain conserve) - Checklists: 24 '- [ ]' -> '- ☐' (3 pages operations, plus de todos Obsidian) - Ancres: 33 reparees (slugs GitHub + ancres HTML <a id> reconnues), 1 reciblee (manuel de reten) - related: tenseflow -> tense-flow, pie -> mechanical-elements, group.md retire (doublon shipping) - Registre: compteur global 122 -> 131 pages - Rapport racine _lint_report.md mis a jour (scan v2 + re-scan final: 0 anomalie) - Aucun fichier limagrain/ modifie (cloisonnement)
155 lines
7.5 KiB
Markdown
155 lines
7.5 KiB
Markdown
---
|
||
title: "Galileo Troubleshooting (Logs, Faults, Address Change)"
|
||
type: operation
|
||
sources:
|
||
- sources/archives/Comprendre_logs_Gateway.md
|
||
- sources/archives/Erreurs_Defauts_GALILEO.md
|
||
- sources/archives/Changer_adresse_WMS_dans_GALILEO.md
|
||
related:
|
||
- architecture/galileo-integration.md
|
||
- operations/galileo-simulation.md
|
||
- operations/troubleshooting.md
|
||
- concepts/stations.md
|
||
- concepts/mechanical-elements.md
|
||
- modules/automation-dashboard.md
|
||
last_compiled: "2026-04-17"
|
||
---
|
||
|
||
# Galileo Troubleshooting (Logs, Faults, Address Change)
|
||
|
||
## Overview
|
||
|
||
How to read Gateway logs, interpret station / route updates, trace a container through a simulation or production run, and resolve the most common GALILEO faults (EndErrorCode=4, 1116 incorrect task, variator faults). Pair this page with [GALILEO Integration](../architecture/galileo-integration.md) for the protocol reference and [Galileo Simulation](galileo-simulation.md) for the bring-up procedure.
|
||
|
||
## 1. Gateway log - location & structure
|
||
|
||
`C:\ProgramData\Mecalux\EasyWMS Gateway 2015\Logs\AllLog.log`
|
||
|
||
Every frame exchanged between GALILEO/EasyS and EasyWMS lands here. Recommended viewer: **klogg** (handles 100 MB+ files without lagging).
|
||
|
||
The log is dominated by three categories of lines:
|
||
- Station updates (every 1–3 s per station)
|
||
- Route updates (every 1–3 s per route)
|
||
- Event / Search / End frames (driven by container movements)
|
||
|
||
### 1.1 Station update line
|
||
|
||
Fields carried on each update:
|
||
|
||
| Field | Description |
|
||
|-------|-------------|
|
||
| **StationType** | Station type configured in the WMS |
|
||
| **StationNumber** | Station number configured in the WMS |
|
||
| **Status** | `1` = ready, `0` = error |
|
||
| **Loaded** | `1` = free, `0` = loaded |
|
||
| **Capacity** | Max containers on the station |
|
||
| **CurrentCount** | Trackings currently on the station |
|
||
| **Aisle** | Aisle number bound to the station |
|
||
|
||
> The couple **StationType + StationNumber** is unique - always identify a station by that pair.
|
||
|
||
### 1.2 Route update line
|
||
|
||
| Field | Description |
|
||
|-------|-------------|
|
||
| StationTypeSource / StationNumberSource | Origin station |
|
||
| StationTypeDestination / StationNumberDestination | Destination station |
|
||
| **Status** | `1` = free, `3` = full |
|
||
|
||
(Protocol also defines `0` = no comms, `2` = electromechanical fault - see [GALILEO Integration](../architecture/galileo-integration.md).)
|
||
|
||
### 1.3 Event, Search, End
|
||
|
||
- **Event** - typically a PIE event with barcode + weight + dimensions + container/height types
|
||
- **Search** - a TK or conveyor asking for the next order
|
||
- **End** - confirmation the container reached its destination (with an error code)
|
||
|
||
## 2. Trace a container in klogg
|
||
|
||
Two search patterns are usually enough to reconstruct a container's history.
|
||
|
||
1. **What happened at the PIE** (identification data):
|
||
```
|
||
DataInfo.+_CodeSupport_
|
||
```
|
||
Replace `_CodeSupport_` with the actual container barcode. Returns all PIE events that read that code.
|
||
|
||
2. **What happened after** (movement trace):
|
||
```
|
||
Movement=_NuméroDeTâche_
|
||
```
|
||
Replace `_NuméroDeTâche_` with the task number. Returns all Search / End / status updates tied to that task.
|
||
|
||
This two-step pattern answers most "where is container X?" questions without paging through the whole log.
|
||
|
||
## 3. End error codes - diagnosis
|
||
|
||
| Code | Meaning | First action |
|
||
|------|---------|--------------|
|
||
| `0` | Movement complete | None - next movement generated |
|
||
| `1` | Deposit error | Inspect the destination location, relocation/reject task expected |
|
||
| `2` | Extraction error | Inspect the source location, relocation/reject task expected |
|
||
| `4` | Inconsistent order | WMS/GALILEO config mismatch - see section 3.1 |
|
||
| `7` | Gauge error | Container fails dimensional check - routed to REAC / RECH |
|
||
|
||
### 3.1 EndErrorCode = 4 (most frequent)
|
||
|
||
GALILEO did not understand the order. Root cause is **always** a configuration drift between EasyS/WMS and GALILEO.
|
||
|
||
**Likely causes:**
|
||
- Location does not exist on the GALILEO side
|
||
- Location exists on both sides but the allowed **container type / height type** differs
|
||
- X/Y coordinates out of range on GALILEO
|
||
- Two containers planned to cross paths (impossible movement)
|
||
- Coordinate system discrepancy between sides of the entry table vs the aisle
|
||
|
||
**Resolution - 4 steps:**
|
||
|
||
1. Grab the frame sent to GALILEO from the Gateway log (Station types, numbers, coordinates, container/height type)
|
||
2. Open the GALILEO program: `C:\<NomDuClient>\Programme\<installation>.mgp` (double-click to launch)
|
||
3. Compare the station list between GALILEO and EasyS - aisle, allowed types, X/Y - line by line
|
||
4. Use the station query shipped with [Galileo Simulation - §9.1](galileo-simulation.md) to dump the WMS-side view
|
||
|
||
If you change anything on the GALILEO side, also sync the change in EasyS (and vice versa) - the two systems must stay in lock-step.
|
||
|
||
## 4. GALILEO fault codes
|
||
|
||
Faults reported on the GALILEO SCADA / Automation Dashboard. See [Automation Dashboard](../modules/automation-dashboard.md) for monitoring; use this table to triage.
|
||
|
||
| Code | Name | Typical causes |
|
||
|------|------|----------------|
|
||
| **1116** | Incorrect task CU1 | Location locked on GALILEO but not on EasyWMS (or vice versa); location exists in EasyWMS but not in GALILEO; same location has different allowed container types on each side; WMS asks to deposit on the left rack while the container sits on the right fork of the miniload (and vice versa) |
|
||
| **1201** | Variator fault X | - (variator hardware fault on axis X) |
|
||
| **1291** | Unreferenced SM302 card on the variator | Warning only |
|
||
|
||
Fault 1116 is the configuration-drift counterpart of `EndErrorCode=4` at the automation layer - same root cause, different reporting surface.
|
||
|
||
## 5. Change the WMS address inside GALILEO
|
||
|
||
When the WMS server IP or DNS changes (migration, VM rename, network reconfig), the GALILEO side must be updated so the PLC can reach the new Gateway.
|
||
|
||
> ⚠️ The Confluence page for this procedure contains only screenshots (no extractable text). Refer to [Confluence - Changer l'adresse du WMS dans GALILEO](https://easywmsfrance.atlassian.net/wiki/spaces/EF/pages/3000756076552) for the step-by-step screen walkthrough.
|
||
|
||
High-level: update the WMS IP / hostname inside the GALILEO program configuration (the `.mgp` file under `C:\<NomDuClient>\Programme\`) and restart the GALILEO runtime. Then verify the Gateway log picks up the new connection.
|
||
|
||
## 6. Checklist before escalating
|
||
|
||
Before opening a ticket or calling Support:
|
||
|
||
- ☐ Gateway service (`EasyWMSGateway2015`) is **Running**
|
||
- ☐ `AllLog.log` shows recent traffic (not frozen, no error spike)
|
||
- ☐ Port 3000 is open on the WMS host (inbound + outbound)
|
||
- ☐ `tenantCode` and `TokenUser` in `MainObject.config` match the target WMS
|
||
- ☐ The specific (StationType, StationNumber) pair exists on both sides with identical parameters
|
||
- ☐ Allowed container types + PLC Height Type couple match on both sides
|
||
- ☐ No untracked containers stranded on blind conveyors (LBC, LRL - see [Mechanical Elements](../concepts/mechanical-elements.md))
|
||
- ☐ Automation Dashboard fault report consulted to correlate with machine-level faults
|
||
|
||
## Related
|
||
|
||
- [GALILEO Integration](../architecture/galileo-integration.md) - protocol reference, workflows, command/event catalogue
|
||
- [Galileo Simulation](galileo-simulation.md) - EasyS bring-up, station sync query
|
||
- [General Troubleshooting Guide](troubleshooting.md)
|
||
- [Stations & Routes](../concepts/stations.md) · [Mechanical Elements](../concepts/mechanical-elements.md)
|
||
- [Automation Dashboard](../modules/automation-dashboard.md) - fault reporting UI
|