E-switch UI Development / FSM

Lexel · 2019-04-18T22:51:02.000Z

ToyKeeper:

Lexel:

I downloaded the Anduril.c and all 2019 changeed configsyesterday between 10:00 and 10:30

It sounds like you should probably use bzr instead of downloading files one at a time. It really helps with a lot of things.

what is bzr?

its also annoying that a lot of changes have to be done to make it run on Atmel studio

Main.c
//#define FSM_BLF_GT_DRIVER
//#define FSM_BLF_MF01_BUCK_DRIVER
#define FSM_BLF_MF01_DD_DRIVER
//#define FSM_BLF_L6
//#define FSM_BLF_GT_MINI_DRIVER
//#define FSM_BLF_Q8_DRIVER
//#define FSM_EMISAR_D1_DRIVER
//#define FSM_EMISAR_D18_DRIVER
//#define FSM_EMISAR_D1S_DRIVER
//#define FSM_EMISAR_D4_DRIVER
//#define FSM_EMISAR_D4_219C_DRIVER
//#define FSM_EMISAR_D4S_DRIVER
//#define FSM_EMISAR_D4S_219C_DRIVER
//#define FSM_FF_ROT66_DRIVER
//#define FSM_FF_ROT66_219_DRIVER
//#define FSM_FW3A_DRIVER
//#define FSM_SOFIRN_SP36_DRIVER

/* specific settings for known driver types */
#include “tk.h”

#if defined(FSM_BLF_GT_DRIVER)
#include “cfg-blf-gt.h”

#elif defined(FSM_BLF_MF01_BUCK_DRIVER)
#include “cfg-blf-MF01-Buck.h”

#elif defined(FSM_BLF_MF01_DD_DRIVER)
#include “cfg-blf-MF01-Buck.h”

#elif defined(FSM_BLF_L6)
#include “cfg-blf-L6.h”

#elif defined(FSM_BLF_GT_MINI_DRIVER)
#include “cfg-blf-gt-mini.h”

#elif defined(FSM_BLF_Q8_DRIVER)
#include “cfg-blf-q8.h”

#elif defined(FSM_EMISAR_D1_DRIVER)
#include “cfg-emisar-d1.h”

#elif defined(FSM_EMISAR_D18_DRIVER)
#include “cfg-emisar-d18.h”

#elif defined(FSM_EMISAR_D1S_DRIVER)
#include “cfg-emisar-d1s.h”

#elif defined(FSM_EMISAR_D4_219C_DRIVER)
#include “cfg-emisar-d4-219c.h”

#elif defined(FSM_EMISAR_D4_DRIVER)
#include “cfg-emisar-d4.h”

#elif defined(FSM_EMISAR_D4S_219C_DRIVER)
#include “cfg-emisar-d4s-219c.h”

#elif defined(FSM_EMISAR_D4S_DRIVER)
#include “cfg-emisar-d4s.h”

#elif defined(FSM_FF_PL47_DRIVER)
#include “cfg-ff-pl47.h”

#elif defined(FSM_FF_ROT66_DRIVER)
#include “cfg-ff-rot66.h”

#elif defined(FSM_FF_ROT66_219_DRIVER)
#include “cfg-ff-rot66-219.h”

#elif defined(FSM_FW3A_DRIVER)
#include “cfg-fw3a.h”

#elif defined(FSM_SOFIRN_SP36_DRIVER)
#include “cfg-sofirn-sp36.h”

#endif

ToyKeeper · 2019-04-19T19:28:52.000Z

Lexel:

what is bzr?

It’s kind of an important thing to know about if you’re working professionally with code in a bzr repository.

Lexel:

its also annoying that a lot of changes have to be done to make it run on Atmel studio

{code}

Those changes don’t actually need to be done to make it compile in Atmel Studio. I removed all that stuff because it’s not necessary. It only needs a single include, or a “-DCONFIGFILE=cfg-something.h” passed to the compiler on the command line, to pull in the bits which are specific to individual build targets.

Lexel · 2019-04-19T19:46:55.000Z

ToyKeeper:

Lexel:

what is bzr?

It’s kind of an important thing to know about if you’re working professionally with code in a bzr repository.

Lexel:

its also annoying that a lot of changes have to be done to make it run on Atmel studio

{code}

Those changes don’t actually need to be done to make it compile in Atmel Studio. I removed all that stuff because it’s not necessary. It only needs a single include, or a “-DCONFIGFILE=cfg-something.h” passed to the compiler on the command line, to pull in the bits which are specific to individual build targets.

you really want that non professional users use some sort of command line and remove the code that works with build solution button?

I know you are used to user some fancy software which uses a sort of libary and can handle different versions and all sort of stuff, but

normal BLF users
download Atmel Studio

download Anduril Project someone else made
or
have to download each file individually on ~toykeeper/flashlight-firmware/trunk : files for revision 250
put all the nessesary files together from various different folders

uncomment the config file name
may do some modifications in cfg file
hit F7 to build the hex
now 3 options

- AVR integrated flash tool

- use USBasp integrated in tools

windows cmd window with the right USBasp fuse settings

beastlykings · 2019-04-19T21:22:28.000Z

I’m a normal BLF user, I think anyway.
I know nothing about coding. But I learned how to use basic BZR functions, because it’s much easier to download the whole directory to work with that way. Launchpad even puts the bzr command with the URL loaded into it at the top of the page, super useful.

Never could make atmel studio work properly, but I like the way TK has it set up without it

Besides, she’s the one doing all the commits? Shrug

ToyKeeper · 2019-04-19T23:26:14.000Z

Lexel:

ToyKeeper:

Lexel:

what is bzr?

It’s kind of an important thing to know about if you’re working professionally with code in a bzr repository.

you really want that non professional users use some sort of … fancy software … ?

I don’t expect everyone to use a revision control tool, but not everyone is working with companies to mass-produce commercial items with my code. That type of work is going to involve some kind of source code revision control tool like Bzr or Git. Also a pretty healthy understanding of the GPL.

Imagine if I had spent the past few months modifying your PCBs, getting lights produced with them, and complaining about it… and then I mentioned that I’m editing the layouts with Notepad. So you tell me I really should be using Diptrace. And then without looking it up or reading the guide linked in your signature, I ask, “what is diptrace?” For an encore, I follow up with a comment about how it’s too fancy and normal people shouldn’t have to use fancy tools designed for the job I’m doing.

TrueRMS · 2019-04-22T05:21:37.000Z

Hello, I need some help getting my FT03 working again! I tried to flash it to Anduril tonight, I thought the pin out might be the same as a GT_Mini driver because a comment from Tom but that wasnt the case.

I can get by modifying code but the setup part has always been over my head, I thought I had the registers figured out but it doesnt work at all now (it did light up with the GT_Mini build but never shut the LED off all the way cause of the conflict with the AUX LED pin and only one channel worked).

The FT03 driver pinout is as follows:
1x7135 is on pin 3 (PB4)
FET on pin 5 (PB0)
SW on pin 2 (PB3)
AUX LED on pin 7 (PB2)

I tried editing the Emisar D4 HWCFG file with these lines:

#define AUXLED_PIN PB2 // pin 7(FT03)

#define SWITCH_PIN PB3 // pin 2
#define SWITCH_PCINT PCINT3 // pin 2 pin change interrupt

#define PWM1_PIN PB4 // pin 3, 1x7135 PWM (FT03)
#define PWM1_LVL OCR1B // OCR1B is the output compare register for PB4(FT03)
#define PWM2_PIN PB0 // pin 5, FET PWM (FT03)
#define PWM2_LVL OCR0A // OCR0A is the output compare register for PB0(FT03)

But that didnt do it, infact that broke it more than the stock GT_Mini file!

Could someone maybe make a HW config and HW Define file for the FT03 or atleast walk me through the process to get my (now dead) FT03 running?

Tom_E · 2019-04-22T11:24:44.000Z

Ahhh, I could not determine the pinouts so I wouldn't have stated it. Best thing to do is take the source code of NarsilM for this light from the link TA provided, and determine the pinouts from there - that should be the best most reliable way.

Ohh, here is TA's post with the link: https://budgetlightforum.com/t/-/54922/2219

After reading the post again, TA sure isn't certain it's what they used but I'm thinking it is.

Update: Ok, I looked it up myself. It looks like the FT03 uses the same pinout config as the S43 and S42, documented in NarsilM (RegisterSettings.h) as this:

/*
 *                  ---
 *    Reset PB5 1 -|   |- 8  VCC
 *   switch PB3 2 -|   |- 7  PB2 Ind.LED
 * 7135 PWM PB4 3 -|   |- 6  PB1 Not Used
 *      GND     4 -|   |- 5  PB0 FET PWM
 *                  ---
 */

So what's unique is using pin#3 for the 7135, then the Ind. LED goes to pin #7, with pin #5 for the FET.

The normal FET+1 pinouts are this:

/*
 *              ---
 *   Reset  1 -|   |- 8  VCC
 *  switch  2 -|   |- 7  Voltage ADC or spare
 * Ind.LED  3 -|   |- 6  FET PWM
 *     GND  4 -|   |- 5  7135 PWM
 *              ---
 */

Now I didn't confirm this by tracing out the driver. How exactly are you programming the 85 on the FT03? Are you using some sort of pogo pin setup?

TrueRMS · 2019-04-22T15:27:42.000Z

Just soldered short wires to the pads on the bottom of the driver.

So if I’m correct on the pinout what have I done wrong? If I’m reading the datasheet right I should be correct on the output compare registers too so why is there no light?

Tom_E · 2019-04-22T15:49:30.000Z

TrueRMS:

Just soldered short wires to the pads on the bottom of the driver. So if I’m correct on the pinout what have I done wrong? If I’m reading the datasheet right I should be correct on the output compare registers too so why is there no light?

Ohhh, stupid me - just read your prev post in detail, so looks like you got the pinouts correct. Not sure if TK is supporting this combo though - there's some things that have to be done.... Not sure if she has all that flexibility built in. She would be best to answer - would take me time to research and/or test in Anduril.

Oh, direct soldering -- Ok, that's cool!

If you simply want to recover your FT03, then reload the stock firmware from TA's link. If this doesn't work, then Mateminco did make a hardware/firmware change we aren't aware of.

ToyKeeper · 2019-04-22T17:45:07.000Z

TrueRMS:

Hello, I need some help getting my FT03 working

Tom E:

/*
 *                  ---
 *    Reset PB5 1 -|   |- 8  VCC
 *   switch PB3 2 -|   |- 7  PB2 Ind.LED
 * 7135 PWM PB4 3 -|   |- 6  PB1 Not Used
 *      GND     4 -|   |- 5  PB0 FET PWM
 *                  ---
 */

I don’t have any drivers like that so I can’t say for sure it’ll work, but I think the easiest method would be to tell it the light has three channels, and then put the PWM data out of order. More specifically:

Copy the FF ROT66 cfg file.
Copy the PWM data from a 2-channel driver like the Emisar D4.
Rename PWM1_LEVELS to PWM3_LEVELS.
Rename PWM2_LEVELS to PWM1_LEVELS.
Define PWM2_LEVELS and set it to all zeroes.

Basically, PWM1 has the FET data, PWM2 is zero, and PWM3 has the 7135 chip data.

I’ll probably add proper support for this kind of layout eventually, but probably not until I have one to test on.

Lexel · 2019-04-24T12:34:02.000Z

I had some discussion with Matemineco today

they seem to miss the blink at ramp floor

I did measurements with Oscilloscope and photodiode and could not spot the slightest hint of a blink

ideal would be a brighter blink like when doing battcheck so it is clearly noticeable

Agro · 2019-04-24T12:40:41.000Z

Maybe at the level the light was at the start of ramp-down? Or minimum(start level, some low but clearly visible level)?

Tom_E · 2019-04-24T13:01:14.000Z

I'm checking on the current NarsilM V1.3 right now, and it's very hard for me to notice the blink at the bottom of the ramp. I can do it 20 times and can't be sure it blinks or not. If I do the blink, it's maybe at a low output level and quick. I don't think Mateminco has anything to do with it? I thought they used the version of NarsilM v1.3 provided by TA directly, so basically it's what I did in NarsilM?

