I’ve found soft start to be “choppy” in about 1/4th of my builds. Don’t know what makes the difference.
So, foot-mouth, I may have detected minor debouncing issues occasionally on e-switch (I think it's debouncing, some other click sequence logic was also changed so I'll review it). This wasn't happening just before release but I did change the debouncing time at the last minute with only quick testing. I thought it would save a couple of bytes. Actually it wasn't necessary for saving bytes anyway, but then I left it because I thought it was enough anyway. Probably just a matter of bumping the stabilization time back up around 50ms, as previously advised and tested. Things are working pretty well, certainly well enough for people who want to try it, but I do occasionally get a short click interpreted as medium on e-switch.
Posted version 1.7.1 see OP for link.
1.7.1
Polishes some claims in 1.7, particularly click timing stability.
Now solid e-switch click interpretation even when clicking furiously.
E-switch timing sped up slightly, long click off now only 1.0s. medium click threshold reduced to 0.375. That could be too low on forward-clicky OTSM lights but is nicer on a lightweight e-switch like the q8.
Adds "fetonly" single channel (PB4 pin) OTSM builds with TA's triple modegroups mapped onto one channel. These were planned for awhile but particularly inspired by Schoki's boost driver plans, which should maybe work with the OTSM-LDO-fetonly build.
I have not tested this one on my OTSM light yet. No changes made to the OTSM code though since 1.4.1 really. Once I get that tested, hopefully this version can get upgraded to "stable".
Version 1.7.1 now tested on OTSM as well. No problems showing up and in principle, even on OTSM it should have a little more stable click timing than 1.4.1, and of course it works on e-switch. As always feedback will ultimately tell, but 1.7.1 is now the version I would recommend to try.
Updated to 1.7.1 in the repo.
I got here a request for Bistro using just 2 channels for´1+1 AMCs
I got first tried to just replace the channel use for the 20 brightness levels
It works in modes, but when going to special modes the Turbo does not light up as it seems to be programmed somewhere else not using the 20 levels
Then I tried to bridge FET output to the AMC channel, the chip does not like it breaking normal operation
Then I tried to change to 2 channel output in the TA config file and get the modegroups again changed, but it still does not use the pin 6 for FET output
First, merry Christmas. Turbo uses the 20 levels even in hidden modes, but obviously you've got something not quite right. It sounds like something I could look at pretty easily, and actually there may already be something pretty close in the latest 1.7.1 release which does include a FET+1 build or two, maybe not on the channels you need. I'm a bit pre-occuppied with the holidays for a while though. That might mean I get time to think about it soon, or might mean it takes a couple of weeks, not sure.
how would i go about using bistrohd otsm on a ta fet+1+ board without the fet?
I mean no FET on the board. Just 7135’s.
A pretty simple way would be to start with the “modegroups-TA-triple-v1.3plus.h” modegroup definition and edit the ramp matching your FET to all 0.
this wont work if you do not copy the ramping tables for 1 and all AMC from 2 Channels to 3 Channels as well as edit all FET to 0
Has someone a project that produces working hex files?
I downloaded several versions but making an Atmel Studio 7 project and compile a hex does not work on the driver
Yes, today I ran a build for TAv1 OTSM, flashed it, and built a light. Works great! I really like the new thermal system.
Its the HD OTSM build did you had your own atmel studio or use the existing hex files?
if so I need the atmel studio project
I ran my own build, since I customized the modegroups and default settings. Here are the steps I followed:
1. Install Atmel Studio with default directory. When prompted, select only the 8-bit option.
2. Extract bistro-hd archive to temporary directory, then move main folder to c:\firmware\HD
3. In Atmel Studio, start a new project with default settings (C/C, GCC C Executable Project). When prompted, select ATTiny25.
4. In the Solution Explorer window on the right side, right-click main.c and click remove. Then right-click GccApplication2 (or whatever your project is named, it’s the line with the yellow page icon) in Solution Explorer and click Add->Existing Item. Select C:\firmware\HD\bistro-HD.c and click add.
5. At the top of the window, click Build -> Configuration Manager. Then change “debug” to “release” on that screen, you might need to change it in two places. Click Close.
6. In Solution Explorer, right-click GccApplication2 and click Properties. In Build->Configuration, make sure Active (Release) is selected. Check the box for Use External Makefile, then Browse to C:\firmware\HD\Makefile and click Open. Then click the Save icon (or press Ctrl+S).
7. At the top of the window, click Build -> Build Solution. Check the Output window at the bottom of the screen, especially for the avr-size output. ATTiny25/45/85 has 2/4/8K of memory, so make sure your build fits. The resulting files should appear in C:\firmware\HD\hex and should work when flashed.
Here are the options I use for avrdude (I always erase manually even though it does it before flashing):
avrdude -p t25 -c usbasp -e -u
avrdude -p t25 -c usbasp -u -Uflash:w:FILENAMEGOESHERE.hex:a -Ulfuse:w:0xd2:m -Uhfuse:w:0xde:m -Uefuse:w:0xff:m
Total facepalm moment, I just now noticed the “Atmel Studio 7.0 Command Line” shortcut. New, better build instructions, no solution file needed:
1. Install Atmel Studio with default directory. When prompted, select only the 8-bit option.
2. Extract bistro-hd archive to temporary directory, then move main folder to c:\firmware\HD
3. Open “Atmel Studio 7.0 Command Line”. Type in the following:
cd \firmware\HD
make all
1. Install Atmel Studio with default directory. When prompted, select only the 8-bit option.
what means 8 bit?
Apologies, I should have specified that I used the web installer instead of downloading the full installer. When you run the web installer, you get a pop-up that asks which devices you want to install support for. There are three check boxes, and 8-bit is one of them. If you aren’t getting that prompt, it shouldn’t be a problem for compiling, it just means it will install more than what you need to get the job done.
I just wanted to say thanks for such useful and well documented firmware!
I got further testing with 2S builds
The Battcheck and LVP does not work properly
at 8.4V I get 3 and 7 blinks for 3.7V
at 7V I get 3 and 9 blinks for 3.9V
at 6V again 4 and 2 for 4.2V
2. driver
8.4V—>3.1V
7V—>2.6V
6V—> 2.5V