Interesting, might have to order one of those.
The fact that it works but not under steady on, might inidicate something is pulling more current than can be sustained for more than a short capacitively-backed burst, maybe a partial short or breakdown, possibly in the control pin of that single 7135, drawing too much current, or a current starvation at the mcu side. You say the mcu voltage is fine but is it fine without pwm? How can you know that if non-pwm doesn't work. The problem with a 7135 short is how does it explain the FET not working? ON the other hand I agree that 200ohms shouldn't starve the mcu.
Exactly the conundrum I have. Everything seems to work individually but not as a whole.
to make things even stranger, if I now flash battcheck to the MCU it flashes out the voltage just like it should but if I flash bistro back to it, same thing. Quick flash of low level light and then nothing.
Well a 7135 with a partially shorted controll pin might still "work" if the pin is fed enough current from test voltage, but might pull down a whole mcu too. Just making things up here kind of though.
Yeah, I had the same thoughts but it didn’t explain why the bank works fine in the same conditions. It should have been even worse since there were 6 of them together.
I was looking at the Digikey shopping cart for parts and I’m wondering if the part representing R1 listed in the cart is slightly wrong.
R1 is described as 19.1kΩ resistor, but the closest thing I saw in the cart is a 22kΩ resistor. Was this the cart wrong or is one of them a newer known good parts list?
Thanks for reminding me, I need to update that. Either will work but I have switched back to 19.1K myself as it makes OTC timing more reliable. It is also what the official firmware is setup around.
Although hopefully the new OTC method we are discussing in the firmware thread works out and removes all the hassle with OTC completely. Till then I recommend a 19.1K 1% 0603 resistor.
I just updated the cart link with the 19.1K R1, so it should be good now.
Well, I thought if only the single is shorted, internally maybe. But it doesn't seem to explain the FET quitting anyway.
I recently built one of these up for an EE X6 triple XML2 and I used 380mA 7135's (all I had at the time). It was flashed with PD68's tripledown bistro. It all worked fine except moonlight. I assume the 380mA 7135 on the +1 channel is unable to go that low.
Can I use a 350mA 7135 on the +1 channel and 380's on the bank?
Yes, I recommend using 350ma 7135’s but you can do whatever you want.
Also check the OP, I have the “Texas Avenger” version of bistro uploaded and it has hex files with a few different moon mode options. The 4 pwm for moon might get moon to work for you.
I usually use 380ma for the bank and 350ma for the single, but I’m starting to agree more with TA and think I’ll just go to using 350ma next time I order from FT.
Okay, thanks for the info.
I got the PD68 tripledown chip from Richard. I actually just got Atmel studio 7 downloaded last night (no idea how to use it). I installed the driver for the usbasp, seems to be working. I downloaded the WINavr from Hoop's tutorial, not to sure about it.
Anyway I downloaded the TA Bistro file and connected the chip. Without studio 7 or WINavr open I opened the "Bistro-Texas-Avenger-V1.zip\avrdude Simply run flash25bistro.bat from command line" folder and ran "flash25bistro". A black command prompt? screen came up for half a second and the usbasp LEDs flickered and that was it. Did it flash? Do i even need Atmel studio or WINavr?
This is my first time trying this and i have absolutely no clue whats going on or why.
I set it up with the hex files for exactly this reason, this way you do not have to touch a line of code unless you want to :laughing:
You simply need to run that file from the command line to see what is going on. The easiest way for this is at least with windows 7 to hold shift and right click in the folder the file is stored in. There should be an option in the menu to “open command window here”.
Click that and it should come up with a command prompt with a blinking line and the folder location you have the files stored in in the top left of the window.
Then simply type flash25bistro.bat and press enter. It will then run AVR dude and try to flash the file. It will tell you if there is an error or if it was successful in the messages that follow.
If it was disappearing instantly before, then it most likely had an error, this is usually a connection error for the USBASP.
Alright, I did it just like you said and it seems to have worked correctly this time. Bout to hook it up and see what happens.
TA , is there a specific component list for this board ?
https://oshpark.com/shared_projects/r9gaWM3e
I want to use it with e-switch only , on 6V led .
thanks
All the drivers are the same, there is a component list for the LDO boards in the OP (or there should be). It is the same as the normal TA drivers except for the addition of the LDO and the change of C2 from 0.1uf to 10uf. The rest is the same IIRC but check the op to make sure.
Pretty sure this is what Tom used on his L6 LDO driver and he said it worked fine.
For those not aware it is possible a Texas Avenger V2 might be in the works, along with possibly a brand new driver as well. These would be running a yet again improved component setup that should fix OTC issues and allow them to be used with any voltage desired without having to change components (except for R1 for the voltage divider). Still in the works but they are being worked on.
Not sure if I should rename the TA V2 to something else and leave these alone or simply update these with the new design when it comes to that.
Any suggestions on a name for an updated Texas Avenger? it will be basically the same in function, just take on a slightly different form.
Texas Buck was used for the buck driver and Texas Operation is a name I am kicking around for the other driver I am working on.
Thanks , ordered some boards & LDO .
Okay my driver is working but when I program for reverse order (hi-lo) it won’t go to turbo from hi. It goes straight to batt check then into the strobes.
Mode groups 12 and 13