-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RFC] Other front end boards #2
Comments
Rf power meter + frequency counter is another idea. |
true, it could be a laser driver, humidity sensor, single channel Sampler, optical power meter, etc. I would expose all pins we have |
is this too much mission creep? there are a million little commodity IoT widgets out there. I don't think it hurts to expose all available pins, but maybe better to focus on making this a good photodiode monitor first? |
I'd argue that the photodiode aspect of this project is trivial. The 'IoT widget' aspect seems to be the tricky part and thus I think we should consider leveraging effort put in there.
I think this issue is more about keeping this in mind and not doing anything to preclude it unless there is good reason, rather than creeping the mission. |
Agreed. But making a good photodiode monitor is less about the photodiode circuit and more about the digital side of things, in this instance.
Fair. Just wanted to raise the point. It's already starting to look like the all-singing, all-dancing IoT widget with 4 different communication protocols and 3 connectors and power harvesting and.... |
Right now it looks like DiPho will be a two board device, with one board having the photodiode + amp, and one board having the DAC, uC, power, and communications. It has already been mentioned that different versions of the photodiode board could be produced in the future (eg. with log amp). One could imagine a much broader range of applications though (eg. analog front end for voltage monitoring/logging, environmental monitors). I mention it now as, if this is thought to be a good idea, it may influence exactly how things are divided between the two boards and what kind of header should go between them.
The text was updated successfully, but these errors were encountered: