Mecalux/mcp-wms-wiki
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

lint(standard): corrections completes mode standard

Browse Source 
- 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)
This commit is contained in:
Arthur
2026-07-20 13:01:21 +02:00
parent 7496aafe64
commit 9ce6ae37be
88 changed files with 1769 additions and 1871 deletions
Download Patch File Download Diff File Expand all files Collapse all files
wiki/operations/galileo-troubleshooting.md
+28 -28
View File
@@ -21,7 +21,7 @@ last_compiled: "2026-04-17"
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
## 1. Gateway log - location & structure
`C:\ProgramData\Mecalux\EasyWMS Gateway 2015\Logs\AllLog.log`
@@ -46,7 +46,7 @@ Fields carried on each update:
| **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.
> The couple **StationType + StationNumber** is unique - always identify a station by that pair.
### 1.2 Route update line
@@ -56,13 +56,13 @@ Fields carried on each update:
| 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).)
(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)
- **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
@@ -82,15 +82,15 @@ Two search patterns are usually enough to reconstruct a container's history.
This two-step pattern answers most "where is container X?" questions without paging through the whole log.
## 3. End error codes — diagnosis
## 3. End error codes - diagnosis
| Code | Meaning | First action |
|------|---------|--------------|
| `0` | Movement complete | None — next movement generated |
| `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 |
| `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)
@@ -103,14 +103,14 @@ GALILEO did not understand the order. Root cause is **always** a configuration d
- Two containers planned to cross paths (impossible movement)
- Coordinate system discrepancy between sides of the entry table vs the aisle
**Resolution — 4 steps:**
**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
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.
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
@@ -119,16 +119,16 @@ Faults reported on the GALILEO SCADA / Automation Dashboard. See [Automation Das
| 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) |
| **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.
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.
> ⚠️ 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.
@@ -136,19 +136,19 @@ High-level: update the WMS IP / hostname inside the GALILEO program configuratio
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
- ☐ 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
- [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
- [Automation Dashboard](../modules/automation-dashboard.md) - fault reporting UI