@jcaron as of right now what I want to achieve: Using a SCD30 sensor (which gets humidity, temperature and CO2 levels) read the data and save it, for that I intend to create (or modify based on other libraries) the library for the sensor. I already have the adress of the sensor and the hexadecimal "commands" and I am trying to use the libraries of the Pysense sensors as a template

@dan I understand that and get this error when I flash it, but I would also like it to link in Atom so I can build and run it right away without having to flash it. [image: 1537809779016-2f6c007e-17d2-4496-a1eb-b82c77973113-image.png]

Hi @nobo23 Are you trying to connect multiple sensors to the WiPy and communicate with them via Bluetooth? Connecting multiple BLE nodes to the WiPy is possible. You can find our BLE examples here. Hope this helps, let me know if you have any questions!

@robert-hh said in Wipy 2.0 and save data on my pc, not in flash memory: Which BN055 module I was asking about the vendor and make of the BNO055 board.

@nobo23 Accirdoig to the datasheet, you can operate that device from the 3.3V output of the WiPy. That matches the signal levels of the I2C interface. Since the module has built-in pull-up resistors (if you install the jumpers), you do not have to add additional ones.

Later I realized I needed to download the pycom libraries in https://github.com/pycom/pycom-libraries. There was the mqtt lib and now it works. Isn't this supposed to be in the online documentation? Thank you.

@jimpower Oh, didn't realize you had changed devices. So do you get a value equivalent to 4ma through the INA device (may need to be scaled) ? when not in the water ?

Here is the Library logging.py

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.

@noboz32 Do you mean just seeing what devices are connected to I2C? If so, please see the i2c.scan() function: https://docs.pycom.io/chapter/firmwareapi/pycom/machine/I2C.html#i2cscan

That worked! Thank you..

@seb No luck with pull up resistors. There is also garbage when connected on P22/P21. PyTrack connected to the same pins with the same settings goes smooth. While connecting our L76-L there is no response on I2C ;-( only garbage response for i2c.scan(). Maybe you reconfigure L76-L chip through UART after mounting ? Will try to connect oscilloscope and/or logic analyzer

@incognico said in Reading BNO055: Maybe try adding some lower value pullup resistors. From the FAQ page of your device BNO055 FAQ #4 "Depending on your system setup, you might need to adjust the pullups on the SCL and SDA lines to be a bit stronger. The BNO055 has very tight timing requirements on the I2C bus, requiring short setup and rise times on the signals. By default the breakout board has 10K pullups, which might be too weak on some setups." I had a similar problem. I'm not sure if it's been fixed or not, because I haven't tested it lately. Anyway, it had to do with I2C Clock Stretching. For me the solution was to set the I2C baud rate as low as it would go and work my way up until i found the fastest value that worked. Maybe give that a try, if you haven't already. =)

@robert-hh Okay, understood. Will test and update here with my findings. Thank you again @robert-hh for your great great support!

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?

Never mind I found the problem. It was actually in the line above paramVal = self._device.readfrom_mem(self._address, SI1145_REG_PARAMRD, 1)

@lopyusr I apologize, I misunderstood. I provided too much info on something not your issue. I'm assuming you are using this driver and example: HERE And documentation HERE