kylebotha Posted August 14, 2020 Posted August 14, 2020 I have a Pylontech battery that I am trying to read info from, and I've had some on and off success, I have a RJ-11 to RS-232 Cable and the Pylontech is connected to my Windows laptop for now, at a later stage I want to connect it to my Raspberry Pi 4, with a script that saves the info that is read from the battery, but I first need to understand the Pylontech CLI before I can start writing scripts to communicate with it. At first I tried using some Console emulators such as PuTTy, but I had no success, kind of, It looked like I was indeed getting a response from the battery, but it didn't look like the correct response, as far as I understood, I needed to activate the batteries console, by setting my terminal program settings to 1200, 8,N,1 and then sending the following hexadecimal string 7E 32 30 30 31 34 36 38 32 43 30 30 34 38 35 32 30 46 43 43 33 0D after sending that string, I got the following response: ~200146060000FDAD ~200146060000FDAD I tried messing around a bit more but I kept on getting this same response, I then found the BatteryView application and started to use that for a temporary solution, and it works perfectly fine, but it still doesn't completely solve my problem. Today, I tried to connect via a terminal program again, and I had some success, I changed the terminal program settings to 1200, 8,N,1 and sent the hexadecimal string (7E 32 30 30 31 34 36 38 32 43 30 30 34 38 35 32 30 46 43 43 33 0D) but this time I got a completely different response, now I unfortunately didn't record that response but it had was a bunch of strange characters, I then proceeded to change the settings to 115200,8,N,1 and then I sent the 0D 0A hexadecimal string. Success! Finally, I had gotten into the Pytontech CLI and I was able to type commands like help, or bat to get some data, which was cool, but then my laptops battery had died, and when I rebooted to connect to the battery again, I had gotten the same responses that I originally got, which was: ~200146060000FDAD ~200146060000FDAD So I don't know if I just accidentally got something right and was lucky, or if I am missing some step, but the thing is, I got it to work, and now I'm stuck again at square one. Quote
Louisvdw Posted August 15, 2020 Posted August 15, 2020 The console must be turned on. To do this, change the terminal program to 1200, 8,N,1. Then send the following hexadecimal string to the battery : Data: 7E 32 30 30 31 34 36 38 32 43 30 30 34 38 35 32 30 46 43 43 33 0D Switch now to 115200,8,N,1. Data: Send 0D 0A. The pylon> flag should appear, allowing command input. From this post Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.