I'll be back on B4R again

Peter Simpson

Expert
Licensed User
Longtime User
So once again I've ordered lots of kit from AliExpress (I've not done that in a while), so I'll be uploading lots of code and examples onto the B4R section of this forum again. I really do like B4R, especially as I used it to program a few smart light switches in my house :)

I'm just writing a program for one of these at the moment, I needed a break for AW (Android Wear)...
1.jpg

3.jpg
 

Cableguy

Expert
Licensed User
Longtime User
Is it an esp32?
Can you post a link for the product?
 

mrred128

Active Member
Licensed User
Longtime User
FYI: I have the esp12e version with a joystick and a .97 oled display. Nice toy and you can't use the display with B4R as it is on a non-exposed I2Cpins. The current B4R wire lib does not let you remap, like the standard Arduino 8266 Wire lib does.
 

mrred128

Active Member
Licensed User
Longtime User
Can't you just find and use another library with Inline C @mrred128?

As you read this, note that I am not disgruntled. I bought two of these units to play with.....looking at some battery backed up alarm sensor support.

For me, it was a nice toy but not very practical. Let's go into the reasons......

No Joy joystick. There is no reset button on this board so they used the "right' part of the joystick. You don't get to use it, unless you can take advantage of it rebooting every time.

Non default I2C buss for the OLED display. No go for the adafruit driver unless you hack it. There is another driver out there made for the esp8266 that you can set the I2C ports to use. These pins are not exposed and Wire doesn't seam to be able to handle multiple port defs. If you have additional I2C devices to use, you would need to write your own Wire lib.

Not all pins get exposed. You only get access to A0, D0, D3, D4, D8, D9, and D10. Throw in a motor control or a servo.....all gone. D3 is also used by the no joy joystick....so I guess you have to watch using this too.

Battery has to be removed to program. There goes OTA updates for an installed device.

So, for all the extra gizmos in the version I got, B4R is no longer a RAD solution. It's still useful under C++, but I don't see much benefit with this "all-in-one" device. Too many tradeoffs.

The unit you chose will probably only have an issue with the battery. Everything else should be smooth sailing. A much better choice for B4R projects.
 
Top