Hello guest, if you read this it means you are not registered. Click here to register in a few simple steps, you will enjoy all features of our Forum.
This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 3 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Heavy Lifters
Ok, here we go.

Sirius Air 3 Hero SPi-F3 FC re-installed.

I have 4 different configurator programs installed on my computer.

Betaflight, Baseflight, iNAV and Cleanflight. When last used all 4 were working perfectly.

Today Betaflight loads correctly but will not connect to the FC. Correct CP210x drivers are installed and the Port number (7) is correct. Or at least I think that is the correct driver.

Baseflight, iNAV and Cleanflight begin to load and stall halfway into the load and will progress no further.

I think I am about to scream.   Angry

I am also beginning to think there is something seriously wrong with my computer.

Next step is to uninstall and re-install the configurator programs.

Anyone got any other ideas?

KK
Reply
Login to remove this ad | Register Here
I am also beginning to think I have forgotten everything that I knew about the Hero system. Particularly the drivers.   Cry

Which is the correct driver may I ask?

KK
Reply
Howdy Boys,

I re-installed all four configurators and all worked perfectly after downloading.

When I went to reopen them all four refused to open.

So I am afraid I need some serious help. I have absolutely no idea what is going on.

KK
Reply
Howdy Boys,


Still no progress since the last posting.

I am now beginning to wonder if this failure to load is associated with why my DJI Naza could not connect with the Assisstant.

Monday morning first thing I am off to the computer doctor with laptop under arm for a full check up.

This is all very suspicious.   Cry

Next week should tell the story.

KK
[-] The following 1 user Likes Keyboard Kid's post:
  • sloscotty
Reply
OK here I am on a new second hand Laptop and I have installed three configurators, Betaflight Cleanflight and iNAV.

Out of 12 test loads Betaflight failed to load once and the others loaded every time. I am beginning to wonder if the version of Windows 10 is having an effect.

Until just recently all four configurators never failed to load on my old Laptop. Now on my old Laptop they do not load at all.

I will be curious to see if I can connect to a configurator using this computer.

Stay tuned.   Wink

KK
Reply
   
Finally connected my new laptop to Wooden It now fitted with the Hero.

There appears to be no problem with the configurators loading but I still cannot connect the hero to the config.


The attached photo shows the correct driver is installed and the config is auto detecting the correct port.

The Port opens successfully and after 10 secs closes successfully but no actual connection to the Hero.

All three configurators do the same thing so once again I am afraid that I am at a loss.

I will just keep grinding on until something gives.

Either me or this wretched system   Angry 

KK
Reply
Position to date.

After a full day of trying everything I know all 4 configurators are now loading correctly on both computers.

All open successfully and after 10 seconds close successfully but still no comms on either machine.

I have tried everything I know centering on those drivers to no avail.

I assume it is a driver problem.

Any clues out there in the Quadosphere?   Cry


KK
Reply
Ok, you have all been very patient while I have been struggling with the Hero so I am proud of you all. Here then is what you have all been waiting for……the juicy bits on the Opera House job.

By now you should have all read the story in the previous postings and there is absolutely no inkling of juicy bits in that lot. That was all written long before I graduated as a story teller. It was pretty dry stuff I must admit.

So let me correct that perception with the following.

You all saw in that story the difficulties that the designer of the robot had with traction on that sloping glass roof covered in soapy water. Well the same thing applied to us poor humans. Slippery wet soap covered glass canted at 15 degrees from horizontal made for a very precarious perch and this was long before Occupational Health and Safety came on the scene.

What did that mean? Simply that we all wore no safety harness. When I think back on that now I shudder actually but I am getting ahead of the story.

We were all given little chamois bootties to slip over our shoes which certainly provided a reasonable grip on the glass and did make us feel much safer. However it was the awe inspiring view that tended to overwhelm once you walked out onto that glass roof.

Surrounded by towering buildings, the glittering harbour view and dominated by the Sydney harbour Bridge it was indeed an overpowering experience. Especially to someone who spent much of his life locked in a dogbox working on microscopic components.

Anyway the day in question was one of the final inspection days where we had to demonstrate the finished robot under operational conditions.

What was not highlighted in the ETI articles was the cleaning brush roller was on a drop-arm which automatically cut off air to the forward drive, leaving only the reverse drive in action. This feature was included to allow the robot to drive right the edge of the glass roof at which point the brush dropped and stopped the robot until the reverse command was given; all very neat in theory.

Come the time to demonstrate this feature things did not quite go to plan. The driver may have approached the edge a little too quickly or something and when the drop arm fell off the edge there was a slight delay in cutting off the air and the robot ended up sitting right on the edge, teetering backwards and forwards, rocking as gently as a baby in the breeze.

The apprentice that was with us was a quick thinking lad and he immediately grabbed the air and water hoses and kinked them hard, shutting off all air and water to the robot. We all stood around patting him on the back saying well done lad but our hearts were still in our mouths because the robot was in such a precarious position.

Now I cannot remember the exact details of the debate that followed but it was decided that we would try to drive the robot back from the edge as called for in the plan and this called for the apprentice to release the hoses in order to restore power to the reverse drive.

The moment he did this the force of the air and water hitting the robot pushed it hard forward and thus the poor little thing jumped right over the edge which was some 50 meters or so above the walkway below.

