Structured approach to testing BL Ctrls (2.0)

[davidp]

I would remove the jumpers on the C & D pads that support the non CAP end of the board and flip the inner boards up. If you used an L shaped piece of wire for those jumpers they are very easy to "spin" around. Then you can get to the inside.  I didn't think about an edge connector. That's a great idea.

[funk_e]

For those of you that have not seen it yet, here is the link to the wiki for updating these boards:
http://www.mikrokopter.de/ucwiki/en/BrushlessCtrl#Software_update

This shows the edge connector method, although it does not show it on controllers attached to a dist. board.

[davidp]

I think this is worth a try. Full source code is available, too. It's an IC2 - PWM converter, and the design is dead simple:

http://forum.mikrokopter.de/topic-11206-1.html

[Buzzed]

Who's going to step up to the plate and give this a try? Doing a firmware update without removing BLs could save a lot of messing around. We need documentation on a simple fix.

[funk_e]

I think this is worth a try. Full source code is available, too. It's an IC2 - PWM converter, and the design is dead simple:

http://forum.mikrokopter.de/topic-11206-1.html

This is great.. allows us to use other BLCtrls in place of the MK I2C versions... Thanks davidp :-)

[funk_e]

Who's going to step up to the plate and give this a try? Doing a firmware update without removing BLs could save a lot of messing around. We need documentation on a simple fix.

I didn't think you were using the 2.0 BLCtrls Buzzed? Why do you want to do a firmware update?

[Crash]

Who's going to step up to the plate and give this a try? Doing a firmware update without removing BLs could save a lot of messing around. We need documentation on a simple fix.

Pic below: BL-CTL ProgrammierSchnittstelle. BTW, That's a 4mm Allen wrench between the pivot to spread the jaws apart a little. I think it will work. Now ... what to use for contact points.

I have the 1.2 controller boards so I have no need to update them.

Edit: I was looking at the .de site and someone linked to this: http://forum.mikrokopter.de/topic-post233798.html

I'm too tired to run it through the translator but maybe there's some ideas there.

[Buzzed]

I didn't think you were using the 2.0 BLCtrls Buzzed? Why do you want to do a firmware update?

Cripes! Mine are 1.2s man it's been a loooong Labor Day weekend. But on the good side look at all the time you just saved me. 

[chainey]

 

I just wrote a mega long update.  Then quit my browser!!
I will start again.
This forum has been very helpful.  I have posted on the German site and not a single response!

I have good news. I will share my story. ( I will add photos next week)
I bought an OKTO 2, spent three days building and instantly blew 7 BLCTRL 2.0s.
I determined that i had damaged the power distribution board while soldering the MOLEX connector and bridged +V to C or D.

I ordered a new distribution board and 4 BLCTRL 2.0s (all i could afford).
I also spent money on a better solder station, a variable DC power supply, Head mounted magnifying glasses, flux pen, and various other small tools.

I removed all of the broken BLCTRLs, removed the capacitors, cleaned the boards and checked for solder bridges or damage using a USB micro scope (very useful piece of kit).

On the new distribution board i connected the 1 working old BLCTRL and then tested by connecting the FC2.1 to the distribution board via wires and not the MOLEX connector (I did not want to damage another board).  I connected the MKUSB to the FC2.1 and then to my MACPRO running parallels and Windows 7.
The software told me BL CTRL 2 was missing (meaning that 1 was being seen).  I added the new boards, 2 then tested (OK), 3 and tested (OK), 4 and tested (OK), 5 and tested (OK).

Now for the hard bit.  I had 7 broken boards.  I managed to get hold of an old floppy disk connector that also had an IDE connector still attached.  I used a hot knife to melt away the short side of the connector so that a BLCTRL could be attached.  I added the Jumper to the MK USB (as this sends 5v to the BLCTRL).
I guessed the orientation that the side connector of the MKUSB should be connected to the IDE connector.  Lights on the MKUSB and connected BLCTRL lit up.  I reveresed the connector to see what happened - No lights. I returned to the original configuration.

In MK Tool i clicked the firmware & update terminal button and the MKUSB tried to connect to the BLCTRL. 
Nothing, no joy  :'(
I removed the BLCTRL 2.0 and added another (i have enough!)
I restarted the application and checked the connectors and YES.  Connection. It was recognised.  I updated the software using the BL-Ctrl_MEGA168_V0_30a.hex file.  It updated very quickly and recognised the address.  I am feeling a bit happy at this point.
I proceeded through the rest of my broken BL CTRLS.
I managed to update 4 out of the 7 (1 of the 3 un updateable ones has a surface mount capacitor missing!)
Next i connected three of the newly updated BL CTrls 2.0s to the distribution boards (one at a time).
I now have a distribution board with all green lights and no errors showing.
What a ride.
It was getting late but i could not resist connecting at least one motor.  I did this to BL CTRL 8 and clicked the motor test tab - wow.  This was the first time i have controlled a motor on the machine.

I hope my  little story helps and inspires some people out there to persevere.
There is a BIG lack of easy to follow instructions.
There are plenty of people who might help.
But the fact is that the help is not gonna come at the speed you require it.

Myself, i am enjoying the challenge.  I am sure i will have many more to overcome.  But for now i feel elated at overcoming quite a major hurdle (in my mind anyhow).

I will get some photos and videos on line at some point.  I promise.
Thanks again everyone.
Chainey
 

[funk_e]

Great post. Well done Chainy.

Is it possible the spike of electricity just wiped the firmware on AMTEL microcontrollers? This is why the firmware flash brought them back to life?

I wonder how many 'blown' BLCtrls are out there that just require this fix...

[Buzzed]

Good job Chainey.

Pictures and video will be well appreciated. It looks to me like in a lot of cases it's up to us to help each other.

[davidp]

I've got a whole stack of blown BLs. The older ones. I'll give this a try as soon as I can find a connector. I may just solder one or two for testing. Somehow I have 4 good BL-ctrls not on my hexa. I blew two sets and wound up with those 4 still viable. If I can recover a couple of more I also have an extra working FC now thanks to Crash and Andy, and a few others!!

[Crash]

That's great to hear Chainey. You did update the firmware on ALL the controller boards right?

[chainey]

I have only updated four so far, three are on the OKTO.
I will go back and do the rest this weekend.
Then the next stage!
How on earth do i calibrate the thing!!!

Back to the forum i think!

[davidp]

Chainey, did all of your BLs light up when connected to the MKUSB? All of the ones I tried to recover do not light up when power is applied. None of them worked, either. I only populated 4 wires in the connector. RX, TX, +5, GND .  Do I need to add more ?

For those interested I cut up an older SCT Performance chip to get a connector. After I cut the ends off the wide connector this worked really well. I had a few dead chips around from testing.