hello there, Did you manage to solve this issue? :) Thanks

@arso Besides that this forum is about Pycom and Python, I can leave a few words about ESP32 and Arduino. It works, both with Version 1.6.13 and 1.8.10. In order to use the ESP32, you have to follow the intructions here: https://github.com/espressif/arduino-esp32/blob/master/docs/arduino-ide/boards_manager.md to Change the preferences to include the ESP32 modules Select the ESP package in the board manager (tools->board menu) and let it install the package. It is BIG. Select an appropriate board and settings in the tools menu If you have done a lot of configuration attempts, it may be better to erase Arduino form you system and start over again. Especially the Arduino folder with it's settinsg should be newly created (...\Documents\Arduino on windows, ~.arduino15 on linux), at this contains the ESP32 package.

I've seen comments about using lipo's for their current capability, I am using a generic Li-ion 26650 which is certainly capable of https://snaptube.cam/ , https://syncnet.onl/telegram-web/ multiple amps (haven't measured draw yet) so that seems unlikely. Any suggestions ?

Thank you robert-hh for the response. It's useful. I was not knowing about this as i run netflix on chrome as i got FreeAccountsOnline.

@ZachH The type of these bipolar transistor is not critical at all. Assuming that the sensor consumes less than ~200mA, almost any small signal type will fit.

Ok I finally got this to work! I was using the pycom fw upgrade tool tol flash my device with what I thought was the latest fw. Flashed my device with version 1.18.0 and it worked like a charm (latest version did not work, giving me another error..) Why doesn't the firmware update tool flash the latest version?

@robert-hh I did a concatenation with string and it's working. thank you for your answer

@Alephus GND is the reference point for signal levels. Principally, if both devices are connected by USB cables to the same computer, there is a GND connection. That's why it worked to some extend. But its is a long connection though many connectors with a substantial impedance, which form a large loop. That large loop picks up a lot of noise. And that noise created the weird bytes. So always have a good GND connection. P.S.: You're not alone.

@melbinmanuel Sorry, I cannot. Pycom does not publish any substantial technical information, and I do not have that board here for analysis.

@tttadam We all have these kind of findings over and over again.

@robert-hh This was a typo, i meant 100nF (ceramic capacitor with value 104) :-) Yes, I understand that the firmware should not be of an issue, this was really strange and inconsistent. Regarding vref_to_pin() call, at least for 10-20 secs the 1.1V output seems not to switch-off (i had a voltmeter connected permanently). I am also suspecting issues with ground-cabling in the breadboard, but I hope the capacitor would deal with them. Anyway, the thing is that I observed really large differences in the observed values when changing modules. For example for a 3.9V battery voltage using 3 different modules I got 3.9V, 3.7V and 3.6V. I will re-run the tests and report again. Thanks!

@robert-hh said in ADC sensors on external PSU: @Alephus Connecting the sensor to the input should not raise the voltage measure at that connection. So it must be something else in the set-up. after a while i did a few more tests and found something: of all ADC1 pins, all behave properly except P19 and P20 (guess wich 2 i was using) a friend analized my problem as well and detected that those 2 pins where not "floating", and after analazing the datasheet he assumes its because they are the only ones with pullup/pulldown internal resistors. So for now i have a solution however i still dont understand is why, after all, they are tecnicaly valid Pins pins in the datasheet

Thanks again for your explanations, @robert-hh! @robert-hh said in Deepsleep hangs system: I'm not fully sure, because I never got myself an expansion board 3.x. I never imagined pycoproc could also be used for the regular expansion board 3.x, I always though it was for controlling the PyTrack and PySense boards only. Now reading that the same hardware functionality available from the latter two as well as the early Deep Sleep Shield might also be available on the expansion board 3.x, we will be more than happy to investigate whether one can put the device into even lower/zero currents.

@psrebrny So I can't say that I predicted in detail the process you went through but my gut feeling told me that it won't be easy (although kudos to you for proving that it is possible). So I slept on the issue for couple of days and decided for another $50 to solve this problem by purchasing another dev board with Assist GPS and cutting my (TTFF) cold start to 26 sec. In fact just by reading its spec I was amazed and excited to avoid all this trouble - so I think that $50 is well spent. So if I were you I'd take a look at uBlox NEO-M8 series. I went for this one: NEO-M8U-0-10CT-ND Still waiting for delivery from Digi-Key. I must say here that although Pycom deserves a good word for its innovation and rushing forward with its devices, IMO this rush is very hard on developers that either face unexpected problems with firmware (that sure does not go through any QA), or capabilities of devices or lack of them that never mentioned by Pycom. So, I'd recommend for Pycom to slow down and make their HW more capable that can be used in real commercial devices and their FW reliable.

@papasmurph You're code is not working in iBeacon mode with my WiPy. Any Idea ? No problem at all on Eddystone I'm on 1.20.0.rc13 Thanks !