Thanks for testing that. When I have time I'll dive into the terminal code of the atom-ide-ui plugin and see what is causing the issue. Maybe I can make a workaround in the Pymakr plugin to make them act nice together.

@kaspars said in rgbled does not change collor if I2C is used: bus=machine.I2C(1, machine.I2C.MASTER, baudrate=100000, pins=('P3', 'P2')); The RGB LED is using P2. If you use P2 for I2C, it is no longer able to control the RGB LED. See https://docs.pycom.io/chapter/datasheets/development/wipy2.html as an example, this applies to all our modules.

@jmarcelino Thanks for the support! I'll wait for your feedback, best

@tushar44 Version LR5.1.1.0 was the one used for certification

@rcolistete That is incorrect. I'll ask the documentation team to update it.

Are you using a LoPy 1 or LoPy 4? Are you using an expansion board, PySense, PyTrack or Deep Sleep Shield? How are you powering the board? The LoPy 1 (but not the LoPy 4) has an issue with deep sleep which draws more power than initially anticipated (due to the regulator and the on-board flash IIRC), so if you want to achieve currents closer to 10 µA than 10 mA, you need something external to completely power down the LoPy, either the Deep Sleep Shield, or a Pysense or Pytrack (and use the relevant library rather than the built-in machine.deepsleep). Note also that you will only achieve the lowest power draw when powering via the battery connector and not via USB, and without an SD card.

@jmarcelino You are right. I have corrected the connection and it works again. thanks Now I still have the first error when i try to import the library Traceback (most recent call last): File "<stdin>", line 4, in <module> ImportError: no module named ' '

Hi @tom Pycom provides a soldering profile on the L01 datasheet: https://docs.pycom.io/chapter/datasheets/downloads/l01-specsheet.pdf That's what our manufacturing partner uses.

@ea I've actually managed to get it working, however if you check out this thread here, I've just run into a new issue where using multiple pins, each including callbacks, simply causes the first pin pushed to be the only callback which ever runs and only when that pin is pressed. Quite frustrating and unsure what the issue is. https://forum.pycom.io/topic/3173/multiple-pins-multiple-callbacks-not-working-urgent

I have a near identical issue (wipy on pysense stops responding after some time). I have followed the various procedures to reset and reflash both the pysense and the wipy. I have - while the wipy was responsive - entered the stanza above to reset the state of the filesystem. I am still experiencing this as an issue.

@administrators @jmarcelino I have two Fipy’s one installed on a Pytrack board and another on an Expansion Board 2.0. I did a firmware upgrade on the the first Fipy on Expansion 2.0, the whole process never worked and went into safe recovery after multiple tries( with AT+SMSWBOOT=3,0, failed error). Now I have an error code for at command ‘ATI’ on that FIPY. So I have refrained from firmware update on the other FiPy on Pytrack . Now on the FiPy on Pytrack which was not updated ( firmware) it is still responding to lte=LTE(), followed by LTE(‘ATI’), but I get AT+CSQ as 99,99. And on the same FiPy if I do AT+ CGSN, I can get the modem IMEI number but AT+ CCID it does not return the SIM number. It makes me conclude that the SIM and the modem is not talking to each other or exchanging data. Should the system not respond to standard AT command even without firmware upgrade??? My fiest FIPy is already not usable but I don’t want to do the same to the other. I am using two Cat-M1 SIM from Verizon and per one of the suggestions from @jmarcelino , I have already setup a ticket with you tech team. Hope to find a resolution soon! Thank you much for the assistance.

@akshayjames Thank you, I can't immediately reproduce it but have asked the team to look into it

@jmarcelino That did it ! Thanks !!!

I don't know exactly how to fix wrong Win7 FTDI driver problems. I would try to get the latest drivers from http://www.ftdichip.com/FTDrivers.htm and force install them.

Can you tell me what is the behavior of the WiPy when connecting P8 with +3.3v?

Hello, I know the topic is quite old, but has someone managed to make it work ? I have tried with both i2c and HSU (high speed UART), and none is working. With I2C, nothing with i2c.scan. I detect the pytrack accelerometer and gnss but not the PN532 board when connected to (P22, P21), and nothing when connected to (P9, P10) I get no data with UART (nothing returned from uart.read) when connected to UART1, after sending the same frame as with the Arduino to get the firmware version. The board works fine with an Arduino, in both 3.3 and 5V (with PN532 lib & with custom code to get the firmware version) Thanks for any help !