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

Question [DIY arduino 2DOF] Issue: SimTools deadzone between 0 and -25

Discussion in 'DIY Motion Simulator Projects' started by pog0, Aug 25, 2020.

Tags:
  1. pog0

    pog0 New Member

    Joined:
    Oct 29, 2019
    Messages:
    8
    Occupation:
    student
    Location:
    somewhere in Europe
    Balance:
    - 17Coins
    Ratings:
    +2 / 0 / -0
    My Motion Simulator:
    2DOF, DC motor, Arduino
    Hello! Hope everyone's alright :)
    I'll be super quick.
    After a longish break from the sim I reinstalled everything and am presented with the current issue:

    - SMC3 control works flawlessly, meaning manual control from -limit to +limit is smooth.
    - Axis assignments are the same as they were before the reinstall. (regular [A<Axis1a>][B<Axis2a....)
    - GameEngine output testing does work BUT...

    - When output testing, both Axis1a and Axis2a don't respond to input from the values of -1 to -25.
    Beyond -25 the motor jumps to the correct position, while if i drag the slider above -25 it doesn't jump back until it hits +1. The rest of the range works with no problem.

    - If i limit the axis to 50% from within "Axis limiting", the deadzone increases from {0,-25} to {0,-50}, if i limit the axis to 25% the deadzone goes all the way from 0 to -100.

    What do i do? The arduino is working fine since SMC can control it with no issue.

    Thanks a lot!

    P

    Attached Files:

    pog0, Aug 25, 2020
    #1
  2. pog0

    pog0 New Member

    Joined:
    Oct 29, 2019
    Messages:
    8
    Occupation:
    student
    Location:
    somewhere in Europe
    Balance:
    - 17Coins
    Ratings:
    +2 / 0 / -0
    My Motion Simulator:
    2DOF, DC motor, Arduino
    P.S.: Windows locale has already been set to US english, so I doubt that's what's causing the issue.
    pog0, Aug 25, 2020
    #2
  3. noorbeast

    noorbeast VR Tassie Devil Staff Member Moderator Race Director

    Joined:
    Jul 13, 2014
    Messages:
    21,030
    Occupation:
    Innovative tech specialist for NGOs
    Location:
    St Helens, Tasmania, Australia
    Balance:
    147,878Coins
    Ratings:
    +10,880 / 54 / -2
    My Motion Simulator:
    3DOF, DC motor, JRK
    noorbeast, Aug 26, 2020
    #3
  4. pog0

    pog0 New Member

    Joined:
    Oct 29, 2019
    Messages:
    8
    Occupation:
    student
    Location:
    somewhere in Europe
    Balance:
    - 17Coins
    Ratings:
    +2 / 0 / -0
    My Motion Simulator:
    2DOF, DC motor, Arduino
    pog0, Aug 26, 2020
    #4
  5. pog0

    pog0 New Member

    Joined:
    Oct 29, 2019
    Messages:
    8
    Occupation:
    student
    Location:
    somewhere in Europe
    Balance:
    - 17Coins
    Ratings:
    +2 / 0 / -0
    My Motion Simulator:
    2DOF, DC motor, Arduino
    Update : rolling back to 2.4.0 fixed the issue!
    • Informative Informative x 1
    pog0, Aug 27, 2020
    #5