(25-Jun-2017, 11:49 PM)Keyboard Kid Wrote: I am using a toggle switch on a 1" lead as the boot strap. Is that OK?

This allows me a hands free very easy to use and solid connection which I can very quickly switch when trying multiple flashes. (And believe me I have tried multiple multiple flashes. Enough flashes to drive me crazy!)

Re the last point, I have never encountered the "Erase all settings" check box and I have used (or am using) Baseflight, Betaflight and Inav.

Where do I find that check box?

- DIY boot button? should be fine
- You can find "Full Chip Erase" under the firmware flasher tab, e.g.

- 

(26-Jun-2017, 12:18 AM)Oscar Wrote: - DIY boot button? should be fine
- You can find "Full Chip Erase" under the firmware flasher tab, e.g.

- 

Thanks for your help Oscar.

I was looking for "erase all settings". I have been checking "Full chip erase" when flashing to no avail sadly.

As it stands at the moment I can successfully load the firmware using iNav or Baseflight but I cannot get a connection when I try to connect to the configurator.

I have tried to load the Zadig and STM32 drivers as suggested but I am not sure how successful that was.

I did not really get any indication that I loaded successfully on both configurators.

I assume I am only loading the drivers into my computer, not the Hero.

So after hours of trying I still have made no progress. It really is very frustrating.

The only good thing so far is that I have become quite comfortable handling the configurators and flashing firmware.

So I suppose that is progress of sorts.

KK

One final thing for this morning.

I just successfully flashed Betaflight firmware, something that I had not been able to do until this morning.

But once again trying to connect with Beta configurator gave the same result.


Port 5 successfully opened.
Port 5 successfully closed.

No message about why the connection failed.

So I am lost.

Is the hero faulty? I wonder?

KK

This is the video I used as a guide. Different flight controller but same principal. It sounds like you may have a driver issue.so the step at 6:00 may be the answer if you haven't tried this yet

do you have a different computer you can try on? Or can you try a different flight controller? So far it sounds to me it's just a faulty FC...

(26-Jun-2017, 11:29 AM)Oscar Wrote: do you have a different computer you can try on? Or can you try a different flight controller? So far it sounds to me it's just a faulty FC...

Hi Oscar, I did try it on my son's Mac and I got worse results over there.

I could not load one successful firmware flash and I tried all three configurators.

On my computer I can flash firmware on all three configurators but cannot connect with them.

I am pretty sure it is either driver problems or a faulty FC.

The only other FC I have is the Hobby King V3 which I have never been able to find out what program to use with that.

I have got a little USB device to connect to it but no real information on how to use it.

Thanks for your help.

Regards,

KK

Howdy All,

Does anybody know about Jungo, some sort of usb app that can affect usb operation. (flashing)

I suspect that this may be my problem.

It is on my computer.

(26-Jun-2017, 05:44 AM)RENOV8R Wrote: This is the video I used as a guide.  Different flight controller but same principal.  It sounds like you may have a driver issue.so the step at 6:00 may be the answer if you haven't tried this yet

Hi Reno, thanks for sending that video.

I will give this a try later this morning but I have a feeling this will fix my problems.

Once again, thank you.

Regards,

KK

(26-Jun-2017, 05:44 AM)RENOV8R Wrote: This is the video I used as a guide.  Different flight controller but same principal.  It sounds like you may have a driver issue.so the step at 6:00 may be the answer if you haven't tried this yet

Hi Reno,

No luck I am afraid.

I uninstalled Jungo, installed Impulse and successfully flashed using all three configurators in turn and several times each.

Same result in all three cases. "Error no configuration inside of 10 seconds - port successfully closed."

So I am completely stumped.

There is one thing. During the entire episode the Impulse page (block, indicator?) never changed state to give me an indication that it had searched for and found the required drivers. It just kept flashing "searching for flight controller" even when the FC was plugged in with the bootstrap in place and the firmware was in the middle of flashing. Is this normal?

Would the successful flashing occur if the FC was faulty?

Anyway I have had enough for the moment I am off to the farm this morning but sadly without my trusty old Wooden It.

