RTU and PLC's network do not connect? #376
-
IntroductionSo I've made simple power station with one fission reactor, a turbine and an induction matrix. They are all working correctly, however the Reactor PLC and the RTU Gateway have their network light off (disconnected). Also pocket computers say permission denied when I try to use the alarms app, I think I need to input the auth key, but Computer screenshotsReactor PLC
Peripherals
The PLC connects to the reactor fine because when I activate in the GUI the PLC automatically turns it off. RTU Gateway
Peripherals
SCADA Supervisor"SRV" page
"PLC" page
"RTU" page
"CRD" page
Peripherals
"PKT" page
SCADA Coordinator"CRD" page
"API" page
Peripherals
Power station setupReactor
That network cable goes to the PLC. The waste goes to a bunch of Radioactive Waste Barrels. Turbine
That network cable goes to the PLC again Induction Matrix
The network cable at the top goes to the RTU Gateway Config files(without real auth key) Some of the configs were made with the GUI configuration programs. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 13 replies
-
|
Are you using wireless modems or ender modems? Wireless modems have limited range which is reduced by walls and bad weather. |
Beta Was this translation helpful? Give feedback.
-
|
The new logs are Looks like the supervisor is just ignoring the PLC and RTU |
Beta Was this translation helpful? Give feedback.
-
|
Please edit |
Beta Was this translation helpful? Give feedback.
-
|
Looks like the same supervisor-log.txt |
Beta Was this translation helpful? Give feedback.
-
|
If you are using facility keys and you edited the right file, you should be getting log messages about it verifying the messages if it is receiving any, including from the coordinator. Looking at that log, I don't see it initiating the cryptography. That means it doesn't have an AUTH_KEY set, so I bet the coordinator is the same way. I noticed you had named all your configuration files with .settings, I assumed that was just something you edited when zipping them for some reason. Only the Reactor PLC and RTU support the new .settings format, those aren't used elsewhere. The setup guides and wiki instruct that you should still be using |
Beta Was this translation helpful? Give feedback.
-
|
That was correct. Not sure how the extra .settings files were made. However the server now crashes because the environment detector. Should try to update Advanced Peripherals because I'm on "0.7.32b" |
Beta Was this translation helpful? Give feedback.
-
|
Glad you've got it working now! Yeah updating looks like it should work now, I see this in their resolved issues: IntelligenceModding/AdvancedPeripherals#532 |
Beta Was this translation helpful? Give feedback.
-
|
That fixed it. Thanks! |
Beta Was this translation helpful? Give feedback.
If you are using facility keys and you edited the right file, you should be getting log messages about it verifying the messages if it is receiving any, including from the coordinator.
Looking at that log, I don't see it initiating the cryptography. That means it doesn't have an AUTH_KEY set, so I bet the coordinator is the same way.
I noticed you had named all your configuration files with .settings, I assumed that was just something you edited when zipping them for some reason. Only the Reactor PLC and RTU support the new .settings format, those aren't used elsewhere. The setup guides and wiki instruct that you should still be using
coordinator/config.luaandsupervisor/config.lua. If y…