Rftop
January 31, 2020, 12:34pm
14
@hwestbrook , I agree, the issues are NOT limited to Solar Borons.
In the meantime, here are a few links:
Thanks. I just 1) flashed V1.4.0, seeing it is released, which amounts to flashing a new bare Tinker install, and 2) discovered this thread:1.3.1-rc.1+ change to Boron solar charging (via VUSB) behavior
What do you know, now the Boron starts up and connects to cellular with USB only power without any problem, rather than suddenly crashing/dying on startup.
Amazingly, just like that OP, this yet-another Particle software-related update-related catastrophic failure necessitated a 3-hour drive, a…
I’ve never noticed that, but I just tried and confirmed.
My Guess is that during EN pin Shutdown, the PMIC reverts to it’s default/basic configuration.
The results would suggest that the Minimum Voltage or Current isn’t being met with a Computer USB port, but can be met with AC/DC charger, which makes sense.
But I seem to recall confirming that the user defined PMIC settings were obeyed after EN Pin shutdown… at least back in 0.9.0 firmware days. I could be remembering incorrectly.
System …
@aklein24 , I decided to reproduce your findings for documentation.
I can reproduce using a USB port from a Computer.
I can not reproduce using a 5V power supply with micro USB connector.
To Break (with USB cable/port):
Li-Po @ 3.81 V
USB cable/computer port (4.95V no load) to Boron USB connector, Boron begins charging Li-Po @ 440 mA, 4.05 V measured on Li-Po Pin.
Remove USB Port power source, Li-Po now powers Boron.
Ground EN pin causing a Shutdown.
Re-attach 4.95V USB port power sourc…
Update:
Today, I tried to confirm that the workaround detachInterrupt(LOW_BAT_UC) returns the PMIC to previous Charging Performance since I have extensive test results for Boron Charging.
While the workaround does enable charging, It Does Not compare to previous results.
1.4.2 fails miserably when compared to the actual PMIC performance under earlier firmware.
Both Solar and Utility Powered when using the USB connector.
Since the Li-Po Charging issues are Chronic verses Acute, the typical u…
Per my testing, the workaround still doesn’t meet previous charging performance for Borons, both Solar and Utility Powered when using the USB connector, link
I don’t think the pmic.setInputCurrentLimit() nor the pmic.setChargeCurrent() have as much impact to Solar Borons as the setInputVoltageLimit(3880) change that happens behind the curtains. The first two are maximum allowed by the PMIC. It really shouldn’t matter what the first 2 are set at for a Solar Boron.
Would the proposed fix st…
Chip, I believe the culprit is the Boron 2G/3G. I typically assume LTE when speaking about Borons, I sometimes forget about the 2G/3G model that has a higher peak current demand. I’m assuming (from Below) the change was invoked for Boron 2G/3G without a Li-Po, which indeed is a very specific use-case to cause widespread problems for most other Boron Applications.
I do understand the need/desire to have the Boron and Electron compatibility in the Device OS (900 mA default).
However, the B…
I haven’t seen anything in the PMIC Datasheet that would suggest this…but I could be missing something.
I tried to reproduce your issue, and can now confirm something is very strange.
My Test:
3xAA (L91’s) Resting Voltage = 5.08 V
3xAA Operating Voltage = 4.91 V at 13 mA (Cloud Connected, powered by 3xAA only on Li-Po connector)
Then Connecting a 5.25V Power Supply to the Boron USB connector actually INCREASED the current leaving the 3xAA to 41 mA. Approximately 140 mW was un-accounted …
@Tim-D , I’ve performed some recent testing with variable power supply (Current and Voltage), and with 6V Panels. Tests were performed using the Vusb pin.
It appears that the Boron DPDM is going crazy during Sleep.
After Calling enableDPDM(); during setup, the Boron will obey both Current and Voltage limits per the user’s settings for a Solar Panel, while it’s awake (as expected). The Boron will automatically manage the current to maintain the Voltage Setpoint (Solar Panel).
But as soon as…
I have many projects sitting on the Shelf because of 1.3.1 firmware and newer.
Its my opinion that Particle assumed (incorrectly) that these issues were only for Solar Recharged Borons which is limited Scope/Customers. Hopefully the Boron will get the attention it deserves in the near future after the smoke clears from the Mesh
