MetzNet
/
v5_field_control
3
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Updated readme

main
noah metz 2023-12-14 17:32:59 -07:00
parent 8ff39bca17
commit 1512a14a5e
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
README.md
Unescape Escape View File

@ -1,15 +1,13 @@
# Setup
Connect ESP32 TX2 & RX2 to DI & RO of the Max485.
Connect Arduino TX2 & RX2 to DI & RO of the Max485.
Connect ESP32 D23(or whatever read_line is set to) to RE/DE.
Connect Arduino D23(or whatever read_line is set to) to RE/DE.
Power Max485 with ESP VIN/GND.
Power Max485 with 5V and GND connected to the Arduino.
Replace {WIFI_SSID}, {WIFI_PKEY}, {MQTT_HOST}, and {MQTT_PORT} in the code(and SubTopic if you want).
Flash the code onto the Arduino, connect A&B of the smart cable connected to the controller(aka the black and red wires respectively) to the Max485.
Flash the code onto the ESP32, connect A&B of the smart cable connected to the controller(aka the black and red wires respectively) to the Max485.
Viewing the USB serial of the ESP32, send 0xAB-like hex sequences to update the configured state.
Viewing the USB serial of the Arduino, send 0xAB-like hex sequences to update the configured state.
Known States:
- 0xC9 : paused
@ -30,3 +28,5 @@ From this the flags are thus:
The field control sequence(aka when the controller sends 0xA7) can be responded to with either a 0x02 ACK packet to acknowledge that the current values are correct, or a 0x53 packet to send new values. However, a 0x02 must be sent at least every 20 packets else the controller will restart the connect sequence.
All of the protocol reversing has been done with 1 brain & 1 controller, so any unique fields are constant and will need to be updated.
connection.txt has my notes from reversing the protocol, and notes.txt is my summarized reminder of how the protocol works at a high level.