From 1512a14a5ef99313adf86083ab545050a9a2676d Mon Sep 17 00:00:00 2001 From: Noah Metz Date: Thu, 14 Dec 2023 17:32:59 -0700 Subject: [PATCH] Updated readme --- README.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index 3e870f6..e7ce480 100644 --- a/README.md +++ b/README.md @@ -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.