|
Post by trevinlc1997 on Jan 24, 2019 5:04:01 GMT
I've been trying to use the Modbus protocol over the bluetooth module but many apps fail to see the Serial Port Profile. Has someone successfully pulled information from the charge controller from the bluetooth module using their own app? If so can you leave a message on the steps you took or PM me.
|
|
|
Post by Admin on Jan 27, 2019 15:12:01 GMT
Hopefully this helps:
Here: renogy.boards.net/thread/266/rover-modbus
-Renogy Team
|
|
|
Post by playersz28 on Feb 5, 2019 16:46:51 GMT
At one point I was logging the BT data but never went as far as seeing if I could get an app to talk to the BT1. I'm using a Pi thru the port and the BT1 is disconnected.
|
|
raydas
Solar Devotee
Posts: 166
|
Post by raydas on Oct 31, 2019 13:53:11 GMT
playersz28, I know this is an old thread, but could you elaborate a little more as to how you were logging the BT data. I noticed you were/are using the Pi, which version. Also, what program were you using to do the logging.
|
|
|
Post by playersz28 on Nov 1, 2019 13:21:52 GMT
playersz28, I know this is an old thread, but could you elaborate a little more as to how you were logging the BT data. I noticed you were/are using the Pi, which version. Also, what program were you using to do the logging. Haven't been on here in a long time but started checking in a week or so ago. I was using nRF Connect on Android to watch the BT packet flow. I haven't looked at it for a year since I disconnected the BT1 and started using a Pi. It's a 3B+. I also still have an ESP8266 monitoring my shunt and sending the data via UDP to the Pi because I haven't found a C++ lib for the INA219 and haven't ported the Python one.
|
|