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
Multiple busses on GPIO
#1
Hello,
I’ve managed to create a second SDA and SLA connection using some code in the CLI that added a second bus on the GPIO pins for multiple sensors and it’s showing up in terminal “sudo i2cdetect -y” search but when I look to add the sensor in Openplotter i2c app, it doesn’t show up so I take it that OP only listens to one single bus and you have to wire multiple sensors in parallel?
Reply
#2
you can have up to 128 devices on the I2C bus no need for the second bus

https://www.robot-electronics.co.uk/i2c-tutorial
Reply
#3
(2021-05-03, 05:22 PM)jim321 Wrote: you can have up to 128 devices on the I2C bus no need for the second bus

https://www.robot-electronics.co.uk/i2c-tutorial

Good to know, thanks Jim! Now the next question is what if I have two identical INA260 sensors, that I'm still trying to figure out how to get in OP, one for house and one for starting Batts. They seem to be registered in the i2C protocol as having address 40.
Reply
#4
Photo 
assign a different address to one of the  boards

soldering the A0 pad of the board you set his address to: 0x41

soldering the A1 pad of the board you assign the address to: 0x44

[Image: sensors_cropped_front.jpg?1556734366]
Reply
#5
(2021-05-04, 03:55 PM)jim321 Wrote: assign a different address to one of the  boards

soldering the A0 pad of the board you set his address to: 0x41

soldering the A1 pad of the board you assign the address to: 0x44

[Image: sensors_cropped_front.jpg?1556734366]

Well, I guess if I RTFM'd the damm board I would've known that! My apologies. Now, bigger question, have you been successful in setting these INA's up in OP? IE: what are the actual sentences in i2C etc...
Reply
#6
no i haven't messed with the software for over a year. there should be no problem setting them up thought, many people have been successful with it.
Reply
#7
on the SignalK slack site I was talking to somebody ([b]xbgmsharp) [/b]and he had created a plugin to use https://www.waveshare.com/wiki/Current/P...onitor_HAT as a 4 channel power monitor.  he said he was going to publish it.  also there is a thread about it: https://forum.openmarine.net/showthread.php?tid=3197
Reply
#8
INA260 is supported by openplotter-i2c app but I need to make some test when I get a unit:
https://forum.openmarine.net/showthread....1#pid19221
Reply
#9
Hello there,

INA260 should work? I tested today, default 0x40 address, near a BME280 at 0x76.
The BME280 is working nice but no signal from INA260, even it's address is detected

Any advice for debug it?
Fair winds
- SV Haimana
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)