Hi, Yes, the way the Pytrack/Pysense/Deepsleep shield sleep works is that they disconnect the power from the module, sensors etc entirely. In the case of the Pysense and Pytrack the USB is also de-initialised meaning you will lose the serial connection, this can make talking to the device difficult if it does not wake up for long The Pytrack/Pysense/Deepsleep shield sleep is a a "deep" sleep rather than a regular sleep. Once you use this, when the module wakes up it will be like it was rebooted. Pycom board do not currently support machine.sleep although this is being investigated. The way this differs from the machine.deepsleep is that this uses external hardware and powers off everything on the board, not just the ESP32 processor. You can still use machine.deepsleep if you desire but note that on the WiPy2, LoPy and SiPy, due to an issue with the way the voltage regulator is connected the deepsleep current draw will be quite high (15mA) If you connect P12 to 3.3v with a jumper cable and wait for the device to wake from sleep you will see the on-board LED blink orange. Once this happens you can disconnect the cable. The device will now "safe boot". This prevents the device from running boot.py and main.py and therefore the code putting the device to sleep. The best way to stay informed of firmware updates is to use the forums subscribe feature for the announcements forum. We will always post in there when a new firmware is released

Hi Not noticed the lTE issues as this does not work in the uk. It should keep the almanac and other data when in sleep mode, however the sleep architecture is one where essentially recovering from sleep is a (re)boot, so you need to design accordingly. Also, do not use an SDCard as this will stop the sleep current from going below 5mA. I have not progressed this for over a year. Sorry.

I am looking for a CAD drawing of the expansion board 3.0 as well in order to design an enclosure. Anything available? I can measure it myself, but it would be nice to reference the actual dimensions.

@seb How do we get the position we just get: https://forum.pycom.io/topic/2971/lopy-gps-pytrack-no-coordinates-found

Solved! Thanks again everyone. The problem was indeed that the antenna was mounted according to the specification for the LoPy1r, so it was actually on the LoRa 433-510 MHz antenna slot. After a quick range test I now receive packets at at least 400 meters distance. Many thanks, I thought I had gone crazy there for a while!

@seb First I want to thank you for your help - you have helped me resolve the board detection issue. I understand try/except is the "python way" but as a developer with a much more structured background I was hoping for a solution that might be more robust so as not to encounter issues in the future as the interface or hardware might change. I really do appreciate your time and effort and I understand this is likely the best solution for now.

hey @misterlisty great to hear you are trying to interact with the sensors on the PySense. I have found that watching Alex's Corner Week 7 video on YouTube was the best introduction, together with the basic main.py document on the GitHub and reading the datasheets of course! good luck and don't forget to post your project back on the forum! Phil

@mrainone said in function removed from LIS2HH12.py library module: can you recommend a low cost magnetometer to connect to the lopy I use simple GY-271 (HMC5883L) It working fine for me and is cheap

@combaindeft B) is clear, since the 3.3 regulator is on the FiPy device. Without that, no power at the 3.3V pin. Due to A) with the rock solid supply through a battery it is hard to accept, that it's a firmware issue, at least of the FiPy. Still, the PyTrack board can be the culprit. Did you try to run the FiPy without the PyTrack board, like on a breadboard with a separate USB/serial interface? Shorting 3.3 and GND should be avoided. P.S.: It's a pity that Pycom does not publish schematics.

What version of Windows are you using? If its Windows 7, do you have the drivers for the Pytrack/Pysense installed? You can find instructions on how to install them here: https://docs.pycom.io/chapter/pytrackpysense/installation/drivers.html

@jonasde On the bottom of your Pysense board you will find a 5x2 header you can solder to (see: https://docs.pycom.io/chapter/datasheets/downloads/pysense-pinout.pdf) When I connected it I used P8 and P4 which are availble on pins 9 and 10 of the external header. You will also need to connect to GND and 3V3_Sensor to the modules GND and Vdd pins.

Hi! Please find here the file. Let me know if you need any help. Marco https://www.dropbox.com/s/c3phhysmv1nps98/pycom_ok.dxf?dl=0

@Cormac Yeah the mkfs method has been renamed or just removed. Use os.fsformat('/flash') instead, as i also wrote in my previous post.

I've had the same error and it was due to some junk files on my Fipy. A filesystem reset worked for me: >>> import os >>> os.mkfs('/flash')

+1 External active antenna with LNA would be great. Other boards have this (e.g. Adafruit and NEO boards).

@gnm Glad to hear it finally worked :) I hope the rest of the getting-started experience will be smoother but don't hesitate to let us know if you need anything further.

address 0x08 in the PIC microcontroller on the Pytrack/sense so it is supposed to be there. When I tested this out on a LoPy4 with the latest firmware and a Pytrack with the latest firmware it worked fine the first time. So are you completely unable to talk to the PIC without errors?

@brotherdust any chance you share the pin pad mapping on the bottom (at least RX/TX) ?