Trevor
0
- Joined
- Jul 17, 2009
- Messages
- 4,386
- Points
- 113
So, here's an idea that I've had kicking around for a while.
What I'd like to assemble is an integrated laser diode testing environment for use when a new burner diode comes out and must be murdered, or when we just want to test a laser diode. Take the (not so) recent 8x murder test for example.
As most of you know, an 8x Blu-ray burner diode was sent to IgorT to be tested... almost two years ago. He had an environment set up that would count 60-second on/off cycles and he would take the laser diode out of the environment to do P/I tests every ten hours or so.
I'd like to add a new twist to this. Here's how it would work under my model:
During the on cycle, we keep track of input current, voltage drop, and power output (efficiency will be derived from this data in real time). When the run cycle completes, that data is dumped to another microprocessor. It in turn generates an HTTP post and sends the data up to my web server while the next on cycle completes. The web server records the data into a database as a new 60-second cycle.
Here's the fun part: all data would be publicly accessible during the test. This would include full lifetime graphs of any of the data, degradation information, and complete information of the last cycle. This would allow the community to be constantly up-to-date with the progress of the test and how far the laser diode has degraded.
This system would also allow the automated collection of a P/I curve at precise intervals. If I recall correctly, this was a time consuming process for IgorT. This test would happen in a matter of seconds and the test would continue on its merry way.
----------
I think this would be a really useful tool for the community to have at its fingertips, but it's not a small amount of effort. I'd like to gauge interest in it to find out if the community at large thinks this is a good idea.
The most time consuming portion of the work is going to be in the construction of the interface that allows the complete test data to be browsed. If this doesn't sound worthwhile, I'll just cut the actual delivery out and make this a personal project.
It's also going to be kind of expensive in terms of the other equipment I'd pick up for it. Again, if it doesn't seem worthwhile, I'll simplify it and make it a little easier on my wallet.
----------
Thoughts? Criticism? Trolls?
-Trevor
What I'd like to assemble is an integrated laser diode testing environment for use when a new burner diode comes out and must be murdered, or when we just want to test a laser diode. Take the (not so) recent 8x murder test for example.
As most of you know, an 8x Blu-ray burner diode was sent to IgorT to be tested... almost two years ago. He had an environment set up that would count 60-second on/off cycles and he would take the laser diode out of the environment to do P/I tests every ten hours or so.
I'd like to add a new twist to this. Here's how it would work under my model:
During the on cycle, we keep track of input current, voltage drop, and power output (efficiency will be derived from this data in real time). When the run cycle completes, that data is dumped to another microprocessor. It in turn generates an HTTP post and sends the data up to my web server while the next on cycle completes. The web server records the data into a database as a new 60-second cycle.
Here's the fun part: all data would be publicly accessible during the test. This would include full lifetime graphs of any of the data, degradation information, and complete information of the last cycle. This would allow the community to be constantly up-to-date with the progress of the test and how far the laser diode has degraded.
This system would also allow the automated collection of a P/I curve at precise intervals. If I recall correctly, this was a time consuming process for IgorT. This test would happen in a matter of seconds and the test would continue on its merry way.
----------
I think this would be a really useful tool for the community to have at its fingertips, but it's not a small amount of effort. I'd like to gauge interest in it to find out if the community at large thinks this is a good idea.
The most time consuming portion of the work is going to be in the construction of the interface that allows the complete test data to be browsed. If this doesn't sound worthwhile, I'll just cut the actual delivery out and make this a personal project.
It's also going to be kind of expensive in terms of the other equipment I'd pick up for it. Again, if it doesn't seem worthwhile, I'll simplify it and make it a little easier on my wallet.
----------
Thoughts? Criticism? Trolls?
-Trevor
)
