@Youssef-Elwakil are you running an app on your phone or your PC that advertise something? Use a BLE scanner app on your phone. If that app can’t detect the device, neither will the GPy.

@thinginnovations Thanks. Yes I am using reed switches for reset and Mode on opposing ends of the case. I will add another PIN for interrupt.

@jcaron Thanks for the clarification. Okay, Then how about the second part of my question? If I import a library, does the whole library (including unused functions) get loaded into / waste memory? Thanks, Troy

@Fred I haven't seen a schematic so I can't really comment on the performance gains you are referring to but unless i've missed something any circuitry before the connector (SMA/MMCX/u.fl or otherwise) is in most cases independant of what it's connecting to. From what i've seen there's already a manual active antenna switch in the form of a jumper (AON?) which negates the need for any electronic switching mechanism, unless you mean for the internal/external antenna feed, in which case i would have thought doing away with the passive onboard module altogether would have been the solution as in 'real world' conditions it's use is very limited. Perhaps you can clarify, I may be getting the wrong end of the stick here. @Gijs @jcaron Thank you for your recommendations, I had considered MicropyGPS before starting this thread as i've had a fair amount of experience with it in the past, however it doesn't seem to play nicely on Pycom modules and causes it to crash (also as a frozen module). Regardless, as the dump_nmea() function simply prints the sentence it can't be used to feed the update() function within MicropyGPS. If i get a spare few minutes I'll write some stuff for the Pycom lib, in the mean time i'll have a go with L76GNSV4 :)

it's not possible to use only the library provided on github? Since i have a lots of lopy4 and provision the mesh from Pybyte is not feasible

Hi, Ive been working with our datasheet designers to get this fixed. Unfortunately it still has not been fixed due to other more important work. Sorry for that, Gijs

Thanks, in the FAQ's section I also found a little more information, in case someone else has this concern. https://pycom.io/learn/faqs/

Hi, There can be many reasons for a coredump (I think is what you are describing?). I tried to make a guide to help you debug the output yourself here: https://docs.pycom.io/advance/coredump/, but it is quite complicated and requires some experience. If you keep getting the same traceback in your coredump, I can check the cause for you if you can tell me the exact firmware you are using (incl Pybytes/ Pygate version). At this time Im unable to check your code as it requires some external components I dont have.. You mention they are typically caused by this, so not always? We know it is possible for the LTE connection to drop, as the environment is constantly changing. We therefor advise to only connect to LTE when you need to send data, and then disconnect again. Best, Gijs

In the latest version (1.20.2.r0) os.fsformat() is available, and os.mkfs() does not work.. Which firmware version are you running then? On the other parts, I totally agree with you. Im looking for the best method to document such things to be more complete in the documentation, and not make it more confusing for beginners. If you have some documentation style you prefer, let me know! Gijs

Hi, Sorry if I was not clear. The Pygate does work fine with the GPy, the only issues we are currently running into is the RF LTE connection not always being sustained. This is the case with many wireless devices, where you simply cannot rely on always being connected. There are several factors (outside our control) that influence the stability. We are currently working on tests to recover the connection gracefully once it has dropped. This issue is also at hand without the Pygate, but before we saw no use-cases where the connection had to be sustained for longer. Gijs

@trojanc Well, i have a talk with a sigfox founder. First news about this topics is Sigfox France Network now sell device subscription by year for one device. Unfortunatly this will not help you in this case, sorry. It seem that kenya and south africa is not still available on buy.sigfox.com, as all technical event is off i dont know where i can see someone from sigfox in futur to ask us some news.

Hi, I believe the documentation is outdated. To circumvent it, you can use a try-except statement like here: (You can also specify the exception in more detail) try: counter = pycom.nvs_get('count') except Exception: counter = 0 Best, Gijs

@pwest The worst-case interrupt latency that I measured on pycom's Wipy board was approximately 1 ms (measured with an oscilloscope). I did not find the timerchannel.capture ([value]) method on the micropython implementation of pycom. In the meantime I switched to the Pybord D series with an STM32F7. The measured interrupt latency is approx. 30us and the timer.capture method is implemented and can be called within the callback routine. Measurements in the us scale are no problem, so this solution works for me.

i'm having a dou't wether we can use lopy4 as a access point or are we able to use this as a wifi hub that may be join to computer after which can it be used as a usb dongle.