Hello sir, I'm new to this and after I downloaded and unzip the dif util file I went to the x64 folder and double clicked on the dif_util but nothing happened. I'm running win10 64bit. May I ask what am I doing wrong? Thank you sir
@@andypiper5285 Thank you so much for answering sir. I were able to use a different method and got the bootloader loaded on the flight controller successfully. However, when I plug in the flight controller, the flight controller first showed up COM6 labled ardupilot but then it changes to COM 7 and 8 labled as Mavlink and SLCAN, I can only connect to COM7 when I do that followed you to the setup screen it say that I cannot load firmware, I have to disconnect and connect to firmware screen. But everytime I unplugged and pluged backed in the flight controller it showed COM6 then switched to display COM 7 and 8. I have the exact flight controller that you have. THank you for your time and I hope to hear back from you
@@andypiper5285 Hello sir, I actually went back and erase the FC and followed your step from the beginning and successfully uploaded your bin file to the FC. Now when I connect to my PC COM6 does show as ardupilot. However, when I go to the mission planner it showed com 6 but when I connect it just say "Try to connect time out in 27 second" and counting down. I've tried different usb port and cables but producing the same result. May I ask if I need to do something else sir? THank you for your time.
Hello sir, Sorry for bothering you. I think I got it working :). I went and just flashed the actual boot loader hex from quadcopter and after flash that's when the usb showed up as ardupilot without any COM number in the device manager, then when I go on the mission planner, com 7 and 8 showed up like the first time. I clicked on com 7 and it connected. I now realized I can skip the step regarding the firmware loading because I already loaded during the flashing dfu procedure. Now I'm just following you after that step. Thank you again for sharing your knowledge.
@@bohaman. Yes its important to reason that on some flight controllers (including this one) the COM port used by the bootloader is different the one used by the actual firmware. This is why the port changes. When you have two ports that usually means the firmware is running - one is the regular com port and the other is for a CAN connection
Thanks for sharing this series of videos!!
Glad you like them!
good stuff!
Hello sir, I'm new to this and after I downloaded and unzip the dif util file I went to the x64 folder and double clicked on the dif_util but nothing happened. I'm running win10 64bit. May I ask what am I doing wrong? Thank you sir
Hi, if you are using dfu you need to use it from the command line - so open up a powershell or bash window and run dfu from there
@@andypiper5285 Thank you so much for answering sir. I were able to use a different method and got the bootloader loaded on the flight controller successfully. However, when I plug in the flight controller, the flight controller first showed up COM6 labled ardupilot but then it changes to COM 7 and 8 labled as Mavlink and SLCAN, I can only connect to COM7 when I do that followed you to the setup screen it say that I cannot load firmware, I have to disconnect and connect to firmware screen. But everytime I unplugged and pluged backed in the flight controller it showed COM6 then switched to display COM 7 and 8. I have the exact flight controller that you have. THank you for your time and I hope to hear back from you
@@andypiper5285 Hello sir, I actually went back and erase the FC and followed your step from the beginning and successfully uploaded your bin file to the FC. Now when I connect to my PC COM6 does show as ardupilot. However, when I go to the mission planner it showed com 6 but when I connect it just say "Try to connect time out in 27 second" and counting down. I've tried different usb port and cables but producing the same result. May I ask if I need to do something else sir? THank you for your time.
Hello sir, Sorry for bothering you. I think I got it working :). I went and just flashed the actual boot loader hex from quadcopter and after flash that's when the usb showed up as ardupilot without any COM number in the device manager, then when I go on the mission planner, com 7 and 8 showed up like the first time. I clicked on com 7 and it connected. I now realized I can skip the step regarding the firmware loading because I already loaded during the flashing dfu procedure. Now I'm just following you after that step. Thank you again for sharing your knowledge.
@@bohaman. Yes its important to reason that on some flight controllers (including this one) the COM port used by the bootloader is different the one used by the actual firmware. This is why the port changes. When you have two ports that usually means the firmware is running - one is the regular com port and the other is for a CAN connection
no info after downloading the 2 files.