@jmpratt I cannot believe that you have the same code on both WiPy's. Please reload the code to both devices, reset them and try.

@dan Yep I have never put anything in boot.py, have always had main.py run without intervention.

@capnahab The Expansion Board 3.0 is already shipped with the latest firmware. The one posted on https://docs.pycom.io/chapter/pytrackpysense/installation/firmware.html is for reference only and identical to the one already flashed at the factory.

@robert-hh The hearbeat LED flashes when the board and code are working properly. If I notice that the data is not updating, I'll go look at the board and the heartbeat LED won't be flashing. I'll hit the reset button on the board and everything will work normally again. I think I'll setup an identical rig but power the USB power port from a variable DC supply. Then I can turn the voltage down and see what happens.

@pedrofelipest said in nrf24l01: Please verify a) the intended connection as below CE on P6 -> GPIO27 CSN on P21 ->GPIO26 SCK on P22 ->GPIO25 MISO on P12 -> GPIO21 MOSI on P20 -> GPIO33 b) The semantics of the SPI method may be different between the poerts. Please compare the different ports (Pycom and micropython) by printing the results and self.buf content from write_register and read_register.

I spoke too soon! >.< From a fresh wipe and firmware upgrade, I was able to run the I2C library. However, once I loaded my own modules onto the device and used them to connect to my network, calling "init" on an I2C instance caused the WiPy to freeze (connected over serial, but I could no longer type into the console). I built a bit-banged version of I2C yesterday and am able to use it on the same pins ("P8", "P9") without issue.

Hi @fbt said in problems with service_data field on advertisement packets: it is possible to configure the wipy not to send those fields? Sorry, this is not yet possible.

@dda Are you sure that you are not mixing up number schemes P and G? P9 and P10 are the default pins for SDA and SCA, and these are not used for the SD card. Besides that, switching uses might be possible, but you would have to re-init and re-mount every time between each access. Better change the board.

Hi @jmarcelino, wow you're right a reminder to always read exactly!! Thanks so far! Now I ran the program with the corrected PINs several times but I still have the issue that I get sensor readings just at a maximum one time per run. I am sure the Hc-sr04 has 5V as needed and the logic level converter should also not be an issue as both trigger, echo and ground are correctly connected to it. I annexed the Atom Output to this post after uploading the new program: Running C:\Users\pmb\Desktop\Wipytest\wipysensortest.py Distance 1 cm Disconnected. Click here to reconnect. Connecting on COM5... Running C:\Users\pmb\Desktop\Wipytest\wipysensortest.py Disconnected. Click here to reconnect. Connecting on COM5... Running C:\Users\pmb\Desktop\Wipytest\wipysensortest.py Traceback (most recent call last): File "<stdin>", line 34, in <module> KeyboardInterrupt: raw REPL; CTRL-B to exit Disconnected. Click here to reconnect. Connecting on COM5... Running C:\Users\pmb\Desktop\Wipytest\wipysensortest.py Running C:\Users\pmb\Desktop\Wipytest\wipysensortest.py Distance 45 cm Disconnected. Click here to reconnect.

Hi @ricardo85 Can you share what water flow meter you're planning to use? Are you sure you want the WiPy to be a transmitter or a receiver?

Thanks everyone, safe boot procedure by holding pin 12 high during reset completely solved my problem!

@xykon Note to self: connect the ground of the USB-to-serial converter to the WiPY's ground :) This was the issue all along. Can't believe it actually worked in putty though Thanks for all the help.

@seb Thanks for pointing out!

@jmpratt For the WiPy2 you will need to follow the instructions found here: https://docs.pycom.io/

I'm testing this code with the correct frequency but i had probleme call "OSError: I2C bus error" in initialisation. i use the sipy on the P9 and P10 and i didn't use int out it's on this lines print("initialize") whoami = self.i2c.readfrom_mem(self.addr, _MAG3110_WHO_AM_I, 1) print(binascii.hexlify(whoami))

@spacelggo I do not remember what was the cause of slowness you can try to find info on the forum. I suppose that this was releated directly with SD driver not SPI itself. Someone tested this i do not tested this myself. I use always direct connection and built in driver.