-
Notifications
You must be signed in to change notification settings - Fork 25
Machine Monitoring
gordominossi edited this page Dec 30, 2022
·
2 revisions
This module runs on a `local server`
Supported machines:
- GT machines
- Adapter
- Waypoint (Optional)
- The other NIDAS hardware requirements
- Tracks machine information:
-
Names
-
Recipe progress
-
Efficiency
-
Power usage
-
Number of issues
-
Locations
Each machine has to be individually configured for location support.
-
- Robot (for machine maintenance locations)
- Place it by a charger so it doesn't run out of battery.
- Create your robot with the following components:
- Internet card (for setting up and updating).
- Tier 2 network card (for communicating with the server).
- Some RAM.
- A disk installed with OpenOS
- A keyboard (for running commands)
- A graphics card.
- A CPU.
- A Screen
- Upgrade Container.
- Navigation Upgrade in the Upgrade Container. (Craft the Navigation Upgrade with a vanilla map that was created on top of the robot to ensure it being in range)
- Install the program just like you did for the server. You can also install NIDAS to the hard drive before creating the robot.
- Whenever you place your robot in a new location, it'll prompt you for that location. Use the terminal to give the X, Y and Z coordinates.
- New machines
- (Optional): Place down a waypoint so the particle effects are inside the machine controller location.
- (Optional): Name the waypoint. This will be the name of the machine in the system.
- (Optional): Give it a redstone signal.
- Place the adapter on the machine controller (You can use an MFU for that, so you don't need the adapter to be adjacent to the controller).
- (Optional) Remove the waypoints.
- This is what it looks like:
Notice the adapter have MFUs on them because they're not adjacent to the machine controllers.