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
{{ message }}
This repository was archived by the owner on Jul 16, 2023. It is now read-only.
When trying to modify the motor settings (for instance, trying to configure a dual Y motor setup) in the TinyG configuration panel, changes are not made nor do edits persist when the panel is reopened. At this point, motor outputs cannot be assigned to correct axes nor can their characteristics be modified to calibrate the machine.
The text was updated successfully, but these errors were encountered:
Hello,
Thank you for your feedback.
Goko doesn't persist TinyG configuration. It uses the connected TinyG controller and request for its configuration.
Few things to check :
Is your TinyG board powered and connected ?
Are you able to talk to your TinyG ? (you can enable the serial console view and see if TinyG talks back)
When applying your settings, do you see any outgoing data in the Serial console view ?
You may have to enable the console view before doing anything to see the logged serial data.
Here's what I can verify:
TinyG is powered and connected. Requests to motors are processed and motors rotate.
TinyG communicates.
After configuring motors to proper axes (i.e. Motor 1 - X, Motors 2 & 3 - Y, Motor 4 - Z) and pressing OK, there is no data appearing in the Serial console view. I taking this to mean that no configuration information is being sent along to the TinyG.
Let me know if you need additional information. Thanks for quick response to issue posting!
When trying to modify the motor settings (for instance, trying to configure a dual Y motor setup) in the TinyG configuration panel, changes are not made nor do edits persist when the panel is reopened. At this point, motor outputs cannot be assigned to correct axes nor can their characteristics be modified to calibrate the machine.
The text was updated successfully, but these errors were encountered: