Do you know when we will see “B”, “C”,… lights?
I’d love to know more about how programmable the Asgard is. For example, does its programming language have any form of logical control structures and loops? Can it stay on while the power button is being pressed, for things like press-and-hold to ramp the output? Does the language have a concept of variables and mathematical operations? How much space is available for storing programs / modes? Can the user define multiple mode groups and switch between them with well-timed button presses? Is there any type of random number generator, for things like a randomly-varying strobe mode? Etc…
Never mind…
Sorry to jump on this sub-thread, but I can’t find fasttech’s post above…
FastTech,
What you said about “theoretically work with Android 2.1+” is good, but then, can you ensure that your developers don’t do something, or configure something, in the app that would explicitly PREVENT it from running on, say, Gingerbread? I’ve seen (and been frustrated by) too many Android apps that just won’t install on a specific version (i.e., Gingerbread) because the app developers configured the app to exclude certain versions of Android when they implemented their app.
I don’t know about others, but if I was going to buy an Asgard (and I am now seriously considering it), a lot of its value (and possible usage scenarios) would be lost to me if I couldn’t use the Android app.
Thanks,
Jim
Pretty sure it's the same as my T60; a boot change would be quick and easy . . .
jackbootedthugFoy
I like the concept of easy programmability.
The naming of the specific model and the other suggested labels remind me of this brand which I am quite the fan of.
And have already spent thousands on.
anybody know?
I read that the default on this light is something like, low, med, high. So, does this have 3 settings available? You could program ‘many’ different light settings but only use 1 of three at any give time. Then use the app to transfer other settings to the light if u want? Is that how this will work? Sounds like fun, for a while……
thoughts?
patrick -
flexcandles.com site says: "Program your flashlight the way you want it. Make it single-mode, 3 modes, or even 30 modes."
now that sounds even ’funner!’
I’m hoping to be able to program moonlight low medium high with memory, its just about my favourite set up, this would make this light an awesome bed side light - moonlight or very low for baby duties, high with decent throw for when things go bump in the night.
I also agree with a statement above, it would be nice to know if the 7135’s are addressable, then you could stack the one for high to gain a higher high and retain a very low low, unless I’m totally not understanding the driver set up.
Since the moonlight mode doesn’t have PWM and each 12.5% in output doesn’t have PWM, I don’t think the moonlight uses any of the AMC7135 chips but uses something else instead. Seems to me you could double stack each 7135 if you wanted to get 6A output without effecting the moonlight mode. Of course I’m just spit-balling here but it sounds logical on the surface to an electronic ignoramus like myself. 
that’s kind of what I was wondering, it would be nice to keep moonlight - 12.5% of 3a - 50% of 3a - 4.5a+ for high and use an xm-l2 nw on copper that way you get moonlight low no pwm medium no pwm - high no pwm 8)
Lol,
They build the light out of our dreams and we still want to mod it…
From my understanding the 7135 are stackable, too.
Would anyone expect any less of us?
No
Modding is not a means to an end for me, it is the end :) This one I might actually keep stock though.
I’m merely looking to build on the awesome platform presented 0:)
We have here, a light that seems infinitely configurable, we have been told we can set brightness levels at 12.5% intervals that have no pwm (8 chips, 8 levels that can be independently turned on, well you start at 1 and stack those intervals) that being the case, we have the options of a number of sensible levels and one stupidly high turbo level to unleash the throw potential of this host, check out tom e’s results in relics zy-t08 review thread to get where I’m going with this.
Given the opportunity, and potential, would you really not even ask the question?
I’m still debating…. on the one hand,
- It’s programmable
- It’d be my best thrower (since I gave the TK75 away), yet still be usable indoors thanks to low/extra-low modes. I think it’d get like 65k to 70k lux stock, and go down to around 3 lumens on the 8mA mode.
- It’s programmable
- I had been kinda thinking about a ZY-T08 or HD2010 or Jacob A60 or ZY-C10-S anyway, just for fun.
- It’s programmable
But on the other hand…
- It’s too big for most of my purposes
- I almost never have a use for a long thrower
- The control app might not be compatible with any of my devices
If they can fit this programmable driver into a Convoy S3 or similar, it’d be a no-brainer.
Maybe I just need to get the hardware to flash an ATTINY and take apart some tube lights. Or, the HexBright looks nice too, and its video shows the ability to handle press-and-hold events so it’s an electronic switch. Looks like its programming language is sufficiently powerful too, so I could give it algorithmic features and a wide variety of UI styles.
Or, as they say on CPF, maybe I should just get both. Or do all three.
if one can program 30 modes, or more, how does one access all the modes? Half press? How would u remember them all? Could someone please address this, thanks…
toy keeper, as I said in another thread, I’d really like to hear both yours and chloe’s opinions on one of these actually in hand.
The zy-t08 really isn’t so big, considering, I love mine for a jacket/cargo pocket thrower, I just see this as adding so much more usability to a stock zy-t08.