...any thoughts on to what might be wrong?
Ok, if this is a likely fix, i will throw in an additional (or two) LT3763 when i finally manage to order the parts for my bare boards kit.
Thanks for the quick reply.
...any thoughts on to what might be wrong?All is good -- apparently it was a PEBCAT issue (Problem Existed Between Chair and Touchscreen).
The system was powering up with the current limits set to 0. Once setting a non-zero current limit, everything (including the coupling) is working great!
Thanks for all the suggestions.
Installing either module individually or both simultaneously, module self-test will fail frequently (~50%). Both modules fail sporadically and with identical symptoms. Typically, only a single module fails during a boot session. Rarely, both modules will pass self-test. If a module passes self-test, it can successfully drive 1A @ 20V into a Maynuo 9811 active load. If a module fails self-test, it cannot be used unless the system is power-cycled and the module happens to self-test successfully.
Today I've used both BB3's on actual work powering some LED's and eval boards. Works a treat!
However: in my playing I noticed if you set the OCP to values lower than 20ms and enabled, strange things happen. i.e. the whole chassis reboots? / enters standby when trying to enable the module.
For DCP405's... setting the value to less than 3ms = causes the stanby bug on output enable.
For DCM220's... setting to less than 10ms = causes the standby bug on output enable.
If it is out of spec to have the OC protection work <20ms on modules (the default). This is ok, but I think the user should be prevented from trying to enter "invalid" values. If the units are designed to work down to "0ms", then any ideas what is causing the sudden stanby panics?
I made two quick vids showing:
First vid = Ch1 @ 10ms, Ch2 @ 1ms (both DCP405). http://danielbriggs.co.uk/images/BB3_OCP_Issue1.mp4
Second vid = Ch2 @ 10ms, Ch2 @ 5ms (both DCM220). http://danielbriggs.co.uk/images/BB3_OCP_Issue2.mp4
Ok, please let me know what you have defined here under "Shutdown when protection tripped":
Very very very minor requests:
- Is it possible to get the built in BB3 file manager to hide hidden folders?
When you plug one of the SD cards into a Windows PC you get "System Volume Information" folder created. And plugged into OS X you get lots of crap: ".Trashes", ".fseventsd", ".Spotlight...." etc.
It would just offer less clutter to the nice file manager view you have made.
- I'm sure it's a rounding fragment, or floating point issue, but often when the display is reading "0V" or "0A" it's displaying as "-0.0V or "-0.0A" this seems a bit illogical, so any way to clamp it to remove the minus when it's at zero (or as close as possible). Or am I being too picky (pls tell me to shut up if so!)
I have a question about grounding: I know we can remove a little paint around the mounting hole on the bottom plate where it meets the grounded mount point on the AUX-PS module. But is there any benefit to removing the paint around the mounting holes where the MCU and BP3C modules are mounted?
Hi Dan, feel free to open a new issue with for this on Github.
Returning to the issues I've reported: Is it still your position that I must return both modules for repair?
Returning to the issues I've reported: Is it still your position that I must return both modules for repair?
My concern with sending them back is that the issue may lie elsewhere - it would be frustrating and disappointing to get new modules and find you still have the same problem.
I haven't seen any other people reporting this problem, and it seems unlikely you would have received two modules that tested okay for Denis, but developed identical subtle faults during transit - my money would be on some other common element. Unfortunately, this is one of the risks of buying a kit of modules - the modules have been tested, but not tested together. The errors suggest to me intermittent I2C comms with the DCP405 modules, yet other I2C modules in the system appear okay, eg fan controller, and backplane, so maybe the issue is with the power supplied to the DCP405 modules. Since the DCP405 have independent Meanwell 48V power supplies - maybe there is an issue with their upstream supply from the AUX board (maybe the soft start), or a loose AC connector?
BTW, I'm just another customer - I don't speak for the Envox team.