Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tachometer stops working after applying brake, when motor was running at high duty. #17

Open
pabloxid opened this issue Apr 9, 2016 · 6 comments

Comments

@pabloxid
Copy link

pabloxid commented Apr 9, 2016

Steps to reproduce this error:

  1. run BLDC tool, select "realtime data" tab, check "activate sampling"
  2. send some kind of "high duty" command to the motor (e.g. duty 0.5, rpm 4000, current 3.0A, etc.)
  3. then press "brake" / "full brake" button (or send duty 0.0)
  4. now move motor shaft by hand
  5. repeat from point 2)

You may notice after repeating this several times, some of them tachometer don't change with manual shaft movement, it remains "frozen" until you quit brake state.

@rewolff
Copy link
Contributor

rewolff commented Apr 16, 2016

It could be that the measuring of the rotor state is difficult when "full brake" is on. So I wouldn't be suprised it it cannot measure the rotor state in that situation. Could it be that you're getting tired after a a few tries so that the induced voltages are less and that the measured voltages end up below the detection threshold?
Why is this a problem for you?

@pabloxid
Copy link
Author

Yeah, I thought this might be the cause, however there are two important points:

  1. failure occurs only sometimes. That is, the system is actually capable to detect the state of the rotor when "full brake".

  2. this shouldn't be a surprise, because in fact I'm using hall sensors. Maybe the problem is that, occasionally the system is put into sensorless mode and "forget" that it has hall sensors (In fact, it switches to sensorless mode at high duty cycles, don't it?).

Why is this important to me? Because I'm using VESC in a positioning system, so the tachometer can help me determine if there was any fault.

@pabloxid
Copy link
Author

Definitely the problem is related to sensored/sensorless switch under "hybrid" mode, which is what I've been using. If I put VESC into full "sensored" mode, tachometer works always.

@pabloxid
Copy link
Author

I think when braking, a call to update_sensor_mode () is missing somewhere in the code. Can anyone confirm this, and tell me where that call should be placed?

Thank you.

@vedderb
Copy link
Owner

vedderb commented Apr 18, 2016

I can have a look at this soon. Sensored mode in the BLDC code has some issues in general and I haven't tested it much, so it needs some improvements. Could you give sensored FOC a try?

@pabloxid
Copy link
Author

I could not get my motor works in FOC mode. Maybe I didn't understand the procedure for adjusting the parameters, but for reasons of time, I needed to finish this project and had already achieved some results in BLDC mode, so I kept in BLDC mode. This issue is for "hybrid" BLDC mode, full "sensored" mode works well.

vedderb added a commit that referenced this issue Oct 18, 2024
f4502208 Bugfix in reader related to gc removing a string that may still be in use.
51bc2cc1 fix bug in recv-to where GC can reclaim patterns
19fd94ea fix broken code in earlier commit
d5b7f65e refactor for readability and cleaning
3a07a746 slight refactor of tok_symbol case in reader for readability and code-complexity improvements
de77d0c5 update test_event_5/6 to work independently of scheduling
3ed2da36 adding a read-eval-prgram while flatten-unflatten stress test
888f7057 running tests after merging changes to how var and let bindings work
ceba045d Merge pull request #16 from laxsjo/fix/var-redefinition
322a1f81 Add tests for new var and let behavior
7a066d14 Set temporary binding to `$placeholder` in var/let
0f90bda6 Make `var` not shadow previous bindings in value eval
ac3e8f16 runnign tests after PR merge + small tweak repl
abdfb198 Merge pull request #17 from laxsjo/refactor/repl-warnings
7b2ffcbd added to flat value stress tests
a47d850a Fix warnings when building repl
0cc8c71d Fix indentation of `eval_var` in eval_cps.c

git-subtree-dir: lispBM/lispBM
git-subtree-split: f450220879ca1d3a718f91fcc092c235fa2cad97
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants