@chrisi Are you measuring over USB or on a battery? According to this post: https://forum.pycom.io/topic/1460/power-consumption-deep-sleep-pysense-pytrack/20 you'll get about 10 mA more over USB. Also, are you using the expansion board, Pysense, Pytrack...?

@RobTuDelft The comment in the example is wrong. Maximum is 19455. For an input value between 19456 and 19531 you'll get 19531 Hz. Generally, the precision is low at the higher frequencies. So specifying a value of 19000 give 19011 Hz, 19200 -> 19230. So it looks as if the "real" periods are multiples of a small value like 200 ns.

@Jiemde It's working here >>> py = Pysense() >>> print (py.read_battery_voltage()) 4.11466 Make sure you have everything up to date: the Pycom board, the pycom-libraries and Pysense/Pytrack firmware

@jmarcelino got that ;) i prefer the sparkfun then because I can plug a standard cat5e cable which is widely available. Thanks for your help!

@jcaron said in First steps with LoPy & PySense and feedback: The cases (probably) fit the expansion board, but not the PySense. Wouldn't hurt being a bit more explicit about it on the site. Are there any cases that would fit the PySense? +1 for the cases issue. I bought a PySense and a PyTrack and a case for each. Pretty frustrating that there aren't the appropriate mounting points in the case for those boards.

@jmarcelino it sure would be very interesting but unfortunately i work almost alone and I have 3/4 months to get the things full working, and i was lucky enogh to start the project in summer season. I hope the gpy/fipy will be released before september so i can build the lte support for it or i'll have to deal with another problem lol

@aldrinleal your parser is really minimalistic and do not check crc and fix the best i have found was https://github.com/inmcm/micropyGPS/blob/master/micropyGPS.py it need some modifications to be more usefull and you extend error handling. Also at the end you need to add GLONASS commands to the list - but work like a charm :)

Rock and roll! Good timing.

Hi @Jen, I think you might be in the wrong place! These forums are for the Pycom (https://pycom.io) products such as the WiPy, LoPy, etc. It seems as though you are using the Raspberry Pi which uses a different version of Python from that found on our devices! I'll point you towards https://www.raspberrypi.org/forums/ to find some more support for your issue! Thanks! Alex

@tholden PIC should also be able to wake up the Pycom board from deepsleep for example if movement is detected by the accelerometer.

Thanks for the input. However, i already did use P9 en P10 for buttons. I'm using the pytrack for a movable cache (geocaching) and need some more user interaction than - probably - normaly would be used with an iot-device.

@cfaessler No, the maximum input voltage is 5.5V. You'd have to use an external regulator.

@bartp The model name of the liPo batteries is they dimensions, for example: DTP603443 - "60" is 6,0 mm of max tickness, "34" is the max width of 34 mm and "43" is the max lenght of 43 mm. So with the dimensions you can find the capacity you need.

Use pytrack.py from https://github.com/pycom/pycom-libraries/tree/master/pytrack/lib. Copy pytrack.py to /flash/lib. Test: import pytrack py = pytrack.Pytrack() print( '{}V'.format(py.read_battery_voltage())) Dispaly is 4.686702V hope it's help you.

I recommend playing a bit with motors and motor drivers on some cheap Arduino clone. Get a 3.3V (volts) version, like the Arduino Pro Mini 3.3V - these can be had for less than $5 on Ebay and AliExpress - before moving to tests on an expensive FiPy. Once you have the logic figured out it should be easy to move to Python.

@tainanfish You might be surprised what LoRa can do (and remember in LoRa you CAN set the TX power) but if the question is just cost, then the GPS will be about the same ($8 for a GPS module, same as a LoRa module) To me the problem with GPS is it's even higher power consumption than WiFi.