WisBlock power design feedback

After using these things for few years now, I thought I should share some feedback about the power arrangement on WisBlock. I certainly appreciate the flexibility that the WisBlock products provide, and this feedback is offered in the hope of making them even better.

My “standard hardware” is a RAK19007 baseboard, RAK4631 processor, RAK12500 GNSS, RAK15002 SD carrier, and two RAK15005 FRAMs.

I think FRAM is the ideal form of small NV memory. The two main advantages over EEPROM is that you don’t have to prearrange writes in pages and there isn’t the 5ms polling wait after writes. I use the RAK15005 because the larger sizes use SPI rather than I2C and I’m using the SPI to stream data to the SD Card.

The 15005 in standby draws 15uA. It can be put into sleep mode to draw 4uA.

I use an active GNSS antenna with the RAK12500 GNSS module also powered by 3V3_S, and this typically draws something like 10mA. There is a resistor strapping option that would connect the LNA_EN pin directly to the antenna, but the enable is meant to control an external switch, and I doubt it is rated to handle a 10mA draw directly (but I admit I haven’t tried this). To power down the LNA I have to drop the 3V3_S and everything that hangs on it. But conversely this means that whenever I want to use the FRAM, I have to power the LNA on the GNSS antenna.

At the same time the SDcard is powered by unswitched 3V3 which idles at something like 10mA. There is no option to fully power down the SDcard at all.

I know that everyone has their own projects and their own use cases that are not the same as mine. But I also think that everyone is trying to solve the same basic problem of how to make their device run on less battery and the general principle is the same.

I suggest that future versions would be improved by making the default supply for any peripherals under (say) 1mA to use unswitched 3V3 and anything over 1mA to use 3V3_S. We can debate the ideal threshold, but clearly having the FRAM with uA standby current on 3V3_S and the SD carrier supply unswitched is the wrong way around.

The GNSS would be improved by including a switch controlled by LNA_EN, but the above changes would at least allow the whole GNSS to be powered down while still using the lower powered devices.

I also think the memory cards would be improved by having the most sig address bits strapped to the slot id somehow, but I don’t have a straightforward solution for this.

Thank you for your feedback. It is helpful for future module developments.

For your last point

I also think the memory cards would be improved by having the most sig address bits strapped to the slot id somehow, but I don’t have a straightforward solution for this.

Can you explain? I am not sure if I understand it fully.

On all the various EEPROM and FRAM devices used on the storage cards are the A2 A1 A0 pins that are strapped via resistor loads. They configure the chips to respond to different I2C device addresses like 0b1010aa where aa is 0…3.

If I want to use two storage modules on the same baseboard I have to ask you to identify the relevant resistors for me (because they are not shown in the usual doco) and then modify one of the cards so that both are addressable on the shared I2C bus.

It would be nice if a storage card in slot A had aa = 00, slot B had aa = 01 and so on, by having fixed logic strapping on the baseboard side of the connector. This would require freeing up a few spare pins on the existing connector definitions.

Got it.
But there are not really “spare pins” on the sensor slots.
The connector is designed to allow the sensor module to be plugged in in any orientation (like a USB-C).

Doesn’t make sense anymore today, but that’s how it was designed in 2020.

:grinning: That’s why I said I don’t have a ready solution.

I don’t know if you have enough orders going through to justify it, but maybe it would be possible to create different product codes that one could order different device address strappings. … like I can order PocketV2 in three different colours.

Or maybe I’m the only customer who wants more than one memory device :frowning:

It’s not a big concern. The 3V3 situation is the main issue.