You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I built the project from source using the newest available tools (just updated to npm 10.2.3) but the same behavior is repeated with the webcontroller linked on official webpage official webcontroller .
I don't know react or js.
Turns out with a freshly loaded webcontroller the control mode toggles between undefined and angle mode.
The torque mode undefined results in voltage mode as its default.
Is this expected behavior?
The issue starts when torque mode was changed to a different mode.
Both control mode angle and torque mode voltage result in an XXundefined command. The current mode is not highlighted with the buttons. The last selected button stays on and the controller running Arduino-FOC (2.3.1 Driver: 1.0.5) does no longer interpret MTundefined as MCvoltage.
Since this seems Arduino-FOC related, I will create an issue on the other repo referencing this thread. Arduino-FOC bug report
The text was updated successfully, but these errors were encountered:
I built the project from source using the newest available tools (just updated to npm 10.2.3) but the same behavior is repeated with the webcontroller linked on official webpage official webcontroller .
I don't know react or js.
Turns out with a freshly loaded webcontroller the control mode toggles between undefined and angle mode.
![image](https://private-user-images.githubusercontent.com/123752377/280257305-11aec170-1fe9-4192-bb7e-6bf71d99d9f5.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjU3NzU0NDAsIm5iZiI6MTcyNTc3NTE0MCwicGF0aCI6Ii8xMjM3NTIzNzcvMjgwMjU3MzA1LTExYWVjMTcwLTFmZTktNDE5Mi1iYjdlLTZiZjcxZDk5ZDlmNS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwOTA4JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDkwOFQwNTU5MDBaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0yZDkwMWU0ZmI1YTU4ZjQ0ZDdjM2VjODEwZTVlOWE5ZjYxNGRkNmMwNzEzN2QyMjRkYzc4YjE3ZjZkNjU5MDViJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.vVtM--fI7P-7Hipx3DmsQAuIC49YBybjmjM8Cvyu3NQ)
The torque mode undefined results in voltage mode as its default.
![image](https://private-user-images.githubusercontent.com/123752377/280257488-76c49769-edcb-477f-82d8-2f51dc5d8332.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjU3NzU0NDAsIm5iZiI6MTcyNTc3NTE0MCwicGF0aCI6Ii8xMjM3NTIzNzcvMjgwMjU3NDg4LTc2YzQ5NzY5LWVkY2ItNDc3Zi04MmQ4LTJmNTFkYzVkODMzMi5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwOTA4JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDkwOFQwNTU5MDBaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0yYzc1ZTAwNzJkNjRjMTlkMzFkMmM3M2I5ZjM0Y2FlODc1MzY1M2Q0MjNiNTU5NDMyNzdiMmI5MWM3OTdiZDhjJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.k7XvpDrfoXLG132xZj8TsmHpNFLfv8EeX7dc093VQ6E)
Is this expected behavior?
The issue starts when torque mode was changed to a different mode.
Both control mode angle and torque mode voltage result in an XXundefined command. The current mode is not highlighted with the buttons. The last selected button stays on and the controller running Arduino-FOC (2.3.1 Driver: 1.0.5) does no longer interpret MTundefined as MCvoltage.
Since this seems Arduino-FOC related, I will create an issue on the other repo referencing this thread. Arduino-FOC bug report
The text was updated successfully, but these errors were encountered: