rhd
0
- Joined
- Dec 7, 2010
- Messages
- 8,469
- Points
- 0
I decided to torture the dual-boost SAIK build to see how it behaved under a long run time. Despite the skepticism from Johnnyz, these drivers appear to like being paralleled.
EDIT
Okay, here are the results. Here's what you're looking at:
- Dual boost driver SAIK build, with each set for 864mA.
- In practice, with the paralleled setup, there was 1.66 A to the diode.
- Powered by a single 26650.
- Aixiz 3-element lens (NOT a G1 as I had used in post #2)
What You're Seeing:
- On the right hand side, the first "kink" or "decline" is where the drivers went into rapid "pulse" mode.
- The second "kink" or "decline" is simply me shutting it off.
- It ran for about 7 minutes before the drivers decided enough was enough.
- I have observed two driver behaviors when it is "tired". It will either pulse rapidly, or simply dim the LD (ie, lower it's current). I do not yet know which behavior is caused by heat (thermal protection) vs insufficient battery current supply to continue boosting to the set current. I presume that each behavior is attributable to one of these two issues.
All in all, this is pretty impressive performance.
EDIT
Okay, here are the results. Here's what you're looking at:
- Dual boost driver SAIK build, with each set for 864mA.
- In practice, with the paralleled setup, there was 1.66 A to the diode.
- Powered by a single 26650.
- Aixiz 3-element lens (NOT a G1 as I had used in post #2)
What You're Seeing:
- On the right hand side, the first "kink" or "decline" is where the drivers went into rapid "pulse" mode.
- The second "kink" or "decline" is simply me shutting it off.
- It ran for about 7 minutes before the drivers decided enough was enough.
- I have observed two driver behaviors when it is "tired". It will either pulse rapidly, or simply dim the LD (ie, lower it's current). I do not yet know which behavior is caused by heat (thermal protection) vs insufficient battery current supply to continue boosting to the set current. I presume that each behavior is attributable to one of these two issues.
All in all, this is pretty impressive performance.
Attachments
Last edited: