That board looks pretty nice, you likely will want to add a couple reverse current protection diodes on the power inputs just in case.
It might make sense to add a footprint for the CAN connection to be an RJ45 since that is what a few of the charge controllers use (pin 1 and 2 IIRC).
hi @stuart,
I think this is correct but i am not 100% sure can you verify?
when i tried this fuse setting i still dont have it connecting to the module.
Edit:: BODPD must be disabled but it still didnt work when disabled.
i feel i am so close but getting frustrated right now hhaah
Kind Regards
Jency
Looks very nice.
I have a small concern about display. It looks like a good feature, however, if controller board is powered directly from battery it might create an unnecessary load. I do not know how much current such display is using, but maybe it would be a good idea to make it switchable? Like add a button (probably hardware switch) to turn it on/off?
The display is about 40mA and is completely optional, I may not even support/write code for it, but its a frequently requested feature so Iād like to include it on the controller just in case.
The display has a touch interface so I can use that instead of physical buttons to power it off when not in use/idle. It also supports a sleep mode to save power. The backlight is also driven from a PIN so I can switch that off.
1 Like
The values need to be
board_fuses.lfuse = 0xE2
board_fuses.hfuse = 0xD6
board_fuses.efuse = 0xF4
You shouldnāt need to mess with the AtmelICE program. Platformio fully supports the AtmelICE programmer if that is what you have Atmel-ICE ā PlatformIO latest documentation
i know it should work. but i keep getting this error: avrdude: jtag3_open_common(): Did not find any device matching VID 0x03eb and PID list: 0x2141
Same problem here, with a fixā¦
https://www.avrfreaks.net/forum/atmel-ice-avrdude-cannot-find-device
That new controller spec certainly looks nice - rs485 would be nice for me as I just received docs for the renogy charge controller Iām using from them (and the time issue isnāt a problem as itāll take me a decent chunk of time to implement the interface to the controller - thereās a lot there.
Stuart, great work on the shunt! I canāt wait until that is a bit further along. Iām even more excited about the possibility of an upgraded controller board!
Iāve got an interesting one for you. I am using both MQTT and Influx. Influx shows 16 cells, MQTT only shows 15. It is missing the last cell. The webpage and influx all show every cell. MQTT is just missing the last one. All the other voltages line up when comparing the other 2 data sources. It is the final cell that just wonāt display.
I took a brief look at the code, but as nobody else seems to have an issue I didnāt know if it was just a weird quirk or if I should try flashing it again.
Also, is there an easy way to reset the wireless credentials without re-flashing a controller?
I am curious why someone wants an LCD.
Also, isnāt the LCD a perfect candidate for a daughter card or cable connected thing? Doesnāt the LCD want to be some distance from the controller/modules?
If the concern is security, then I see no reason why the code canāt be updated to have a login and even https. I would do this, but I see no need. I have a wifi router and it is secure.
If I were you (@stuart) , I would not want the hassle of code for an additional user interface.
Hi Tom are you running the latest code, that was release a few weeks ago? The one with the dark theme.
You can reset the WiFi credentials from the controller. If you reboot it and wait for the led to light, you now have 3 seconds to connect the 2 WiFi rst pins together.
OMG yes such a relieve, i took me quit some time to get it running but it finaly worked.
Thx for your support @stuart
Probably because of the same reason that you wants to have INAs. For someones particular case this feature might be exactly so vital as INAs for you. (A place without a router: a shed in the forest, RV, Boat without any Wi-Fi/internet).
1 Like
Great, well done
I think I got code from before that. Iāll upgrade.
Ahh okay. I recall reading about that at one point but I must have forgotten about it.
Is there any harm to the device to send an MQTT update when the system refreshes instead of every 30 seconds?
Hello,
I have successfully flashed 20 ATTINY modules but the ESP controller (Wemos D1 mini Pro was a FAKE 4MB) despite the change board_build.ldscript = eagle.flash.4m1m.ld it just flashes and I can see it but not address it in the browser
You donāt need to change the value of board_build.ldscript is you are using the latest code and platformio - did you watch the programming video?
If you are trying to connect to the wifi hotspot using an Android phone, switch off mobile data first.
2 Likes
Sorry, I missed that. Why isnāt it just a header? I mean thatās a lot of real estate and you force the user to mount the controller where it can be seen. Why not an LCD attached via cable?
Iād like to hear a real user. I can speculate what they might be thinking as well as anyone.
The guy that makes the electrodacus bms says that people wanted the LCD for āsecurityā reasons. Iāll bet that bogus reason is driving some of these requests.
The cost of adding a 2nd user interface to the DIYBMS is enormous. The time to program it, the questions that come from it, the requests for more and more features, and especially if they start demanding horrid little buttons to make a rotten UI that can change the settingsā¦ just shoot @stuart. Heās already helping individuals sort out wiring and programming problems. A second UI doubles his troubles.
The cost of buying some used phone, or tablet, plugging a usb cable into it and mounting it where youād mount the LCD strikes me as a better solution because I would not be limited in placement except by my ability to get power to it. And all of this is so that I donāt have to switch to AP mode to see the status?
Sorry, but the LCD seems like a very poor choice for @stuart. It seems like a recipe for a ton of work.
Essentially, I donāt see why having a display is a bad idea. To me it seems logical that code runs on the arduino and ui runs on the display making both stand alone elements.