I2cset seemed to work (or at least didn't output an error message). I2cdetect is working just fine, showing devices (on 0x11 and 0x19) dev, addr, i2cbus and i2caddress are simply storing address values.) (As the script doesn't contain a lot more than what's seen in the error message, I didn't include it here.
Value1 = read_line_value(i2cbus,i2caddress,0x01)įile "Downloads/read_sensor.py", line 6, in read_line_value Trying to debug using some python code with the smbus package gives the folloving error message: Traceback (most recent call last):įile "Downloads/read_sensor.py", line 14, in Using MatLab's Log signal data and reading from the log tells me: EXT_I2C_write/write: Remote I/O error The Simulink model still builds but there's no action happening.Įdit: using another fresh OS-build I got it to work for now. Then it stopped seconds after begin of successful transmission. Some random day it stopped working.Īt first it just hung-up presumably when there was more data transfer than possible with the set bus frequency. The whole setup (using Jessie) was working just fine. (The boards are controlled by an STM32 microcontroller, the firmware for which was written by a colleague.) This second one provides data from two light sensors. One controls two motors and the voltage (from a battery pack) for the RasPi and the other board. The second to fourth and otherwise identical setups are running Raspbian Jessie.Ĭonnected to the RasPi are two circuit boards using TWI / I2C protocol. It's being transferred to and built on a Raspberry Pi 3B running Raspbian Buster I'm using a Simulink model created with MatLab 2017b.
#MATHWORKS RASPBIAN MATLAB 2017 UPDATE#
I'll update the information to my problem if I missed something or upon your request. I tried to structure it as neatly as possible. It would be a great Christmas present to me if some of you take the time to read and provide inquiry, knowledge or even a solution. Dear community, I'm almost at my wit's end and would be so happy to receive help.