Convoy XHP35 Driver Analysis / Testing / Schematic

51 posts / 0 new
Last post
icpart
Offline
Last seen: 1 day 13 hours ago
Joined: 04/15/2019 - 01:13
Posts: 361
Location: Bulgaria

Hi here are shared results from PSPice MP3429 simulation with OPA333 and with 1nF compensation capacitor and without it.
https://drive.google.com/file/d/1QdqpdS0zbyeZq07SdJRQYphotLIBf0tb/view?u...
https://drive.google.com/file/d/14RevoKFqxhwbEhwR3nTXxArclXqOwSXa/view?u...
https://drive.google.com/file/d/1JR0oMlGXYW2uxAnudviDN7l8pKKAiKIH/view?u...

From simulation we can see that with compensated OPamp the output current and voltage is very clean and stable compared to uncompensated circuit. There is ringing and large pulsating in output voltage and current.

polarweis
polarweis's picture
Offline
Last seen: 3 weeks 5 days ago
Joined: 05/31/2017 - 17:05
Posts: 572

If got a problem with this driver. It skips to the second mode after about 10/20 sec on first mode. I checked every connection in switch etc and I think the problem is in the driver. Does anyone know where the problem is coming from?

"It wouldn’t be so bright if there wasn’t a shadow every once in a while." - Jason Mraz

agnelucio
agnelucio's picture
Offline
Last seen: 1 month 1 week ago
Joined: 01/04/2015 - 12:36
Posts: 154
Location: UK

icpart, thanks for sharing that. It’s definitely an interesting problem.

I’ll see if I can import the MP3429 Spice model into LTSpice and run some more tests.

I notice that you’ve picked the OPA2333 op-amp with a 350kHz gain-bandwidth product.

Maybe a different op-amp would alter the behaviour (e.g. OPA365)…

Edit: I tried connecting a 10nF capacitor to the op-amp to form an integrator, and while there was no oscillation, it became very slow to respond to changing input.
Adjusting the brightness worked fine, but there was a perceiveable ‘lag’ in brightness changes, and any sort of strobe/flashing mode was a complete mess.

I tested input to the stock configuration, and strobe at 0.1ms pulse length worked up to 2.5kHz. So the stock op-amp setup works very well with stroboscope etc…

icpart
Offline
Last seen: 1 day 13 hours ago
Joined: 04/15/2019 - 01:13
Posts: 361
Location: Bulgaria

agnelucio wrote:
icpart, thanks for sharing that. It’s definitely an interesting problem.

I’ll see if I can import the MP3429 Spice model into LTSpice and run some more tests.

I notice that you’ve picked the OPA2333 op-amp with a 350kHz gain-bandwidth product.

Maybe a different op-amp would alter the behaviour (e.g. OPA365)…


OPA2333 and OPA333 are the same spice models. I choose OPA333 because is used in most circuits of chinese boost drivers like H2-C and H1-A. Also the loneoceans has used the same OPAMP in itss GXB172 driver which is based also on MP3431 circuit. OPA333 is very precision and low power consumption opamp compared to OPA365. OPA333 is zero drift chopper stabilizated OPAMP which have very low offset voltage but in most cases these amps are to slow and with limithed bandwith. Also the power consumption is high. So if you whant to have great low current regulation like moonlight you will need very percision OPamp to measure accurately very low currents like uA. I also searched for precision comparators time ago wgich will be better solution but they don’t exist at all, so we need to use here OPAMP like comparator. Another possible solution is to be used additional OPAMP to amplify current sense voltage and compared but we will have additional stage which will slow down feedback loop also design will be more complex. I wrote a while ago that best solutions will be driver and feedback to be controlled from MCU and not dedicated DC/DC converter i.e. will need digital power supply with PID control in basic concept. One russian guy Tamagochi in fonarevka have similar great driver based at that concept: http://forum.fonarevka.ru/showthread.php?t=37158
You cant. The spice model is encrypted and can be only used in Orcad Pspice but you can use free simulator Simetrix/Simplis from MPS which they called MPSmart. The problem with MPSmart is that the model is not exactly typical Spice model. They used special fast simulation engine called Simetrix specially designed for simulations of switch mode supllies which is very fast compared to Spice, if you need to simulate something for minutes in PSpice here it take only seconds for that. But this engine lack of support of typical Spice models. They have a model for diode and OPamp of which you must add parameters manual. I tried that months ago and I think simulation will maybe not very accurate but you can try.
Yes it support both but when you need to simulate Spice based circuit you need use theirs second simulation engine called Simplis for that.
Here is the original software https://www.simetrix.co.uk/
Monolithic Power System just used limited but very good rebranded version MPSmart of Simetrix. Microchip also used the same analog free simaltor which they called MPlab Mindi.
PS
I tested my boost converter circuit with OPA365 without compensation and it is wrost, the circuit go to be very unstable and oscillate with higer frequency compared to OPA333. Yes with faster OPAMP we have better respond from feedback loop and we can just use lower capacitance for compensation like pF compared to slower opamps. Try to use 1nF capacitor. From simulations I have made it seems to be good choise in most cases. If you have oscilloscope can you post some waveform over sense resistor and output voltage over LED. It will be interesting to compare them with and without capacitor. I will order maybe soon this driver. It seems to be good choise for cheap DEVboard at all for MP3431. Also respond of ciruit is slowed down from PWM DAC and output RC filter. In future if we have MCU with integrated DAC and firmware support of it that will be great.