Lexel · 2019-04-24T13:08:26.000Z

Tom E:

I’m checking on the current NarsilM V1.3 right now, and it’s very hard for me to notice the blink at the bottom of the ramp. I can do it 20 times and can’t be sure it blinks or not. If I do the blink, it’s maybe at a low output level and quick. I don’t think Mateminco has anything to do with it? I thought they used the version of NarsilM v1.3 provided by TA directly, so basically it’s what I did in NarsilM?

Talking of FSM based Firmware in this case Anduril for new light

Tom_E · 2019-04-24T13:17:31.000Z

Ohhh - getting my wires crossed

Lexel · 2019-04-25T11:00:31.000Z

Still having problems getting the thermal regulation stable without the hard turbo dropdown
sometimes it works and sometimes it freaks out heating up to unsafe levels

the stange thing is when I shortened the ramping table to 144 values the thermal regulation worked fine, but other things like 2x Turbo did not work properly

I would like to know if and how this values interact with the thermal regulation

//#undef USE_SET_LEVEL_GRADUALLY
#define HALFSPEED_LEVEL 14
#define QUARTERSPEED_LEVEL 5

basically the MF01S is ready to get produced but still the firmware does not work out
TA tested the thermal regulation to fail heated up to 100°C
Matemineco tested it stopped at 90°C
and I tested it

the thermal regulation freaks out and the light heats up till we stopped at like 100°C the MCU read 95°C when getting into temp check after such a freak out so there is no hardware problem

alternatively how can I prolong the time period when the hard turbo dropdown kicks in and how it its level defined it drops to like 1 minute or 90 seconds?

hodor · 2019-04-25T11:12:26.000Z

Honestly, I’ve experienced strange behaviour with temp regulation on my D4Ses. At first I thought it was due to calibration but am pretty sure that’s not the case. I haven’t been able to replicate the behaviour 100% of the time so haven’t mentioned anything since. Hard turbo dropdown on the D4 works fine though, probably a bit too aggressive for me but I may just undefine it and reflash at some point.

Lexel · 2019-04-25T14:50:12.000Z

So I did a sort of proove as TK dont want to listen to Matemineco or Texas Ace

I could prove here that the temperature regulation starts to inchrease the current again above the thermal ceiling,
so it can oscillate the temperature up like seen on different tests on MF01 and MF01S

Video is calibrated driver with room temp and ceiling to 60°C

at one point it stays at between 80°C and 70°C and the current is at about 70% of Turbo
here is definately a command like stay at MIN_THERM_STEPDOWN 100 when temp >ceiling+5°C, missing that sets the max current when the ceiling is already overshot

it is a kind of problem above ceiling that will always happen if the light does not come to a thermal balanced system, it heats up like 5°C and then cools down only 2°C when the MCU regiusters oh wait ite getting hotter now

DB_Custom · 2019-04-25T14:46:44.000Z

Man, Coming in here is like barging into a room full of geeks that ran out of coffee!

Some people need to take a chill pill and get over themselves… Lexel, talking to you man. Asking for help and being rude about it, seriously?

Lexel · 2019-04-25T14:59:29.000Z

DB Custom:

Man, Coming in here is like barging into a room full of geeks that ran out of coffee!

Some people need to take a chill pill and get over themselves… Lexel, talking to you man. Asking for help and being rude about it, seriously?

Toykeeper is trelling for last months first Texas Ace
then me
last Astrolux
that her firmware has no bug its perfectly regulating temperature
does not want to write new code Astrolux paying her because she claims there is no bug

It works only if you compile the hard turbo dropdown which does after 30s a hard stepdown then limit max. current to a fraction of turbo

We had here lights that you could fry egg on and still getting hotter

There is some sort of heat up oscillation if the thermal mass and heat ratio is making slow cool downs and fast heat up

Asking just for simple code to be written:
if actual temperature is >5K than ceiling stay at MIN_THERM_STEPDOWN xxx

ignoring the problem for last months now the MF01S could be build but still no working firmware that keeps the light at safe temperature levels

TA, Astrolux and me spent hours and hours trying to fix the hardware but its not possible as the code does not work above the ceiling temperature