Welcome to 3DRPilots.com

Sign up and join the largest 3D Robotics drone community!

BAD LOGGING error in Mission Planner when connected to download logs.....

Discussion in 'General Discussion' started by carloliveira, May 25, 2018.

  1. carloliveira

    Joined:
    Jul 15, 2017
    Messages:
    52
    Likes Received:
    13
    Location:
    Denville, NJ
    curios to see what everyone's parameters are set to on 3.5.4 firmware for the LOGGING parameters it appears one of the parameters may be triggering a BAD LOGGING error when I connect to SOLO to download logs. Other forums I have searched showed users switching out the SDCARD but I believe that's not the issue here.....More parameter based Im assuming....
     
  2. carloliveira

    Joined:
    Jul 15, 2017
    Messages:
    52
    Likes Received:
    13
    Location:
    Denville, NJ
    Figured it out just change parameter LOG_BITMASK to 131071
     
  3. XevetS

    Joined:
    Dec 29, 2016
    Messages:
    1,032
    Likes Received:
    328
    Location:
    Somewhere in the Beautiful Nature Coast of Florida
    Isn't that is what it should be set at? That was fixed in RC_8
     
    #3 XevetS, May 28, 2018
    Last edited: May 28, 2018
  4. carloliveira

    Joined:
    Jul 15, 2017
    Messages:
    52
    Likes Received:
    13
    Location:
    Denville, NJ
    After i uploaded firmware 3.5.4 to 5v mod cube it was set wrong on its own just like some of my gps settings....so i just corrected it, i downloaded the 3.5.4 firmware from github site so im wondering if others are experienced the same nonsense
     
  5. XevetS

    Joined:
    Dec 29, 2016
    Messages:
    1,032
    Likes Received:
    328
    Location:
    Somewhere in the Beautiful Nature Coast of Florida
    I see that looking at the RC_8 param file it is set for LOG_BITMASK to 131070 very weird "thats the stock solo cube param setup" I need to check my green cube setup and see what its set to...Thanks for pointing that out man...