@philwilkinson said in Hand soldering OEM modules: Has anyone managed to successfully hand solder the OEM modules onto the reference boards? Lots of solder. Higher great settings. Patience. Nothing seems to work! Yes I've done this many times. My secret is lots of flux, drag soldering and cleaning up with solder wick and more flux. Most problems come from using too much solder creating shorts underneath the pads or too little solder and not making a solid connection.

Branches + Source Control Git helps a ton. but even an older source control system like SVN would be better than nothing. http://rogerdudler.github.io/git-guide/

@crumble said in Dual processor operation?: @troy-salt User code runs only on one core. The other is used for network related stuff. @troy-salt has it correct.

@misterlisty Pycom bluetooth stack is currently BLE (Bluetooth Low Energy) . And, in BLE there is no SPP equivalent (Simple Port Protocol) as in Standard Bluetooth stack. The BLE normalization is as is, only nordic semi (a ble chip manufacturer) provide a non-standard SPP-like library for it's chip. BUT you can exchange data in BLE, you just have to do it by your self with specific software you write, take a look at how service/characteristics work in ble.

@gabrielapb said in Wake up from deep sleep via accelerometer outputs?: @crumble Thanks, I got this part, but now I am actually asking about this https://docs.pycom.io/datasheets/boards/deepsleep/api.html and https://docs.pycom.io/pytrackpysense/apireference/sleep.html, since both can be used to put Pysense to sleep DeepSleep() is there for those that dont need the extra Pytrack/Pysense functionality. the versions inside the Pytrack/Pysense class are the same as DeepSleep() but included in the Pytrack/Pysense libs as a convinience. . @jcaron has this perfectly. use the Pysense lib.

@rcolistete Thanks for the links. Thats a great start, and already has helped me in the implementation of one of my components. As a noob to Pycom, it really has taken longer than it should have to acquaint myself with where to find information, drivers, tutorials, and examples for Pycom. For instance, the links you provided are very useful, but for a newcomer they are very much in the woodworks, and I still think everything is too scattered. Some consolidation would be greatly appreciated. Even a pinned getting started page with links would be a start. Through comparing a few Pycom libraries that were adapted from Micropython libraries I have gotten the hang of how to convert over libraries. If there was a good centralized place to post Pycom libraries I would be happy to share my adaptations and the libraries I've created for some components that don't have libraries out there at all. A tutorial, for converting libraries would still be great, thanks @Paul-Thornton for your consideration.

@dnear1 So what was the issue then with the scope diagram below: https://forum.pycom.io/topic/4263/optimal-i2c-pullup-resistors/5 That one does not look well.

@rskoniec Yes, I tried it, but it did not work. The type of NFC tage I use is Ntag213.

@paul-thornton Sad that everyone needs to have a subscription model... and an expensive one!

Expansion of the question is, how can i stream data from bluetooth to my phone? Is theire serial bluetooth? Want to be able to views logs of device in the field.

@jcaron, ah, that is a shame - but thank you for letting me know. I was hoping this could be done passively, without having to build an iOS app. Basically, I am trying to get the Pycom board to search through the advertising BLE devices on startup to determine if a specific one, my phone in this case, is present or not. Then the board will take one of two actions depending on if the phone is present or not. In standard Bluetooth, there is the process of pairing, where two devices can in effect remember each other. I was hoping there would be an equivalent for BLE.

@robert-hh said in MicroPython 1.8.4 released: @martinnn This is just a kind of spam. This person is just pasting related or even not related material from the internet as contributions. That happens quite often. I do not know the purpose. You and me both. we get the strangest spam. Edit: Just to say thanks to those who report these. we do act and review all the reports. user above is now banned.

@snehasg96 main.py is executed automatically when the device boots. If ouy wnat to run a script, like recv.py, manually, just enter at the REPL prompt (the one with >>>): import recv

@misterlisty Crash dumps contain some state about the device and running code at the point it had an error. with the right tools and source code you can see what was happening on the device when it crashed and try and locate the source of the error. Im not sure we have all the tooling to diagnose a crash dump public. Let me confirm with the team and check I could be wrong.

@misterlisty that’s about as vague as it gets... I recommend you start by reading the accelerometer’s datasheet to learn of its capabilities. An accelerometer detects just that: acceleration, and you can sample the acceleration values at regular intervals to try to detect all sorts of things. I believe you can even “stream” the values samples by the accelerometer. But high frequency vibrations for instance may be an issue as they may exceed the capabilities of the accelerometer. High sampling rates may also be an issue if you have lots of computations to perform. It’s really difficult to help you much further without any indication of what exactly you are trying to measure / detect, and what the threshold are.

@robert-hh thanks there is not much described here about the standard values in the initialiazation.