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
New I2C sensors supported
#21
Testing more sensors, in fact former  sensors used with OP1.17 !

Pypilot reports : IMU détecté: STMLSMDS50 working : not really : boat is rotating in calibration then stabilizes (level), but get rolling all over again when moving the sensor, values displayed but unstable (highly) in OpenCPN dashboard ! EDIT : After more calibration, stability tends to improve
Connection : in I2C app :  no sensor name, UDP 20220, in Pypilot app : Signal K cap, gite, tangage, UDP, 20220, Pypilot Signal x

I2C : sensor identified wrongly as  BME280 ; 0x1a(x3), in fact 2 sensors : HTU21 (gy21) humidity & temperature & and  BMP180 (gy68)  pressure ;  environment O/S pressure, O/S temperature, I/S humidity; rate : 1 (x3) ;step : 0 (x3) :Raw : yes (x3),
Connection : BME280, port 5100, but no value displayed in OpenCPN dashboard.

Signal K dashboard shows 3 connections :
  • Open plotter GPSD, flashy 4 delta/second
  • I2C steady 0 delta/second
  • Pypilot signal K, flashing, 2 Delta/second

i2cdetect -y 1 reports many addresses : 1a, 1e, 40, 6b & 77 !
Cordialement
Didier B
Pi4, SSD USB3, OP 2.7.0 OC  5.2.4




Reply
#22
(2020-11-26, 08:49 PM)jpaul1 Wrote: Hi
Wow that was quick...

I think I have done what you wanted and it seems to be fine.
I unzipped the file, put it in my local directory
/usr/local/lib/python3.7/dist-packages/adafruit_bmp3xx.py
then I removed the sensor/connection from openplotter I2C
and reinstalled the sensor/connection...

and it is working fine, and passing data to signalK

I hope I have done it right..
Let me know if you need me to check anything else.
Kind regards
Jeremy

That was right. The commit was accepted so now we have to wait for them to update the pip repository. Thanks!
Reply
#23
(2020-11-27, 10:28 AM)Didier B Wrote:
(2020-11-26, 07:00 PM)Sailoog Wrote:
(2020-11-26, 05:57 PM)Didier B Wrote: Once more this afternoon, the disparition of I2C data occurred . This time, I could restore the I2C by simply removing the I2C GND wire, and when I reconnected that wire, all data as shown back (both Piylot and I2C) : no need to switch power off then on again !

What sensors you have connected?  GY91 breakout including MPU9250 and BMP280
What sensor is failing? BMP280
What "i2cdetect -y 1" returns when this happens? I'll post (here, by editing) at next occurence (now : 1a, 68 & 76)

Hello Sailoog, sorry for the delay, but it only occurred a few min ago, missing address is 76, but where is the issue : BMP280 part of my GY-91 breakout, or with the I2C app ?
I have spare IMU & environmental sensors, I am testing them from now on !

If the address disappears you should have a bad connection or a faulty hardware.
Reply
#24
(2020-12-01, 08:18 PM)Sailoog Wrote:
(2020-11-27, 10:28 AM)Didier B Wrote:
(2020-11-26, 07:00 PM)Sailoog Wrote:
(2020-11-26, 05:57 PM)Didier B Wrote: Once more this afternoon, the disparition of I2C data occurred . This time, I could restore the I2C by simply removing the I2C GND wire, and when I reconnected that wire, all data as shown back (both Piylot and I2C) : no need to switch power off then on again !

What sensors you have connected?  GY91 breakout including MPU9250 and BMP280
What sensor is failing? BMP280
What "i2cdetect -y 1" returns when this happens? I'll post (here, by editing) at next occurence (now : 1a, 68 & 76)

Hello Sailoog, sorry for the delay, but it only occurred a few min ago, missing address is 76, but where is the issue : BMP280 part of my GY-91 breakout, or with the I2C app ?
I have spare IMU & environmental sensors, I am testing them from now on !

If the address disappears you should have a bad connection or a faulty hardware.
Yesterday I replaced my 'clips' connection with a Dupont cable, we will see ...
Cordialement
Didier B
Pi4, SSD USB3, OP 2.7.0 OC  5.2.4




Reply
#25
Great Job : testing OP 2.6.2 and I2C 2.2.1 since this morning (with new Dupont cable) : so far so good   Exclamation   Smile
Sailooog I confirm the issue was in the H/W Angel
Cordialement
Didier B
Pi4, SSD USB3, OP 2.7.0 OC  5.2.4




Reply
#26
I have question about Rapsberry Pi4 and BMP180. There is BMP280 on list of supported sensors but there are no BMP180. Do you have idea the BMP180 should work in place of BMP280 (on the same driver) or not? I have connected BMP180 to Rapsberry in BMP280 place and it is visible on address 77 like presure and temperature sensor but there any (visible ) data was sended by this sensor to Signal K. I have connected it on UDP 51000. But i dont see any data on NMEA monitor in OpenCPN.
It is only becouse im used PMB180 in place BMP280? or there are something wrong with my configuration of Signal K and OoenCPN?
Reply
#27
I2C app does not send NMEA 0183 data, it sends signal k data. OpenCPN NMEA monitor only reads NMEA 0183. You have to create a signal k connection in opencpn or check if you get data in signal k admin page
Reply
#28
Thank you for answer, Today i recived BME280 and i connect it in the same way like BMP180 .
BME280 was working perfectly .
BMP180 is visible in Rapsberry - and in Signal K but signal from BMP180 is not visible in Opencpn and or not working on BMP280 and BME280 "drivers".
I dont have knowledge to compare comuniication protocol of that two sensors.
Anyway BME280 works ok BMP180 is vissible but not working.
Reply
#29
(2020-12-10, 08:28 PM)Divemaster Wrote: Thank you for answer, Today i recived BME280 and i connect it in the same way like BMP180 .
BME280  was working perfectly .
BMP180 is visible in Rapsberry - and in Signal K but signal from BMP180 is not visible in Opencpn and or not working on BMP280 and BME280 "drivers".
I dont have knowledge  to compare comuniication protocol of that two sensors.
Anyway BME280 works ok BMP180 is vissible but not working.

I would also like to enable support for the older bmp180, while it show up at 0x77 there is no menu entry for bmp180 and hence it does not work, e.g. no data. 
While it's possible to upgrade to bmp280 it would be great if the support for bmp180 could be enabled again, my bmp180 sits on a hat and the module is not plugable.

Ole
Reply
#30
(2020-12-17, 07:52 AM)olewsaa Wrote: I would also like to enable support for the older bmp180, while it show up at 0x77 there is no menu entry for bmp180 and hence it does not work, e.g. no data. 
While it's possible to upgrade to bmp280 it would be great if the support for bmp180 could be enabled again, my bmp180 sits on a hat and the module is not plugable.

Ole

Do you have any python3 script for the bmp180 we can use?
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)