- This topic has 3 replies, 2 voices, and was last updated 8 years, 2 months ago by .
Viewing 3 posts - 1 through 3 (of 3 total)
Viewing 3 posts - 1 through 3 (of 3 total)
- You must be logged in to reply to this topic.
Home › forums › Getting Started and Troubleshooting › PiShield and HifiBerry Compatibility
Hi JP,
First of all, apologies for the delayed response – looks like notifications are not being sent, so I’ll be working on that…
I think it should be fine to use your Hifiberry along with the PiShield.
We’ve uploaded the pinout configuration to pinout.xyz where you can see the exact pins used.
Note that the GPIO2-3 are technically “not used” since they’re simply exposing the I2C bus, and as long as your other devices do not use the same I2C addresses as the sensors you’re using, it should be fine!
Johnty
Hi Johnty,
Thank you very much for your answer. Yes it should be fine and I just ordered the PiShield. So I will see on site soon!
AS I will be using other stuff on the I2C bus, could you tell me which are the adresses of sensors connected to the Digital I2C ports of the PiShield? Is there any mean to change this adresses in case of.. ?
Thank you very much again
Best regards
jp
Hi JP,
By default there are no extra digital sensors built into the PiShield, so you shouldn’t have any address conflicts when adding another device. As you add your own sensors, you should just check to make sure it doesn’t conflict with the HiFiBerry’s address. Some sensors allow you to change their address, while others don’t – so it depends on what you’re using.
A handy command-line tool you can use is
i2cdetect -y 1
Which will spit out the i2c devices currently attached. You can do this with one new sensor at a time to verify that it’s working on the i2c bus and also see what its address is!
Johnty