@stuart
I just noticed that as soon as the screen goes into sleep mode, it wakes back up, still showing the stabilizing screen with the DiyBMS logo and version. And the led is blinking green slowly.
The modules are version 4.2.0
I had this same issue but it seams like there are other chips that are very similar but maybe a slightly changed b value which from reading other posts would just require changing the firmware code a wee bit to get accurate temp measurements.
How old is the firmware on the modules?
Can you take a module out of the loop and upgrade it (disconnect from battery!)
The firmware is pretty old, over a year. I am waiting on parts for the v4.4 modules so I guess I will put this on hold till then.
It should work though, think itâs just due to the age of the firmware on the modules
Hi everyone, am new here. I have some newbie question, I try to order diybms from jlcpcb and have them assembled them for me also but they never have all the components. So my question is can i order the pcb from them and assemble myself, and where do i order all the necessary components for the module and controller. Thanks
Well. I make a big mistake to actualize platformio and since thatâŚ
Welcome Xtlife,
I ran into that same issue. After some digging I have found that the main missing components have alternates that you can manually select in JLC. The thermistor seams to have a similar spec but different brand option at this part number C95968, Similarly the SMBJ5.0A seams to have several basically identical options and based on other forum discussions can also be ommatid with only a small risk of damaging the board from static discharge, the ATTiny often has to be purchased separately if you can find a place with stock. I just looked over the controller board and it seams the IC chips are the main shortage @stuart JCLB is missing components for U1, U3,& U8. I found parts that to my untrained eye seam very similar(mostly just different brand) and likely compatible but cost a bit more. For U1 I found a crazy expensive C132227, U3 C161197, U8 C55762. Any help on if those would work or if I should wait till fall when more parts are in.
Where are you based out of? I am planning an order here in the USA soon and am looking for folks interested in doing a group buy since it is hardly more cost to increase the size of the order.
@stuart as i mentioned earlier, i did the resistor change as per the video you made and the result is now like this :
Notice the module 6 is getting less packets received, is it the sixth module from the controller or should i look a the cable from the previous module or what can that be ? Bad module ? Also i still see few CRC and OSS, is that what to expect at 200.000 packets ?
Hello @Xtlife
Check out the OEM shop - they have v4.40 products in stock now - all parts supplied as a kit.
Definitely something wrong with that module - perhaps is just a cable issue?
Can you swap that module with another one and see if the problem moves?
but should i try to replace module 7 (itâs starts at 0) or should i replace module 6 ?
If you click the âidentifyâ button it will flash the LED to indicate which module it is.
As the packet count is significantly lower than the rest, I suspect the controller ship is rebooting.
Perhaps some bad soldering ?
What do you mean ? As far as i can see the controller doesnât reboot, maybe you mean the module ?
Crazy typo there!
âmodule chipâ
1 Like
Lads,
when i run the controller with no module attached it ends up with STABILIZING⌠on the display, the wifi works and no LEDs flashing. BUT when I try the same controller with the test sofware, the display remains dark and no LEDs flashing.
I already spent two days trying to figure out where the problem is, but Iâm stuck. Any clues?
Thats to be expected - connect a module !
Its waiting for all the modules to reply - you could also try putting a cable between the TX and RX connections on the controller board.
switch (_controller_state)
{
case ControllerState::PowerUp:
//Purple during start up, don't use the LED as thats not setup at this state
hal.Led(RGBLED::Purple);
break;
case ControllerState::ConfigurationSoftAP:
//Don't use the LED as thats not setup at this state
hal.Led(RGBLED::White);
break;
case ControllerState::Stabilizing:
LED(RGBLED::Yellow);
break;
case ControllerState::Running:
LED(RGBLED::Green);
//Fire task to switch off BOOT button after 30 seconds
xTaskNotify(wifiresetdisable_task_handle, 0x00, eNotifyAction::eNoAction);
break;
case ControllerState::Unknown:
//Do nothing
break;
}
Shouldnât LEDs light up according to the controller state?
Yes, but it does appear that the Yellow doesnât light up for me at the moment!