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

MKS Odrive 3.6 56V troubleshooting

Discussion in 'DIY Motion Simulator Building Q&A / FAQ' started by lajka88, Jan 22, 2023.

  1. lajka88

    lajka88 New Member

    Joined:
    Oct 4, 2022
    Messages:
    1
    Balance:
    10Coins
    Ratings:
    +0 / 0 / -0
    My Motion Simulator:
    Arduino
    Hi all folks,

    this is my first post, just about the problem I encountered now but soon I will start my thread on building a 6dof / bldc sim. So far, however, I've run into a problem. I bought an Makerbase odrive v3.6 56v clone from aliexpress, after connecting the motors, the original fw worked, because the motor shaft rotated 1 turn as it should. I decided to use the Stijns guide

    Practically all steps went well, including fw upload, later I had a problem with installing Python on an Ubuntu virtual machine (most likely) because permission denied was popping up while trying to connect board. I used Windows and I was able to connect to the board, but instead of odrv0 the device is named as dev0, then I assume a problem because when turned on the axis does not rotate and immediately after connecting a message pops up. that the board is not genuine and some of the options will be unavailable. Has anyone of you encountered this before and knows how to restore the previous fw or one that allows the correct reading of the encoder by FlyptMover?

    Big thanks for inspiring work to Silentchill and Stijns and any other user on the forum that i learining from.
  2. Gitaaa

    Gitaaa New Member

    Joined:
    Apr 14, 2023
    Messages:
    1
    Balance:
    19Coins
    Ratings:
    +0 / 0 / -0
    My Motion Simulator:
    6DOF
    Hi, I am facing a similar issue, did you managed to resolve it? I have found the makerbase FW here: https://github.com/makerbase-mks/ODrive-MKS/tree/main/02_Makerbase ODrive related documents.

    I managed to flash the custom FW build based on Stinjs guide and I succesfully set up and calibrated the motors and all works without any load, but as soon as I connect it to the platform it reboots after even a little slow movement (when current exceeds about 15A). This happens all the time even with just one motor moving and there is no errror.

    The platform is empty so it is not even pushing as much weight as before. I switched to makerbase odrive board as one of the original boards stopped working and I was not able to get an original one anywhere.