Open ghost opened 8 years ago
Does not need to be a "script" - I was envisioning this as a component / function within the data acquisition executable. Could be done either way, but I think it would be easier as a single executable to maintain the data structures.
I have an Exel file (also on T: drive) which lists MOST of the I2C addresses that the auto-detect would be required to identify. I think the best way to identify the sensors is not by name, but by I2C address.
I will look into it. I can see a slight issue when it comes to auto instantiating, which lies in the fact that I enable the third I2c before anything else in the boot script. I am not entirely sure if enabling the I2c communication will inhibit our ability to use those pins for other IO functions. If it doesn't inhibit anything, then there should be no issues coding an sensor auto-detector (that I foresee).
As discussed in the meeting during Feb 8th, 2016,
The Enable 3rd I2c script will need to be run prior to any sensor auto detect code.
As discussed, we want a script that can automatically detect, identify and connect to any attached sensors.
This requires the names (OR a data sheet link!) of every device we plan on connecting to the BBB 4G.