This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Problem with i2c: enabled | not running
#11
(2023-01-24, 06:39 PM)Sailoog Wrote: Are you sure you are using the right adress? this chip usually uses 0x76 or 0x77

I think I did. In fact, in Openplotter I2C screen (see attached), the connection is made. 
.pdf   Naamloos.pdf (Size: 1,019.97 KB / Downloads: 146)
The Openplotter I2C connection is allowed in Signal K, but nothing appears in the Data browser.
Reply
#12
The connection is made even if you add a wrong address, click on "I2C addresses" to see the detected addresses.
Reply
#13
(2023-01-25, 07:44 PM)Sailoog Wrote: The connection is made even if you add a wrong address, click on "I2C addresses" to see the detected addresses.

It shows the address 76, as expected.
The check system overview shows: "openplotter-i2c-read not running"


Attached Files
.pdf   Naamloos.pdf (Size: 1 MB / Downloads: 119)
Reply
#14
You have also "1a" and "68". what is that?

I remember reading somewhere on this forum about faulty BME280 boards. I should have one somewhere, I'll try it as soon as possible.
Reply
#15
(2023-01-30, 01:03 PM)Sailoog Wrote: You have also "1a" and "68". what is that?

I remember reading somewhere on this forum about faulty BME280 boards. I should have one somewhere, I'll try it as soon as possible.

I've got a heading sensor on I2c as well. If I recall correctly, that one is on 1a. Don't recall the 68 address.
The board used to work under Openplotter 2, and this issue only occurred after updating to Openplotter 3.
Reply
#16
I have just tested my BME280 and is working right. Not sure what to do now. Could you test your sensor in OpenPlotter 2 to confirm still works?
Reply
#17
Hi all,

great work with OpenPlotter!
I have the version 3 (64bit) on an Raspberry Pi 4 8GB with Raspian 64bit.
I have connected via I2C a Bmp280 Sensor via the adress 0x76.

When I start (boot up) the system, no temperature or pressure signals are transmitted.
Only when I log in dirctly to the screen on Raspian, the system check runs, and from the part where the OpenPlotter packages are checked it transmit all the data colected via I2C.

What can I do here?

Thanks for a good solution!

Mitch
Reply
#18
(2023-02-11, 04:59 PM)Mitch Wrote: Hi all,

great work with OpenPlotter!
I have the version 3 (64bit) on an Raspberry Pi 4 8GB with Raspian 64bit.
I have connected via I2C a Bmp280 Sensor via the adress 0x76.

When I start (boot up) the system, no temperature or pressure signals are transmitted.
Only when I log in dirctly to the screen on Raspian, the system check runs, and from the part where the OpenPlotter packages are checked it transmit all the data colected via I2C.

What can I do here?

Thanks for a good solution!

Mitch

Enable "Auto Login" in Raspberry Pi configuration.
Reply
#19
It seems to me that I2C Sensors (3.3.12) on OpenPlotter (3.5.0) may be broken.

Running i2cdetect -y 1 from the command line has my BME280 showing up at address 77. However, when trying to run this from OpenPlotter, nothing appears.
Reply
#20
In addition to the above system details:
  • Raspberry Pi 4 Model B Rev 1.4 on Debian GNU/Linux 11 (bullseye)

Below is a partial output of my log. In addition to the inability for SignalK to connect to influxDB, the vcgencmd command on my pi doesn't exist where Signal K expects it to be but rather at/usr/bin/vcgencmd ...

Mar 26 21:59:16 Error connecting to InfluxDb, retrying in 16000 ms
Mar 26 21:59:17 GET /signalk/v1/api/vessels/self/uuid 404 3.103 ms - 171
Mar 26 21:59:19 signalk-to-influxdb:Error: A 401 Unauthorized error occurred: {"code":"unauthorized","message":"Unauthorized"}
Mar 26 21:59:19 Error: A 401 Unauthorized error occurred: {"code":"unauthorized","message":"Unauthorized"} at IncomingMessage.<anonymous> (/home/inspired/.signalk/node_modules/influx/lib/src/pool.js:50:38) at IncomingMessage.emit (node:events:525:35) at endReadableNT (node:internal/streams/readable:1358:12) at processTicksAndRejections (node:internal/process/task_queues:83:21)
Mar 26 21:59:22 GET /signalk/v1/api/vessels/self/uuid 404 8.785 ms - 171
Mar 26 21:59:25 GET /skServer/debugKeys 304 3.645 ms - -
Mar 26 21:59:27 GET /signalk/v1/api/vessels/self/uuid 404 3.471 ms - 171
Mar 26 21:59:28 sudo: /opt/vc/bin/vcgencmd: command not found
Mar 26 21:59:28 sh: 1: mpstat: not found
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)