1. Do not share user accounts! Any account that is shared by another person will be blocked and closed. This means: we will close not only the account that is shared, but also the main account of the user who uses another person's account. We have the ability to detect account sharing, so please do not try to cheat the system. This action will take place on 04/18/2023. Read all forum rules.
    Dismiss Notice
  2. For downloading SimTools plugins you need a Download Package. Get it with virtual coins that you receive for forum activity or Buy Download Package - We have a zero Spam tolerance so read our forum rules first.

    Buy Now a Download Plan!
  3. Do not try to cheat our system and do not post an unnecessary amount of useless posts only to earn credits here. We have a zero spam tolerance policy and this will cause a ban of your user account. Otherwise we wish you a pleasant stay here! Read the forum rules
  4. We have a few rules which you need to read and accept before posting anything here! Following these rules will keep the forum clean and your stay pleasant. Do not follow these rules can lead to permanent exclusion from this website: Read the forum rules.
    Are you a company? Read our company rules
Shared accounts will be removed Plugin Downloads Zero spam policy Forum Rules

ODESC V4.2 question

Discussion in 'DIY Motion Simulator Building Q&A / FAQ' started by Grunch, Mar 25, 2024.

Tags:
  1. Grunch

    Grunch New Member

    Joined:
    Mar 25, 2024
    Messages:
    2
    Balance:
    22Coins
    Ratings:
    +0 / 0 / -0
    Hi, I have an ODESC V4.2, I was able to flash the device via cube programmer but I want to go back to using it as a BLDC controller, I tried loading the ODrive software from the ODrive website but it doesn't work as the device no longer shows up under /dev/

    Suggestions? There doesn't appear to be any place I can get the ODESC firmware which is bizarre.
    Grunch, Mar 25, 2024
    #1
  2. Grunch

    Grunch New Member

    Joined:
    Mar 25, 2024
    Messages:
    2
    Balance:
    22Coins
    Ratings:
    +0 / 0 / -0
    Gah, I was using the memory editor and not the programmer in the MXCube software, was able to load the correct odrive firmware over USB. Now I get an annoying message about the device not being authentic when I startup odrivetool since it checks a hash attribute but I searched the github repo and it doesn't appear they poison the source code, I'm just assuming the provided firmware is the same though I suppose I could always compile from source.
    Grunch, Mar 25, 2024
    #2