It's aiming toward being able to use the clicking switch like a normal clicky bistro at the same time as an eswitch yes. Since OTSM is broken, for the moment, to do this either requires the noinit trick or just shorting the OTC with the eswitch, preferable with a little series resistance, to squeeze both on. These combinations are all very untested.
One thing that may lead to an issue is as I have the forward switch, what happens when I use this with mode memory and use the switch tactical to give light sighns quickly
Will this also affect the OTC so modes changes when using the forward switch?
Yes, in all versions of bistro, with or without OTC, short presses change modes. Furthermore, many short presses rapidly enters the configuration menu. I think you should read the bistro documentation a bit. bistro-HD has some new features, but the operation is still bistro. I can't even think how to make a light that does what you want. I suppose a medium length press could be used for all mode changes. Otherwise, you'd have to just lock out all control, and then you only need a one-mode driver. Is that what you're going for?
I guess it's possible to have just one of the switches work that way, especially easy to arrange with the click switch. But I thought you wanted the click switch to not be just a dumb lockout. I'm confused about what you want.
I was hoping to get a light that has a mode switch and a seperate forward clicky, like Nitecore P12 or other lights, just turning light on and off with forward clicky
Mode memory always on
So the forward clicky can be used tactical
and having everything else managed with the eswitch including fast taps for programming
Ok, but you were just complaining that in narsil the click switch is "just a lockout". Doesn't that mean it just turns the light on and off? Or does it reset the mode to some default at the same time?
Anyway,ok, it's easy to add an option to bistro-HD for this. I'll continue in that thread.
Strobe and config runs too slow where? on bistro? Too slow subjectively, or like way way too slow? HD is set a little slower than TA-bistro I think. If it's way way slow though it's probably because your fuses have set your clock frequency too low. If all else fails there's a BLINK_SPEED setting that adjusts it.
I compiled the Narsil triple v1.3.c with this method from this thread
I think it does not accept the preprocessor and other configs files
I learned a lot last 2 days getting into Amtel a bit, so i tried to compile your 3*7135 version
Compiling the whole project gives me an error in Amtel 5 that some tool is missing
Opening the Narsil triple v1.3 solution I need a newer version of Amtel studio than my 5
Watching it today... I've never seen/heard of this problem. Been using 7.0 since it came out on 3 different computers - Win 7 and Win 10, probably for a short time on Win 8.
Does the error occur only when you call up the properties page? You shouldn't have to open it - the defaults already in the .atsln and .cproj files should be good to go. What happens when the error is up? Can you close that properties window or do anything?
Looked around and can't find the local file for your local project settings. Think'n if I could find that file, might be worth trying deleting it.
There's some config files in the \AppData\Local\Atmel\AtmelStudio\7.0 folder (under your user name), but nothing I could find specifically on the NarislTriple project.
Under the roaming folder there is a log file called: ApplicationStatus.log. it's in the "\AppData\Roaming\Atmel\AtmelStudio\7.0" folder. Might be worth looking in there.
In NarsilTriple (same as Narsil), the tail switch should work to change modes w/memory, but only if in mode sets, not ramping.
So in ramping -- yes, the tail switch simply cuts power and acts as a mechanical lockout - same as loosening the tailcap on many lights. I thought of using it to go to max output as a default instead of the 2 blinks and default to OFF - it's a simple change really. Downside is if you have the switch off and simply want to power up the light without getting blasted w/max, you can't do that anymore. I could make it a compile time option, or configuration setting as well, but others want to go further with this simple change, and also change how the e-switch basically works - that's where it gets complicated.
Glad that worked out. I'll be adding that into the mainline code for both Narsil versions. Right now I got another driver project to work on - might be tied up with it for a week or two.