Need a custom driver made(red/blue)

I need a custom driver made!

First mode- Red/Blue Strobe
(4 Red flash - 4 Blue flash - 4 Red flash - 4 Blue flash etc.)

Second mode - Blue strobe
(4 Blue flash - 4 Blue flash - 4 Blue flash - 4 Blue flash etc.)

3rd mode - Red strobe
(4 Red flash - 4 Red flash - 4 Red flash - 4 Red flash etc.)

Always starts in first mode

No more than 1A

Clicky switch (I’ll be using reverse)

17mm

I’ll be using a XML colour OR an XPE2 red and XPE2 blue

Other options would be good eg. Press and hold changes brightness of strobe

Anyone who can do it?

I think that’s possible with a 2 channel driver, 3 7135 per channel, and bistro with custom modes.

Edit: Maybe the Vf of the blue LED is a bit high…

Yeh should be fine, but I don’t have the kit to flash the firmware onto the driver, hence I need someone to make it for me

I have the intl outdoor colour driver and the red/blue mode is good but you have to skip 4 modes to get to it.

If someone could flash that driver for the red/blue modes above that would be ideal!

Bump

Toykeeper can make that, and TomE, but not many people on BLF do firmware programming.

Yeah, it’d be great if we had a few more firmware developers around. We do actually have a few that know how to tweak existing firmware, but they do it only for their own projects. Tom E and ToyKeeper are the two I know of that are most actively developing firmware, with Flintrock and Texas_Ace doing some pretty heavy firmware modding as well at times.

Do you have a physical driver board you’re going to use, or do you need one of those made as well?

Well bistro-HD has more of my own code now than it has from original bistro, so pretty heavily modded yes and yet still very firmly intended to act like the nice and simple original, but Mike C and I think Flashy Mike also make pretty elaborate drivers, just not open source ones, which isn’t required here. And Lexel may be able to do some mods like this and does build and flash boards.

First you need a board. I don’t know a board with 2 channels of 3 7135. You could take a standard TA triple channel board and try to stack 3 7135s on the single 7135 channel. Srike that, those channels still drive the same LED.

Then you need the software. Yes bistro HD CAN do it, but it’s not just a matter of configuring custom modegroups. You need custom strobes. We can set set three levels in the ramps like:

red: 0 255 0 255 ( last mode, both on, unused in your spec, but added anyway)
blue: 0 0 255 255
#define RED 2
#define BLUE 3

Then your modegroup will look like

{ RBSTROBE BSTROBE RSTROBE 0}

Then just have to give those strobes an identifier in the same modegroup file (unless it’s in the config file still, I forgot) and the hardest part, program them in the code:

UPDATE… actually it’s now setup to be enabled in the modegroup file (just follow the existing examples) but the identifiers got moved back to bistro-hd.c

they look like this:
/* Define strobe magic numbers */
//Now separate from actually selecting which ones are used.

#define BATTCHECK 244 // Convenience code for battery check mode
//mode codes for strobes, must be less than MINIMUM_OVERRIDE_MODE
#define BIKING_STROBE 243 // Single flash biking strobe mode
#define FULL_BIKING_STROBE // Stutter bike strobe, uncomment to enable
#define POLICE_STROBE 242 // Dual mode alternating strobe

and at the bottom you’d need new ones like:
#define RBSTROBE 233

The numbers don’t matter so long as they are lower than existing ones. They basically assign a virtual ramp level to the strobe modes and are used in the conditionals in the code below.

That will look something like this:

#ifdef USE_RBSTROBE
        else if (output == RBSTROBE) {
            for(i=0;i<4;i++) {
                set_level(RED);
                _delay_ms(250);
                set_level(0);
                _delay_ms(250);
            }
             for(i=0;i<4;i++) {
                set_level(BLUE);
                _delay_ms(250);
                set_level(0);
                _delay_ms(250);
            }
      }
#endif
#ifdef USE_RSTROBE
        else if (output == RSTROBE) {
 ....

Having trouble getting the == character in the conditional to show.

So if you can write how you actually want all those to look, ie particularly the timings, the rest is pretty simple actually. But I won’t flash it for you. Maybe you can get lexel to build the hardware as described and flash it for you.

I would strongly encourage you though to download bistro HD,

https://budgetlightforum.com/t/-/44344

look at the modegroup and config files (start with the TA-OTSM configs and just comment out the FET channel and modify the other two), look at the section of code on strobes (ex: look for BIKING_STROBE) in bistro-hd.c And try to modify in the way I show above. First try the one-click compile script included before modifying anything. You will need to install atmel studio 7 or winavr to use one of the compile scripts. You will also need to read the manual section on compiling. If you're a quick study, you can have it all figured out and done in an hour even if you've never programmed anything, given that I've given you most of what you need above and most of the rest in the compile instructions in the manual.

Updated, still not sure what board to use. LEXEL could probably custom wire one to work or maybe something like it exists, but I don't know.

Thanks, Flintrock. I didn’t mean to discount your work. I didn’t know how much you’d changed with Bistro-HD.

Lots of people could whip up a custom board for this. It isn’t really that hard in Eagle (Or KiCad if you’re Texas_Ace). I could do it if given the parameters. (size, shape of board, number of channels, number of regulators per channel, etc.)

That’s a lot of information!

I have this driver Here

That maybe that could be used? Just with re flashed firmware for red and blue only?

Is double sided driver accepted? I could make a custom driver by easily changing the design of one of my current drivers, but it would have to be a double sided driver. It would be ATtiny1634 based.

However, I wouldn’t do it unless you committed to it as I have absolutely no personal interest in a driver like this.

Looks like that driver would be perfect for your needs. You just need some custom firmware for it and it should be good to go.

I think this driver is the best/least hassle option to save making a full new driver

This code thing is new to me so I’ll try and figure it out but I’m not sure how it will go. Is anyone able to actually flash it onto that driver for me? As I don’t have the hardware to do that either.

Someone else will have to help you with this as I only work with 1634 MCU now days. You could always try asking Kaidomain to forward your request to the driver developer.

Mike C's board is a different chip. I don't know of any open source firmware for that chip, which just means Mike C will need to handle it, so good for 3tronics, but there may be some. I've been considering adding support for it or a similar chip in bistro-HD but this is not the right project to try that as if there are problems there's a chain of people needed to work through them and 3tronics doesn't have much experience, no offense. The strobe code will I'm sure look almost identical on anyone's driver, and it would probably still help if you fill that out or at least describe the strobe sequence in detail(but that's the most direct way), and post it back. Just knowing that sequence should be most of the work regardless which firmware base is used. The rest of the firmware base will mostly be disabled anyway from the sounds of the request.

Speaking of which, I guess there will have to be some consideration of how to handle LVP. For example bisroHD would stepping "down" through modes until voltage was ok or the light went off. That would probably ok, it would change strobe colors a couple of times, voltage would still be too, high, then it would shut off. Could modify that slightly to just blink three times and shutoff or something. I guess a similar thought should be given to any firmware.

David, I didn't take any offense, but getting all the new stuff crammed into HD on a small chip while supporting many hardware configurations really did require an overhaul of many things. The fact that's it's not obvious was kind of the goal, so mission accomplished, because I do like TK's invention and sometimes also consistency. Mike C has more elaborate drivers than I for that matter as I can tell and makes all that cramming moot by going with a high powered chip.

As for that Kaidomain board, it looks like it will fit an attiny25/45 chip or maybe already even has one. Do you know? In that case it would work with a modified bistro or bistro-HD. Of course if the developer is willing to customize the firmware then all done. If not maybe she's willing to flash a custom firmware at least.

Updated code above. Even I forgot how things work briefly. Ramps start at 1 not 0 so changed the defines for RED and BLUE modes accordingly.

Before you can get an answer to that you have to identify what the MCU is. As you have one of these drivers, are you able to see what MCU it has? Can you read anything on it?

The chip is totally blank apart from the dot in the corner

Thanks, I’ve not had a chance to look at it yet as I’m pretty busy at work but I’ll get round to it ASAP