Navigation

    Welcome to the Pycom forum

    Forum

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    1. Home
    2. Tags
    3. i2c
    Log in to post

    • E

      LoPy4 - I2C - FRAM Memory - MicroPython Library
      MicroPython • i2c fram • • Eric Tremblay  

      27
      0
      Votes
      27
      Posts
      118
      Views

      J

      @Eric-Tremblay Ah sorry I had missed that. No, the message is correct. The address is on 16 bits, so takes two bytes to send. What happens when you try a read?
    • T

      TSL2591 runtime error: Overflow reading light channels
      MicroPython • i2c library tsl2591 runtime error • • tttadam  

      6
      0
      Votes
      6
      Posts
      62
      Views

      T

      It looks like you are using signed intergers/numbers for the reading from the light sensor. When it reaches the half way value it wraps around and goes negative. If you simply define the data as an unsigned type does it fix the issue.
    • T

      random I2c adresses
      Discussion • pycom i2c am2315 • • tttadam  

      9
      0
      Votes
      9
      Posts
      254
      Views

      T

      I think the issue was with my breadboard psu... So right now I am using the pycom 3.3V
    • shanefowler25

      I2C OLED Screen Error
      MicroPython • micropython i2c ssd1306 oled display • • shanefowler25  

      7
      0
      Votes
      7
      Posts
      608
      Views

      robert-hh

      @kjm All versions have a usable I2C. The case here is a different one, I assume. @shanefowler25 : Can you publish the full error message you got. It should be more than one line. The framebuffer module is included now. It sneaked in when Pycom moved to MicroPython core V1.11.
    • T

      1602 LCD and I2C backpack with pycom
      MicroPython • i2c lcd displays 1602 • • tttadam  

      17
      0
      Votes
      17
      Posts
      1360
      Views

      robert-hh

      @Lucas_Vieira I'm missing the print statements form the script. So your test script is not executed at all.
    • W

      Best power source for using 5V sensors
      Expansion Board • expansion board i2c battery expansionboard levelshifter • • weingami  

      7
      0
      Votes
      7
      Posts
      772
      Views

      M

      @weingami Note that I2C level shifting is particularly easy as it uses an open drain-pullup signaling scheme. Shifting can simply be done with two FETs: https://electronics.stackexchange.com/questions/255607/i2c-level-shifting-mosfet
    • D

      Optimal I2C pullup resistors
      Discussion • i2c • • dnear1  

      14
      0
      Votes
      14
      Posts
      1207
      Views

      robert-hh

      @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.
    • B

      Display logo on screen
      SiPy • i2c ssd1306 screen • • brossingo  

      4
      0
      Votes
      4
      Posts
      476
      Views

      C

      @brossingo Do you use a pycom board? Then add some wait. You have to wait until the *Py and the board is initialized. Sadly there is no flag or event which tells you that init is ready. So you have to find the right time for your system by your own. It will depend on firmware version and the hardware you added - especially your display. Give 1.20 rc4 a try. This version solved my problems with i2c and pytrack
    • D

      Help with BME280 on Wipy 3.0 + Expansion Board 3.0
      WiPy 2&3 • expansion board i2c wipy 3.0 bme280 • • Dezert754  

      3
      0
      Votes
      3
      Posts
      474
      Views

      D

      @robert-hh Works like a charm, thank you so much!
    • S

      GPY/FiPY & Expansion Bd 3 - Multi I2C and SD Card Instances
      Discussion • fipy gpy expansion board i2c spi • • Stevo52  

      25
      0
      Votes
      25
      Posts
      3535
      Views

      S

      @robert-hh OK, I set up some code to try this out, several timers at different periods and several threads including one to start LTE, send an SMS and then deinit. From what I can see, the timers do NOT get interupted by the LTE device. It seems the timer counts are retained and dumped to REPL as soon as possible (buffered apparently). There is some corruption/mixup of REPL lines but all the timer flags are there I will investigate a bit further and see if I can use this to my advantage. One thread/timer I will need will be at 11uS preferably, so as it is too fast to capture by eye, I'll have to write to a file to a file to evaluate any impact by the LTE device. Biggest constraint might be the actual time to write to disk. A FIFO data buffer is probably a good solution - some work to do there. The test code was pretty rough and ready so its needs a lot of refinement to be truly useful as a valid test.
    • M

      OS Error: I2C bus error on wipy 3.0 with BME 680
      Getting Started • i2c wipy3.0 i2c bus error bme680 • • Modellhaus  

      6
      0
      Votes
      6
      Posts
      916
      Views

      M

      @robert-hh Thanks, I'll try that.
    • O

      Some magnetometer sensors are incompatible with the pytrack shield
      LoPy • lopy i2c sensors magnetometer pytrack i2c • • oldGuyDave  

      13
      0
      Votes
      13
      Posts
      1289
      Views

      O

      @robert-hh I looked at that device but I'm trying to keep my system as simple as possible so I did not pursue that option. I does, however, look like a viable alternative in the event your s/w solution was inadequate for some reason. thanks.
    • S

      Help with I2C connection to BME280 on WiPy 2.0 ...
      WiPy 2&3 • i2c wipy2.0 expension board • • sealyons  

      22
      0
      Votes
      22
      Posts
      5293
      Views

      robert-hh

      @sealyons I made a test with the calibrated temperature mesurement device: Calibrated device: 21.7 21.8 DS18B20: 21.9 21.9 DHT22: 21.8 21.9 SI7021: 21.7 21.8 BMP085: 22.4 22.5 BME280: 21.8 21.9 Besides the BMP085, all devices were on the spot = within 1 digit variance. That status was stable for 5 hours testing. Only the BMP085 was always ~0.6 °C above, but still that at the limits of it's spec.
    • B

      Object with buffer protocol required
      SiPy • i2c ssd1306 buffer downlink • • brossingo  

      3
      0
      Votes
      3
      Posts
      1478
      Views

      B

      @Eric73 Thank you, it works much better now!
    • S

      i2c device Wiring on Expansion Board & WiPy 3.0
      Expansion Board • i2c wipy3.0 expansionboard • • svonbentzel  

      7
      0
      Votes
      7
      Posts
      1196
      Views

      S

      @eric-waai Yes it was a typo I have 3 i2c devices
    • T

      SI7021 I2C pin setup (SOLVED)
      MicroPython • micropython i2c si7021 • • tttadam  

      59
      0
      Votes
      59
      Posts
      12883
      Views

      T

      @robert-hh Awsome! Thank you
    • C

      write word with I2C
      MicroPython • i2c bit shift • • cmisztur  

      5
      0
      Votes
      5
      Posts
      824
      Views

      C

      @robert-hh Thanks for the tips. I ended up doing below, which does save 32bytes over struct.pack. self.tempBuff = bytearray(3) def _writeWord(self,address,data): #self.i2c.writeto_mem(self.address, address, struct.pack(">H", data), addrsize=8 ) self.tempBuff[0] = address self.tempBuff[1] = data >> 8 self.tempBuff[2] = data & 0xff self.i2c.writeto(self.address, self.tempBuff)
    • D

      I2C on Wipy 3.0 + extension board
      WiPy 2&3 • i2c wipy3.0 • • DR_ALOUI  

      9
      0
      Votes
      9
      Posts
      1167
      Views

      robert-hh

      @dr_aloui In that case it's strange. You you have an oscilloscope to look at the signal timing? The expansion board should not add any significant load to the wires, at least not to P9 and P10. The Pyboard has built-in pullup-resistors on the pins dedicated for I2C (X9/X10 and Y9/Y10). That could makes a difference.
    • 1
    • 2
    • 3
    • 4
    • 1 / 4