the datasheet of the tantal cap says the anode is marked with a polarity bar
Nothing special at all - put the files anywhere you like. I generally keep mine in one common folder since our drivers are so simple - might as well keep it simple 
. Only thing to understand is solution vs. project. A solution can contain one or more projects. Studio will want to create sub folders for each project, but I force them to be in only one common folder. For our use, I've only used one project per solution and name them the same. Our firmware is pretty simple compared to Visual Studio solutions I work on at work.
Even if you created a solution and project with the project in the sub-folder -- no problem, move all the project files in the sub-folder to the parent folder where the .atsln file is (solution file), delete the old project from the solution, add it again from it's new location and it all works fine.
Another important thing is to be sure you change the Solution Configuration from "Debug" to "Release". Debug turns off optimizations totally. All we want to use is "Release" since it's fully optimized. Once you change it to "Release", it's remembered and will default that way next time.
What I like is from right inside Studio, you can rename or delete files, projects, or even the solution. I like keeping all header files in the project since global searches/replaces will work thru the headers as well.
Basic Digikey cart with parts minus resistors since we will likely have them around. I am not sure that I have exactly the correct ATtiny25 in the cart…
Right, I found the same datasheet, but the board doesn’t say which way to put it. I’m pretty sure I’ve got it right in the photo.
Matt - did my post above help clarify anything for you?
After giving up on trying to fit a 17mm TAv1 into a Convoy S2 (the “shelf” on the pill is wider, so R4 usually gets crushed), I built a BLFA6_EMU hexfile with custom modegroups and flashed it onto a MTN-17DDm with ATTiny25. It flashes OK, but when I power it on, it just randomly cycles through all of the modes.
I’ve checked through fr-tk-attiny.h and the pins look correct. I’m not sure where to look next.
Hi Flintrock,
I wanted to take a look at your firmware and see if I can use it for some of my recent builds, but it seems like your links in the OP aren’t working, at least for me!?
EDIT: Well, http://www.tinyupload.com appears to be down right now.
EDIT 2: Downloads are working again now.
I tried to contact flintrock over PM
I got a question if 2S OTSM works with zener diode or if the LDO is nessesary
Tom is correct. It doesn’t matter what OS you use to compile; it matters what settings are used and which version of gcc.
If a project was developed with one toolchain and compiled with another, that’s where things get messy. For example, if it was developed with a Makefile or shell scripts for building, and then someone else tries to build it in AVR Studio, then the intended settings are lost and must be re-entered manually in the other tools. But the OS itself doesn’t really matter.
Anyway, a while back I was going to put Bistro-HD into the main code repository but Flintrock asked me to wait until a few things were fixed. Any idea if it’s ready to be added yet?
I don’t have any relevant hardware to test it on, so I’m hoping someone else has verified it.
I am trying to get the OTSM drivers to work,
first
does only get low mode, nothing else
the 2.
gets only low-medium-high
tapping often does not enter config mode
long clicks are not working at all
the 3. only in low mode
4. LDO no response at all
I see Flintrock hasn't been on for 3 weeks. Dang, I really want to read up more on this version - sounds like a bunch of nice features. I've been flip flopping around on clicky switch driver - Bistro, my own, Biscotti, etc., so was hoping to standardize on this one.
Flintrock - congrats on this!! Awesome job!
Yeah, his last post Here seems to indicate he’s got stuff going on (Don’t know if good or bad stuff). It would be great if he’d finish this. It really is (or can be) a nice upgrade.
I hope i am not sitting on parts for 25 OTSM drivers just to figure out they dont work at all
I could maybe help here. Dunno enough yet about building them. Do standard TA boards work? Dunno bout that C2 cap - if it fits on standard C2 pads. Dunno bout the diode either - if that's just a standard diode or not.
the cap is 0805 but fits on the 0603 pad
the diode is a shottky also used on other drivers
the R1 and R2 are different
I needed to add a Diode to the 2S LDO 17mm now it is working
trying to figure out whats wrong with 1S
So you tried three identical 1S boards with the issues as listed above? Weird bout the LDO - never used a diode with one. The LDO replaces the diode on all our other e-switch drivers. Sure you got the correct LDO part? I got burned before by having the wrong type of LDO.
Those R1 and R2 values sure are strange... But I see now - should work fine.
Are you using an "approved" MCU revision?
I figured it out
I made a stupid mistake populating C1 as usual with 10uF, but OTSM needs 1uF there
I had a bunch of 0805 1uF left, where I should have used almost all of them
Ahh! Yea, noticed that in the manual (and post #94). Didn't notice it at first glancing at the parts list.
I loaded Bistro HD OTSM in Amtel Studio
Now I tried to compile a hex with a custom modegroup
But when I flash it its totally messed up, the driver has only 3 modes, does not accept long clicks
when entering config it bliks 6 times then buzz and thats it
P.S. I did a new project in Amtel studio and now it seems to work
also I am puzzled how to change the LVP to another value
the fr-calibration.h has still the stuff from Bistro using 19.1/4.7k resistors to define voltage
also still searching where to adjust moonmode to get it a bit brighter, now its more a firefly mode