My DJI Naza M is still lost in the post but HobbyKing assured me this morning that it WOULD arrive some time this year. So all is not lost yet.

Anyway I have had enough of this stuff for the next few days.

Who is for another "What I would have given for FPV?" episode.

KK

KK, just curious - have you tried different USB cables?

One other thing KK, I think you mentioned a couple times that you jumped your bootloader pads, connected USB and tried to flash with pads jumped throughout the process. Once you connect, you're in BL mode, so try removing the jumper before you start the flashing process

(27-Jun-2017, 07:40 AM)sloscotty Wrote: KK, just curious - have you tried different USB cables?

Good thought Slo. I have not and I certainly should have and I certainly will tomorrow.

KK

(27-Jun-2017, 01:46 PM)RENOV8R Wrote: One other thing KK, I think you mentioned a couple times that you jumped your bootloader pads, connected USB and tried to flash with pads jumped throughout the process.  Once you connect, you're in BL mode, so try removing the jumper before you start the flashing process

Thanks Reno, I did not realise that. Something else to try tomorrow.

I have just arrived back home from the farm  and it is 10:00pm here so tomorrow it is.

Howdy Boys,

Tried new USB cable, no luck.

Tried removing bootstrap as suggested and that made flashing more reliable however still no luck connecting.

I loaded Zadig went to options a listed all devices and there was no STM32 bootloader listed.

I tried downloading BootSTM32 still no mention of STM in Zadig and all the while Impulse is flashing "Searching for flight controller".

So I am afraid I am lost.

One bit of good news, one of my lost parcels showed up yesterday (propellers) but still no Naza.

I am one step short of tearing out all of my hair.  

KK

   
How about something a bit more lighthearted?

Another in the “Oh for FPV serial”

Back in 1971 Silvertone was approached by Volkswagon Australia to radio control a full size Volkswagon 1600TLE for a TV advert. The 1600TLE was the first car to have a computerised engine management system and VW was advertising it as “The car that thinks for itself”.

In due course we did radio control a 1600 and we took it to race tracks to test the system. We fitted the various controls with servos and the blinkers and sundry other items with relays. (A rather neat way to say it was all so long ago I really cannot remember which items).

The steering was fitted with a drive dog which allowed us to quickly disconnect the steering servo and allowed me to drive the 1600 as a normal car. The transmitter was fitted with a steering wheel which gave me seven turns lock to lock. (See photo which is a clipping from a 1971 Sydney newspaper). We showed that car in a wide variety of locations and the interest it aroused was amazing. My favourite trick was to drive it from the rear seat with no one in the front seats.

Anyway to cut to the chase when it came time to film the actual commercial we went out to a country location with a long straight road. The camera was mounted on a tripod which was in turn mounted in a mini Moke car. It was arranged for me to sit on the spare wheel with TX in hand and steer the car during filming. (No seat belts in those days) We made several dummy runs to get me used to everything and then it came time for the real thing.

The script called for the Moke to cruise at 60kph and the 1600 to start 400 meters behind the Moke and accelerate up to the Moke, put on the blinkers move out and overtake the Moke, move back and to disappear off into the distance. The camera was to zoom in on the steering wheel which of course had nobody behind it as the 1600 sailed past. All very sexy!

When it came time for the actual filming run the Director called me over and asked me to come in quicker after I had past the Moke to add a little tightness to the scene.  Apparently I was a little too casual coming back in on the test runs.

So off we went, Moke and VW following speeding up to 60kph, speed up the VW, blinker on, move out, overtake, blinker on and move back into the correct lane; beautifully executed overtaking manoeuver. What the Director forgot to do was tell the Moke driver that I was coming in a bit sooner than in the test runs.

Apparently I moved in a little bit too close for the drivers liking and he put his foot on the brake. I went flying off the spare wheel, dropping the TX as I did so. While I was scrambling around looking for the TX I took my eye off the VW. When I found the TX and looked up the VW had left the road and was doing battle with a barbed wire fence along the road side.
I picked up the TX and stopped the VW which was sliding along the fence and turned off the engine.  (To be continued)