Quote:
Adjusting the brightness worked fine, but there was a perceiveable ‘lag’ in brightness changes, and any sort of strobe/flashing mode was a complete mess.

I tested input to the stock configuration, and strobe at 0.1ms pulse length worked up to 2.5kHz. So the stock op-amp setup works very well with stroboscope etc…

How did you test that lag? And what impulse you injected in the driver, do you used some square wave function generator?
WTF
Offline
Last seen: 10 months 1 week ago
Joined: 03/05/2017 - 20:13
Posts: 318

Could a dedicated MCU replace the op amp? Just feed the pwm and sense resistor into it and eliminate some input stage components.

It might keep more noise out of the signal path and take up less board space.

icpart
Offline
Last seen: 1 day 13 hours ago
Joined: 04/15/2019 - 01:13
Posts: 361
Location: Bulgaria

If you we remove external controller it will be best at all. Just view of Tamagochi SMPS driver. There is no any external DC/DC switching controller at all. In that desisgn with MP3431 yes we can remove opamp to sense and compare voltages. MCU can handle and meausre LED current and adjust via PWM DAC and FB pin output voltage. But there is another problem. To measure current from low ohmic sense resistor we need to amplify voltage over it and we need opamp anyway. The Attiny ADC resolution is just 10 bit and with internal 1.1V reference we have about 1mV resolution to be used for direct current measurements. So over 30mOhm sense resistor lower current which we can measure will be around 35mA per bit, also ADC have errors with some bits deviation and finally that be very unaccurate measurements at all.
If we have 14, 16-bit or the best 24-bit ADC that will be best approach without amplification. There is technique called ADC oversampling which can be used in Attiny to get higher resolution to 12bit, but that method is slow for measurements. But anyway SC-70 case opamp occupy very little space on PCB.

WTF
Offline
Last seen: 10 months 1 week ago
Joined: 03/05/2017 - 20:13
Posts: 318

I could not find much information in the Tamagochi thread and I don’t enough knowledge to base much of an opinion on it. I read about a pic controller optimized for smps and it tops out at 300khz. It has features to keep the converter in focus and stable while the processor preforms other functions. Without those features that driver must have a pretty low switching frequency so it won’t have much use in high powered designs.

I hoped getting rid of about five passives that convert the pwm signal plus the op amp and replacing it with an attiny would save space. As usual there is always a good reason for not doing something, sometimes I just can’t see it.

icpart
Offline
Last seen: 1 day 13 hours ago
Joined: 04/15/2019 - 01:13
Posts: 361
Location: Bulgaria


Here is direct link to circuit of first version of Tamagochi driver on another thread over fonarevka
There are also links to hex file for attiny85 http://forum.fonarevka.ru/showthread.php?t=35292 for another version of that driver.
Very interesting how he generate such 300kHz high PMW frequency from attiny85. Also I readed that he implement the PID control algorithm for SMPS regulation.
Yes you right the output power is limited because of use of such low PWM frequency. I readed that driver have 18W output power at 6V, so 3A output current is very good from attiny control circuit.

Barkuti
Barkuti's picture
Offline
Last seen: 18 min 56 sec ago
Joined: 02/19/2014 - 14:46
Posts: 5576
Location: Alhama de Murcia, Spain

Sorry to interrupt a bit this long boost converter design and optimization off-topic people.  I made a question a couple days ago in #26, could you please comment about it? Auto-quoting myself:

Barkuti wrote:

One more question which could be of interest to some, any potential problems making this driver work with 2S battery? It is within range of the boost converter. Only potential problem I see is with the VLDO, as the stock one probably has a 6V maximum input voltage limit. The rest is, well, for 2S input we need to correct the way the LVP gets its feedback, disconnecting R2 from the VLDO and connecting it to input. So: a) we do away with the stock R2; b) We install a new R2 of adequate value, 243KΩ would for example set the cut-off at 5.5V, but we set the new R2 like if we had rotated it 180° at its right side terminal, so R2 ends up disconnected from the VLDO and with its now left leg connected to the LVP pin and R3; and c) We lie a wire from VCC to the now free right side R2 terminal; as I see it we can take VCC from either side of R1. 

The human mind, and its programming, is at the forefront of a particular battle of The Light vs evil dark forces. Nearly every human being on this beautiful planet “Earth” has some sort of negative mind programming in its mind. And you better take care of your mind programming, or someone else will in this wicked world.

Please avoid fully quoting lenghty posts, namely with nested quotes. Trim quotes down to the essential. Helps with neatness and legibility. Thanks.

I recommend saying no to Covid vaccine. Listen to your spirit or soul. Innocent 

Keanu Reeves may need your help. Join his Telegram channel here.

icpart
Offline
Last seen: 1 day 13 hours ago
Joined: 04/15/2019 - 01:13
Posts: 361
Location: Bulgaria

Barkuti wrote:

Sorry to interrupt a bit this long boost converter design and optimization off-topic people.  I made a question a couple days ago in #26, could you please comment about it? Auto-quoting myself:


Barkuti wrote:

One more question which could be of interest to some, any potential problems making this driver work with 2S battery? It is within range of the boost converter. Only potential problem I see is with the VLDO, as the stock one probably has a 6V maximum input voltage limit. The rest is, well, for 2S input we need to correct the way the LVP gets its feedback, disconnecting R2 from the VLDO and connecting it to input. So: a) we do away with the stock R2; b) We install a new R2 of adequate value, 243KΩ would for example set the cut-off at 5.5V, but we set the new R2 like if we had rotated it 180° at its right side terminal, so R2 ends up disconnected from the VLDO and with its now left leg connected to the LVP pin and R3; and c) We lie a wire from VCC to the now free right side R2 terminal; as I see it we can take VCC from either side of R1. 



I think it must will work. We just recalculate voltage divider for higher cutoff voltage. Direct connection to Vcc battery voltage is the best. Also if we want to protect LDO we can increase R1 value for higher voltage drop of it or install parralel of it 5Vzener for overvoltage protection but best will be to just use higher voltage LDO.
Chatika vas Paus
Chatika vas Paus's picture
Offline
Last seen: 4 hours 21 min ago
Joined: 09/03/2017 - 13:46
Posts: 1053

agnelucio or anyone who has this driver. Is it safe to reduce the diameter to 21mm?

Barkuti
Barkuti's picture
Offline
Last seen: 18 min 56 sec ago
Joined: 02/19/2014 - 14:46
Posts: 5576
Location: Alhama de Murcia, Spain

icpart wrote:
… Direct connection to Vcc battery voltage is the best. Also if we want to protect LDO we can increase R1 value for higher voltage drop of it or install parralel of it 5Vzener for overvoltage protection but best will be to just use higher voltage LDO.

Thanks. I wonder a little what is the point of R1, because the VLDO regulator feeds the MCU and the Current Control Feedback Comparator -CCFC- stages. The MCU theoretically drains less than 1mA (46µA / MHz according to Renesas RL78/GU10 datasheet), and don't know about the CCFC but pretty sure quite low power too (< 10mA). When ≈0.01A go across a 4.7Ω resistor the voltage drop is ≈47mV, so what is the point I wonder. 

