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 Need help for hall effect sensor

Discussion in 'DIY Motion Simulator Building Q&A / FAQ' started by qqqwewqe123, Oct 19, 2025 at 08:31.

Tags:
  1. qqqwewqe123

    qqqwewqe123 New Member

    Joined:
    Mar 20, 2025
    Messages:
    2
    Balance:
    2Coins
    Ratings:
    +0 / 0 / -0
    My Motion Simulator:
    2DOF, 3DOF, DC motor, AC motor, SCN5, SCN6, SimAxe, Arduino, JRK, Joyrider, SimforceGT, Motion platform, 4DOF, 6DOF
    I wanted to build a 2DOF system, but right now I’m having a problem with my Hall effect sensor. In the screenshot taken from SMC3Utils, you can see that when the sensor reaches a certain upper limit, the signal suddenly drops all the way down and never goes back up again — at that point, the motor also stops rotating.
    Because of this, I have to manually realign the motor and the sensor every time. What do you think might be causing this? Could it be an issue with the sensor itself or with the values I’m using?

    Also, the pulley attached to the motor shaft is larger than the small pulley on the sensor, and I didn’t really pay attention to the ratio between them when assembling. Could that also be causing the issue?

    Attached Files:

    qqqwewqe123, Oct 19, 2025 at 08:31
    #1
  2. noorbeast

    noorbeast VR Tassie Devil Staff Member Moderator Race Director

    Joined:
    Jul 13, 2014
    Messages:
    21,783
    Occupation:
    Innovative tech specialist for NGOs
    Location:
    Tasmania, Australia
    Balance:
    152,511Coins
    Ratings:
    +11,081 / 56 / -2
    My Motion Simulator:
    3DOF, DC motor, JRK
    What specific Hall sensor are you using and what is its specs?

    The Hall sensor does not look to be centered in the picture.

    One of the benefits in using Hall sensors is that you can direct drive them, while a mismatched ratio complicates such simplicity.

    I am not sure how you got the values used but it is recommend you follow the steps below: https://www.xsimulator.net/communit...3dof-motor-driver-and-windows-utilities.4957/

    1. Disconnect the motor power supply
    2. Make sure Simtools is not running – we’re not ready for that yet!
    3. Wire up the Arduino (with SMC3 installed) to your H-Bridges and connect to your computer via USB
    4. Run the Windows SMC3 Utility software and make sure it communicates with the Arduino (There is no need to set baud rates, they are not configurable)
    5. Set the Kp, Ki, Kd, PWMmin, PWMmax, PWMrev to 0 for ALL motors (This will make sure the motors don’t move)
    6. Set Clip to 255 (you need to do this first) and Limit to 255 (This will give you plenty of margin if something goes wrong while setting up)
    7. Turn on the power to your motors – nothing should move at this stage!
    8. Set Kp to about 400
    9. Now slowly, increase PWMmax… at some point the motor should start to move. When it does check the “Green” feedback line is moving toward the “Blue” target position.
      • If it is then that motor and feedback is wired correctly - proceed to test other motors.
      • If it is moving away turn off motor power immediately (or quickly reduce PWMmax again). In this case you need to either reverse the wires to the motor being tested –OR– reverse the +5V and GND wires to your feedback pot for the motor being tested (do not do both). Restart the test from the beginning.
    10. Do the above for each motor
    noorbeast, Oct 19, 2025 at 08:58
    #2
  3. qqqwewqe123

    qqqwewqe123 New Member

    Joined:
    Mar 20, 2025
    Messages:
    2
    Balance:
    2Coins
    Ratings:
    +0 / 0 / -0
    My Motion Simulator:
    2DOF, 3DOF, DC motor, AC motor, SCN5, SCN6, SimAxe, Arduino, JRK, Joyrider, SimforceGT, Motion platform, 4DOF, 6DOF
    The sensor I used is pandAuto p3022-v0-cw360, and the values are
    vcc=5vdc, out=0-3.3v, gnd=0v

    Actually, I only shared the screenshot as an example — my real problem is with the sensor.
    Normally, when I move the motor, the motor signal and the sensor signal (the green one) move together.
    However, as shown in the screenshot I sent, when the green line reaches a certain upper area, it suddenly drops all the way down and turns the motor off.
    To make the motor work again, I have to manually realign it by hand.
    I don’t understand why this issue is happening — could it be caused by the gears?
    Last edited: Oct 19, 2025 at 09:49
    qqqwewqe123, Oct 19, 2025 at 09:16
    #3
  4. Joe Cortexian

    Joe Cortexian Active Member Gold Contributor

    Joined:
    Sep 8, 2021
    Messages:
    215
    Balance:
    1,285Coins
    Ratings:
    +53 / 0 / -0
    My Motion Simulator:
    3DOF
    First when the encoder/sensor is out of range the motors will turn off in SMC3. I suspect yours is sending 0 which is less that the Min.

    I suspect that your 3.3v sensor going into a 5v A/D is the problem. When the sensor gets to 3.3v it will go back to zero. The software assumes the range is 0-1024 but yours will range from o-676 so the midpoint is 338. So when you setup the midpoint it’s 338 not 512. So the software has to be modified in order to work.

    I have been successfully using A5600 sensors for a few years now. There are cheap and effective. A different sensor is another alternative.
    Joe Cortexian, Oct 19, 2025 at 16:20
    #4