IPLUSMOBOT Cloudia
The monitor and dispatch server for a fleet of IPLUSMOBOT robots.
Category: Automation and Workflow
Cloudia, from IPLUSMOBOT, is a fleet management system for autonomous mobile robots (AMRs). IPLUSMOBOT describes it as software that assigns jobs to the right robot at the right time and directs traffic between them, and that connects to a customer's WMS, MES, and ERP systems. EmberNet packages Cloudia 2.1.19-34 as a chart of its own, so an edge node can run the dispatch server the robots dial into.
What it does
- Shows the state of the robots, task progress, and system health in real time.
- Dispatches missions to robots and manages traffic between them.
- Manages maps, and keeps uploaded maps and files under its data folder.
- Runs Space Management beside it (rcsctl, with the jzrouter path planner and libmrpc it starts for each space you apply).
- Backs up the database, maps, uploads, and spaces every night, and keeps 14 days of archives by default.
When to use it
Use it when you run IPLUSMOBOT robots and want the server that dispatches them on an EmberNet node at the site, instead of on a separate bare-metal box.
Running on EmberNet
- Its web interfaces are labeled for the App Store. The chart marks the dispatch interface on port 9000 as the primary one and lists Space Management (10000), the component manager (9669), and the file share (8800) beside it, so the App Store's port picker can offer each of them.
- One instance per node. The pod runs on the node's own network so the robots can reach it at the node's address, and a second install on the same node would need the same ports. The App Store offers one per node, and the chart keeps a second install Pending.
- amd64 nodes only. That is all IPLUSMOBOT ships.
- The databases come with it. MySQL, Redis, and InfluxDB run in the same pod, listening on the node's loopback address only.
- Your work survives restarts. Maps, uploads, spaces, and the databases each sit on their own volume, so a restart or an upgrade keeps them.
- The robots dial in. The node needs ports 9000, 9669, 10000, 8800, 8858,
8848, 16666, and 17778 free. After you deploy, set
server_addrin each robot's jzagentconfig.ymlto<node IP>:16666and<node IP>:17778, then restart the agent on the robot. - Then set up a space. In Space Management, add a space, then its map, vehicle type, and shelf, and Apply. Apply again every time a map changes.
- It reaches what the node reaches. The chart adds no network restrictions.
The dispatch interface and the file share ship with default logins, which are listed in the chart's app readme. Change both after you deploy.