You mean a 5.1V zener reverse polarized in parallel with pins 3 and 1 from the VLDO regulator. In this case, R1 would probably need to be recalculated (never done this zener stuff in my life LoL). Would be nice to know, we need to figure out the regulator's power consumption (current to MCU and CCFC), doesn't it? Or is it easier to find a higher input voltage VLDO regulator? No hurry for now, though.

The human mind, and its programming, is at the forefront of a particular battle of The Light vs evil dark forces. Nearly every human being on this beautiful planet “Earth” has some sort of negative mind programming in its mind. And you better take care of your mind programming, or someone else will in this wicked world.

Please avoid fully quoting lenghty posts, namely with nested quotes. Trim quotes down to the essential. Helps with neatness and legibility. Thanks.

I recommend saying no to Covid vaccine. Listen to your spirit or soul. Innocent 

Keanu Reeves may need your help. Join his Telegram channel here.

agnelucio
agnelucio's picture
Offline
Last seen: 1 month 1 week ago
Joined: 01/04/2015 - 12:36
Posts: 154
Location: UK

icpart wrote:
If you we remove external controller it will be best at all.

I think it would be impossible for MCU to do the MP3431's job. The MCU could use ADC and PWM to make a switching converter, but performance and efficiency would be very limited.

Companies like Monolithic, TI, LT have all spent millions over the last 20+ years to make dedicated DC/DC ICs so highly optimised for power and efficiency.

And with the op-amp, you are right, the small-signal performance is far better than 10/12bit ADC as you mentioned.

The Attiny1634 has a built-in comparator, but it's not good enough for this feedback loop.

 

Barkuti wrote:
Sorry to interrupt a bit this long boost converter design and optimization off-topic people.

But that IS the topic Big Smile . We need to understand the driver design positives and flaws if we want to improve it!

 

Chatika vas Paus wrote:
agnelucio or anyone who has this driver. Is it safe to reduce the diameter to 21mm?

I'd say no. It depends on what you're mounting it in, but the top side ground ring is already very narrow.

Barkuti
Barkuti's picture
Offline
Last seen: 18 min 56 sec ago
Joined: 02/19/2014 - 14:46
Posts: 5576
Location: Alhama de Murcia, Spain

I think I found a suitable SOT-23 linear regulator supporting higher than 6V input voltages, the Zetex ZMR330FTA

But still not a word I've heard about the onboard stock one, can someone tell me which device it is? So we can know its pinout, maximum input voltage and etc.

The human mind, and its programming, is at the forefront of a particular battle of The Light vs evil dark forces. Nearly every human being on this beautiful planet “Earth” has some sort of negative mind programming in its mind. And you better take care of your mind programming, or someone else will in this wicked world.

Please avoid fully quoting lenghty posts, namely with nested quotes. Trim quotes down to the essential. Helps with neatness and legibility. Thanks.

I recommend saying no to Covid vaccine. Listen to your spirit or soul. Innocent 

Keanu Reeves may need your help. Join his Telegram channel here.

icpart
Offline
Last seen: 1 day 13 hours ago
Joined: 04/15/2019 - 01:13
Posts: 361
Location: Bulgaria

Barkuti wrote:

icpart wrote:
… Direct connection to Vcc battery voltage is the best. Also if we want to protect LDO we can increase R1 value for higher voltage drop of it or install parralel of it 5Vzener for overvoltage protection but best will be to just use higher voltage LDO.

Thanks. I wonder a little what is the point of R1, because the VLDO regulator feeds the MCU and the Current Control Feedback Comparator CCFC stages. The MCU theoretically drains less than 1mA (46µA / MHz according to Renesas RL78/GU10 datasheet), and don’t know about the CCFC but pretty sure quite low power too (< 10mA). When ≈0.01A go across a 4.7Ω resistor the voltage drop is ≈47mV, so what is the point I wonder. 


You mean a 5.1V zener reverse polarized in parallel with pins 3 and 1 from the VLDO regulator. In this case, R1 would probably need to be recalculated (never done this zener stuff in my life LoL). Would be nice to know, we need to figure out the regulator’s power consumption (current to MCU and CCFC), doesn’t it? Or is it easier to find a higher input voltage VLDO regulator? No hurry for now, though.


