Home Forums Everything about everything else Dronin on Rcexplorer F3FC integrated board

Viewing 15 posts - 16 through 30 (of 82 total)
  • Author
    Posts
  • #35892
    krkljan
    Participant

    I will try flashing in a fee days. Could you confirm that board will not burn if I do it.

    #35896
    jihlein
    Participant

    It won’t burn out the board.

    But I’d wait. I figured out how to build Triflight, and that code works, and it uses the MPU interrupt. There’s something wrong with the F3FC Dronin target, but I haven’t found the issue yet. I’ll update this when I’ve fixed it.

    #35898
    krkljan
    Participant

    Waiting until further notice! 😉

    #35939
    jihlein
    Participant

    Well I can only conclude that there is something wrong with the board I have, as I’ve looked at it from every angle I know and can’t make the Dronin code run without an MPU error. As I said, it used to work and we did get some flights on it.

    This doesn’t entirely make sense to me since Triflight runs, and from what I can tell it interfaces to the MPU the same way.

    If the opportunity presents itself, I’ll try this on another F3FC board.

    #35947
    LitterBug
    Participant

    Will this version work with the standalone F3FC? I could give it a test on my Baby Tricopter if you think so.

    Cheers!
    LitterBug

    #35957
    jihlein
    Participant

    As far as I know the two boards are electrically identical, so it should work. I’m looking into a potential problem with the SPI clock setup, might have a solution there, hope to test it later tonight.

    I did find a small unrelated issue in the GCS software for the F3FC target, so at any rate I’ll post a new link to the updated installer package either tonight or tomorrow.

    Thanks!

    #35984
    jihlein
    Participant

    I won’t bore you with the ugly details, but suffice it to say that the F3FC with Dronin is sitting in front of me running fine. The gyro is responding correctly, and I checked each PWM output (all motors and servo) with a logic analyzer. Pulse widths and periods look fine, matching what is selected in the GCS. I don’t have any spare receivers to bench test with, but none of the updates involved the receiver code. Should be good to go. The installer for this version is at:

    https://1drv.ms/u/s!Am7KDquQANJl5jxFnTO5aaadFOSA

    Delete any other installers you may have downloaded.

    #35985
    LitterBug
    Participant

    Cool beans. Will load it up and try to get an autotune this weekend. If that goes well, I have a couple indoor sessions next week and should be able to give it a full go.

    Cheers!
    LitterBug

    #35986
    jihlein
    Participant

    Litterbug, just so you know, this is the branch with the Triflight algorithms. A few notes are in order. When auto tuning, make sure the dynamic yaw pids are set to one, it confuses autotune otherwise. Also, I’ve had better results not applying the yaw autotune values and staying with the defaults. Out of three copters, only one behaves well with the autotuned yaw. Curious to see how it behaves for you.

    #35987
    LitterBug
    Participant

    Downloaded it and flashed the .hex with cleanflight configurator. Shows up in GCS connecions: as USB: F3FC but get “NO LINK”.

    Cheers!
    LitterBug

    #35989
    jihlein
    Participant

    Shut down GCS, unplug board, then restart. I see that a lot too. I think windows gets “lost”.

    #35990
    LitterBug
    Participant

    I’ve tried all sorts of combinations.
    Plug F3FC in, start GCS
    Start GCS, plug F3FC in
    Rebooting windows… ETC…

    Here’s a log from plugging in after GCS starts:

    22:46:15[debug] Adding  1155 30016 1 "36003D000957335436353320+BL" "F3FC" "RcExplorer"
    22:46:15[debug] usbmonitor detection cycle complete.
    22:46:15[debug] "EnterDFU:64 bytes sent"
    22:46:15[debug] "StatusRequest:64 bytes sent"
    22:46:15[debug] "StatusRequest:64 bytes received"
    22:46:15[debug] "Status:0"
    22:46:15[debug] FINDDEVICES BEGIN
    22:46:15[debug] "FINDDEVICES SENDING CAPABILITIES REQUEST BUFFER_SIZE:64"
    22:46:15[debug] "FINDDEVICES CAPABILITIES REQUEST BYTES_SENT:64"
    22:46:15[debug] "FINDDEVICES CAPABILITIES ANSWER BYTES_RECEIVED:64"
    22:46:15[debug] "Device ID=38401"
    22:46:15[debug] "Device SizeOfCode=212892"
    22:46:15[debug] "Device SizeOfDesc=100"
    22:46:15[debug] "BL Version=131"
    22:46:15[debug] "FW CRC=2780559741"
    22:46:15[debug] "Partition 0 Size 212892"
    22:46:15[debug] "Partition 1 Size 100"
    22:46:15[debug] "Partition 2 Size 16384"
    22:46:15[debug] "Partition 3 Size 16384"
    22:46:15[debug] "Partition 4 Size 16384"
    22:46:15[debug] "Partition 5 Size 0"
    22:46:15[debug] "Partition 6 Size 0"
    22:46:15[debug] "Partition 7 Size 0"
    22:46:15[debug] "Partition 8 Size 0"
    22:46:15[debug] "Partition 9 Size 0"
    22:46:15[debug] "EnterDFU:64 bytes sent"
    22:46:15[debug] "Downloading description partition..."
    22:46:15[debug] "StartDownload 2 Last Packet Size 11 Bytes sent 64"
    22:46:15[debug] "StatusRequest:64 bytes sent"
    22:46:15[debug] "StatusRequest:64 bytes received"
    22:46:15[debug] "Status:0"
    22:46:15[debug] "Download operation completed-- 100 bytes"
    22:46:15[debug] Removing  1155 30016 1 "36003D000957335436353320+BL" "F3FC" "RcExplorer"
    22:46:15[debug] usbmonitor detection cycle complete.
    22:46:15[debug] "Bootloader disconnection detected"
    22:46:16[debug] Adding  1155 30016 2 "36003D000957335436353320+FW" "F3FC" "RcExplorer"
    22:46:16[debug] usbmonitor detection cycle complete.
    22:46:16[debug] Automatically opening device
    22:46:16[debug] ConnectionManager::devChanged autoconnected USB device

    Cheers!
    LitterBug

    #35991
    jihlein
    Participant

    What happens if you go to firmware, hit rescue, then plug in the board? Is it recognized as the F3FC?

    If it is, right click on the settings papartition and select erase. Then press boot and see if it connects.

    #35993
    LitterBug
    Participant

    Firmware –> Rescue recognizes it, allows me to flash, allows export of config… Just never works with anything else.

    Cheers!
    LitterBug

    EDIT: Erasing settings partition had no effect

    #35994
    jihlein
    Participant

    If the settings are erased, and it still won’t connect, I wonder if a driver did not load properly. I’ll look into what drivers need to be removed to force a reload. That’s the only thing I can think of at the moment. Weird.

Viewing 15 posts - 16 through 30 (of 82 total)
  • You must be logged in to reply to this topic.