• Please visit and share your knowledge at our sister communities:
  • If you have not, please join our official Homebrewing Facebook Group!

    Homebrewing Facebook Group

BCS-482 and 7 Segment Display

Homebrew Talk

Help Support Homebrew Talk:

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.

braundgw

New Member
Joined
Nov 16, 2009
Messages
2
Reaction score
0
Location
Perth West Australia
Hi All,

So... over the Chrismas / New Year break I finally put together one of the ebrewsupply BCS kits and it is now complete and I'm super happy with how it's turned out.

I only have one problem for the knowledgable people here and it's to do with connecting the 7 segment displays to the BCS 482.

I have the i2c cable connected from the BCS to the 7 Segment display and it powers up and shows version number and then address, but then just shows "no data" (Most of the time). Funny thing is when I turn it off... before the screen dies it briefly shows the correct temperature. I have no other connection to the display.

I'd ask on the BCS forums but my membership isn't being approved for some reason... and have had nothing back from admin.

Thanks in advance for any assistance with this problem.
Regards,
Greg
 
Bit of an update for this problem.

I removed the BCS from the brew control cabinet and did some bench testing.

With just one temp sensor, one 7 segement i2c display and 12v power supply connected I found that the display would power up, show "no data" for a while and then display the correct temperature for ~16 seconds. It would then show "no data" for a few seconds before again showing the correct data for 16 seconds. This behaviour then repeats continuously. 16 seconds of data followed by a brief "no data". I've tried a number of different screens and each behaves the same way.

Has anybody had success using the BCS 482 with the I2C displays from brewershardware?

I shall continue my investigations, but for the moment I'm suspicious of the BCS I2C interface.

I think I may try sniffing the I2C bus next and try and work out what's going on.
Unfortunately I'll be starting from scratch with this, so the solution could involve lots of googling and reading.
Not all bad though... I do have a beer at hand.
 
Back
Top