The point of R1 is cloned from classic DEL and TA drivers. The R1C1 form RC filter which clean input voltage. Because we have heavy load with high input currents there is pulsating voltage from battery. Also 4.7 ohm is exactly the same used in TA drivers. Also C1 is decoupling capacitor for MCU.
This Zetex LDO is very good indeed. The max input voltage is 22V and also have very low self consumption like 40uA max. Just you need to compare if pinouts are the same as installed on PCB LDO for direct replacement.
Yes you can use any zener diode larger from 3.8V-5.1V. Is good to have enough voltage room for LDO to stabilize to 3.3V Also another tip if you want to lower output current is just low power supply voltage of MCU Big Smile So in that case max reference voltage on inverting pin of opamp will be lower.

Quote:
Companies like Monolithic, TI, LT have all spent millions over the last 20+ years to make dedicated DC/DC ICs so highly optimised for power and efficiency.

And with the op-amp, you are right, the small-signal performance is far better than 10/12bit ADC as you mentioned.

The Attiny1634 has a built-in comparator, but it’s not good enough for this feedback loop.


By the way Microchip have dedicated enhancement 8-bit micros with analog peripherals for power supply control like high resolution and fast PWM and ramp generator. Just see this AN from them for SEPIC led driver
http://ww1.microchip.com/downloads/en/Appnotes/00001978C.pdf
Barkuti
Barkuti's picture
Offline
Last seen: 18 min 56 sec ago
Joined: 02/19/2014 - 14:46
Posts: 5576
Location: Alhama de Murcia, Spain

After taking a peek at the newer AA/14500/16340 driver from Convoy, I think I have identified the SOT-23 LDO regulator in there and here. Marking in this (XHP35) driver's 3-pin SOT-23 is V1SE. Found it is a MicrOne ME6209A-33 regulator, check here (datasheet). Up to 18V of input, this means there's no need to replace it for 2S battery operation. 

The human mind, and its programming, is at the forefront of a particular battle of The Light vs evil dark forces. Nearly every human being on this beautiful planet “Earth” has some sort of negative mind programming in its mind. And you better take care of your mind programming, or someone else will in this wicked world.

Please avoid fully quoting lenghty posts, namely with nested quotes. Trim quotes down to the essential. Helps with neatness and legibility. Thanks.

I recommend saying no to Covid vaccine. Listen to your spirit or soul. Innocent 

Keanu Reeves may need your help. Join his Telegram channel here.

icpart
Offline
Last seen: 1 day 13 hours ago
Joined: 04/15/2019 - 01:13
Posts: 361
Location: Bulgaria

Barkuti wrote:

After taking a peek at the newer AA/14500/16340 driver from Convoy, I think I have identified the SOT-23 LDO regulator in there and here. Marking in this (XHP35) driver’s 3-pin SOT-23 is V1SE. Found it is a MicrOne ME6209A-33 regulator, check here (datasheet). Up to 18V of input, this means there’s no need to replace it for 2S battery operation. 


Nice find Thumbs Up From real photo from listed product here for 3.3V LDO LCSC and I also search over and find there are variants of that marking V1JE,V1SF, V1SE, V1QH. Seems the first two characters are voltage code and last two are code for year and month of production maybe.
pio-w4u
Offline
Last seen: 2 weeks 3 hours ago
Joined: 12/01/2015 - 03:11
Posts: 2
Location: Poland

If I would like to use this driver as single mode by removing the MCU what connections I should provide? Many thanks in advance.

icpart
Offline
Last seen: 1 day 13 hours ago
Joined: 04/15/2019 - 01:13
Posts: 361
Location: Bulgaria

pio-w4u wrote:
If I would like to use this driver as single mode by removing the MCU what connections I should provide? Many thanks in advance.

If you remove R9 from schematic you will remove any control from MCU also you need to EN pin to positive terminal. But in that case you will lose any current control of circuit. It will work as ordinary DC DC power supply with fixed output voltage. Another better option is to recalculate the voltage divider which come from output of MCU to input of opamp.
pio-w4u
Offline
Last seen: 2 weeks 3 hours ago
Joined: 12/01/2015 - 03:11
Posts: 2
Location: Poland

Many thanks for your suggestion and help Smile

Pages