That poor apprentice was still hanging onto the hoses at the time and he went flying forward and ended up sprawled on his stomach halfway down the roof but still hanging desperately onto those hoses for dear life. Luckily there was only about 15 meters of spare hose so when we made our way ever so carefully to the edge and looked over, there was the robot suspended by two quick disconnect hose fittings swinging gently in the breeze, 15 meters below us. It was a sight that I will never forget.

We had to haul the robot up hand over hand standing right on the edge of that roof. It really was a frightening experience. Still all ended well and we took the robot back to the factory for mods to the drop-arm switch.

The final test a week or so later cleared the robot for operation and we all let out a major sigh of relief. I had no desire to scamper around that roof any more than I had to.


Still it was all good clean fun ……… if you will pardon the pun.   Big Grin
[-] The following 4 users Like Keyboard Kid's post:
  • Tom BD Bad, RENOV8R, sloscotty, fftunes
Reply
(21-Nov-2017, 02:13 AM)Keyboard Kid Wrote: Finally connected my new laptop to Wooden It now fitted with the Hero.

There appears to be no problem with the configurators loading but I still cannot connect the hero to the config.


The attached photo shows the correct driver is installed and the config is auto detecting the correct port.

The Port opens successfully and after 10 secs closes successfully but no actual connection to the Hero.

All three configurators do the same thing so once again I am afraid that I am at a loss.

I will just keep grinding on until something gives.

Either me or this wretched system   Angry 

KK
It's just as frustrating for us as it is for you to see you struggle with this, I wish we could track it down to a simple solution.  I'm sure it won't have any affect, but I would disable the com port auto-connect feature.
[-] The following 1 user Likes RENOV8R's post:
  • Keyboard Kid
Reply
(21-Nov-2017, 02:38 PM)RENOV8R Wrote: It's just as frustrating for us as it is for you to see you struggle with this, I wish we could track it down to a simple solution.  I'm sure it won't have any affect, but I would disable the com port auto-connect feature.

Thanks Reno, I really appreciate all of the support you fellows have given me over the time this thread has been running.

In one way I just feel plain embarrassed that I am having such a hard time with this quad section of my project.

I have dealt with some big, difficult projects in the past but nothing as frustrating as this one. Even my early days on autonomous flight were not as frustrating as this and they were difficult enough.

I just cannot understand why it is all so hard. Some of the problems are just plain stupid. Why would the configurator programs (all four of them) stop loading half way through the load only to resume loading successfully two weeks later a couple of days after I had purchased a new computer to get around that problem? And the new computer was no better so now I have 8 configurator programs that load successfully but do not connect to the Hero. Some progress!

It really is weird stuff and the really sad part is that I have no friends left in Sydney that I can call on to help me out. My nearest helpmate is 300km away down in Wagga and I am not sure that even he could help with this problem.

So I will keep grinding on. Something must give sooner or later.   Dodgy 

KK
Reply
I don't know about the dji app, but the rest are all chrome apps... Maybe a windows or chrome update or something messed things up?
[-] The following 1 user Likes fftunes's post:
  • Keyboard Kid
Reply
(23-Nov-2017, 12:59 AM)fftunes Wrote: I don't know about the dji app, but the rest are all chrome apps... Maybe a windows or chrome update or something messed things up?

Thanks FF. I am now using two Laptops both with Chrome and the latest Chrome download.

The curious thing is that all 8 configurators (4 on each machine) recognise the port, successfully  open the port and then 10 seconds later successfully close the port.

I have tried downloading the drivers multiple times and it would appear that I have the correct driver mounted but looking at videos on the web I am just not sure I have the correct driver for Windows 10. 

I am just finding the whole thing extremely frustrating. I have spent days now with no luck what so ever.

I have attached a photo (in a previous post above) of the Betaflight and Device manager which I think shows the correct driver installed but I do have some doubt that this driver may be an XP/Vista version not the Windows 10 version.

I downoaded and istalled Impulse Driver fixer and it just sits there searching for the FC and apparently cannot find it.

I find it all so weird and I still have not found out why the DJI just suddenly stopped communicating with the Assisstant.

One day I hope all will become clear.

KK
Reply
(22-Nov-2017, 12:03 AM)Keyboard Kid Wrote: Why would the configurator programs (all four of them) stop loading half way through the load only to resume loading successfully two weeks later a couple of days after I had purchased a new computer to get around that problem? 

This is solely down to the 'Law of Sod'  Rolleyes

The only thing I can think of to suggest is to remove and reinstall the driver packs, but i'm sure that you have done that a million times already. I doubt it will make you feel any better, but I had issues when I 1st tried to use betaflight with my new (actually downgrade from my busted desktop) laptop took me 2 days of sending the laptop to sleep before I realized that I needed to restart the bloody thing, to get the drivers to work  Doh
Windless fields and smokeless builds
[-] The following 1 user Likes Tom BD Bad's post:
  • Keyboard Kid
Reply
Right now i can only think of "bad USB cable" but i'm sure you tried a bunch... Sad
[-] The following 1 user Likes fftunes's post:
  • Keyboard Kid
Reply
Check your google chrome settings (chrome://settings).
Under "Advanced", check "Content settings".  If you have several things that are disabled or "not allowed", try "allowing" each one (or all) to see if that solves anything. (In particular, allow Javascript and Popups - but I'd try them all.)
[-] The following 1 user Likes sloscotty's post:
  • Keyboard Kid
Reply



Login to remove this ad | Register Here