How does the rfid inventory robot work together?
The RFID inventory of the core of the RFID robots and AMR not to place both devices in the same warehouse, but to put them in.Same set of dispatch logicIn -- who does the task level first, how the path layer avoids, how the data layer returns, what is not. The most problematic place in the actual project is not the robot itself, but the dispatch system does not think of priority for the inventory and removal tasks, the rhythm (that is, the interval between the pace of completion of an action) and the abnormal branch. Here's what we do with the storage projects, we take out one item.
Point 1: First, we'll have to separate the roles.
Many people assume RFID inventory robots and material-handling AMRs can be dispatched together. In reality, they operate quite differently:
- RFID Counting Robot: Core task is to identify the electronic labels on the shelf, which need to be performed in the target areaSlow Stop(usually 0.3 - 0.8 m/s) The length of stay varies from seconds to dozens of seconds depending on the label density and number of antennas. Its "output" is an inventory data count, not a physical shift.
- Move AMRThe core task is point-to-point transport, which pursues the shortest path and speed of rhythm, usually without a long stay in a particular location.
And when we're clear, the dispatch system can send a different command template to two types of equipment -- the machine for "where to go, how long to stay, which labels," and the AMR for "start, finish, which road." We've been in some warehouses, mixed these two sets into the same task pool, and then moved AMR to do the count, and stayed half a minute before the shelf, leading to material transfer cards on the entire line.
Point 2: Unified map and movement control platform, which allows two types of robot to run on the same bottom map
The first step in the synergy isHarmonization of maps. If stocktaking robots and transport AMRs each maintain their own maps, route conflicts are almost inevitable. In practice:
- All AMRs and inventory robots share a single SLAM (simultaneous localization and mapping) map, which robots generate themselves. A grid resolution of 5 cm per cell or finer is recommended.
- The map shows three types of area: conveyance, inventory presence, restricted area. The inventory robot can stop in the area, and move AMR defaults.
- The movement control platform receives tasks from WMS (storage management system) or the upper operating system, which are then distributed according to the type of equipment.
When Shanghai Zejie Technology designed a system for a third-party logistics warehouse, it ran into a common problem: transport AMRs and inventory robots used separate dispatch systems, so both sent vehicles to the same rack area. Connecting all equipment to a common dispatch platform reduced conflict alerts from more than 10 a week to almost zero.
Key point 3: Break down stocktaking into five steps, from triggering to archiving
Once the inventory robot is commissioned, standard processes can be broken down into five steps:
- Mission down.: WMS or manual trigger inventory command, specifying the inventory area (cargo number, alley number or SKU range).
- Path PlanningSchedule platform calculates the best path to avoid operational moving AMR.
- Staying to Read(b) The robot, upon arrival in the inventory area, adjusts the antenna attitude (if multi-faceted antenna shelves) to read the label in predefined order.
- Data Return: Read results are sent back to the edge server in real time via Wi-Fi, and one call delay control is within 2 seconds.
- Abnormal Tags: Unread or misread labels are immediately marked, a list of discrepancies is generated and sent to reviewers.
The most easy to get a shell in these five steps is step three -- stay-read. RFID labels are highly exposed to environmental impacts, and metal shelves, liquids, and labels tend to interfere with reading effects.Minimum stay time(e.g. 8-15 seconds) andMaximum stay time(For example, 30 seconds) The maximum time is over and the anomaly is reported before it is read out, with manual intervention rather than unlimited waiting.
Point 4: Abnormal treatment and priority arbitration, with three types of conflict to be separated
Two types of equipment run simultaneously, and the conflict is basically divided into three categories:
| Type of conflict | Typical scene | Processing policy |
|---|---|---|
| Path Conflict | The AMR and the inventory robot both entered the same alley. | - Move priority. Take a look at the robots and move or go around. |
| Conflict in the area of presence | The inventory robot is at the site. | Move AMR around 2 m radius. |
| Charge Conflict | Two sets of equipment to get the same charger. | Charged pillar group management, inventory of robots using low power stakes and removal of AMR high power stakes |
The logical recommendation for priority arbitration is written in the configuration file of the dispatch system, rather than on running. It is common practice to move tasks > take stock of tasks > free schedule. There is an exception - if the inventory task is relatedMonthly financial closureSuch hard-cut-off operations may be subject to temporary upwards of priority.
Point 5: Several pits that can easily be stepped on during deployment, avoid them earlier.
Finally, there are several recurring problems in the actual project:
- Wi-Fi coverage is unevenA data return package is lost if the number of an inventory robot is weak. It is recommended that RSSI (receiving signal strength indicator) values be measured at each count point, and that AP (wireless access point) be added to a point below -75 dBm.
- The labels are not aligned.: If the label is unsettled, the reading rate falls from 95% to less than 70%. The WMS will add a top shelf rule and enforce the tags out.
- Scheduler clocks are not synchronizedThe time of the mission is deviation from the impact list if you use a local clock for the moving AMR and the inventory robots. It is recommended that all devices be synchronized with NTP (network time protocol) and that errors be contained within 100 milliseconds.
- Ignore night operationsMany warehouses run only the count and not the load, which allows for a full deployment of the moving AMR to charge, leaving the inventory robots in the exclusive possession of the route, which is more efficient.
It's easy to work with this, to run."Stand and run."So, the core is three words: map unity, task diversion, abnormally low. Now that these three pieces are solid, the RFID machine and AMR can actually do their own work in one warehouse without delay.

Ms. Lei
Mr. Pang