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
Problem: Problem getting the configuration in Openbuilds Control v1.0.364 #858
Comments
Something is requesting status during the reading of the config. Status is an immediate command. Those commands have the highest priority in the system. We do not want to block them. |
Thanks @bdring added a note to disable query loop during config dump OpenBuilds/OpenBuilds-CONTROL#283 (comment) We still have a bunch of todo's in OpenBuilds/OpenBuilds-CONTROL#283 (If you look it over and see any of our plans being the wrong thing / wrong way to do it - happy to hear about it! ) - trying to support FluidNC with the minimum of additional work (hehe) so basically need to parse the config to get some values we used to get out of grbl/grblHAL's $$, and then a new config editor to upload yaml (xmodem - love it) and then our machine profiles to be converted to yaml (planning to build the yaml on the fly off our existing grbl profiles) |
FYI, FluidNC has a new feature that can help with status reporting. http://wiki.fluidnc.com/en/support/interface/automatic_reporting . A sender can turn on auto-reporting and then will not need to issue explicit ? queries - nor $G's. |
Thanks - in time we may tweak CONTROL to cater to firmware-specific features, at the moment lack of time means the more we can reuse all the code we already did for grbl, the better - grblHAL slot in nicely there with minimal effort (: |
Controller Board
MKS TinyBee
Machine Description
Not linked with the machine
Input Circuits
No response
Configuration file
Startup Messages
User Interface Software
OpenBuilds Control
What happened?
When you go on the Grbl Settings Tab or FluidNC Settings tab, the displayed information is interrupted by <Idle...> messages, rending the configuration incorrect:
axes:
shared_stepper_disable_pin: NO_PIN
shared_stepper_reset_pin: NO_PIN
x:
steps_per_mm: 160.000000
max_rate_mm_per_min: 8000.000000
acceleration_mm_per_sec2: 80.000000
max_travel_mm: 810.000000
soft_limits: true
homing:
cycle: 2
allow_single_axis: true
positive_direction: false
mpos_mm: 0.000000
feed_mm_per_min: 300.000000
seek_mm_per_min: 1500.000000
settle_ms: 500
seek_scaler: 1.100000
feed_scaler: 1.100000
motor0:
limit_neg_pin: gpio.33:pd
limit_pos_pin: NO_PIN
limit_all_pin: NO_PIN
hard_limits: true
pulloff_mm: 4.000000
stepstick:
step_pin: I2SO.1
direction_pin: I2SO.2
disable_pin: I2SO.0
ms1_pin: NO_PIN
ms2_pin: NO_PIN
ms3_pin: NO_PIN
reset_pin: NO_PIN
motor1:
limit_neg_pin: NO_PIN
limit_pos_pin: NO_PIN
limit_all_pin: NO_PIN
hard_limits: true
pulloff_mm: 4.000000
stepstick:
step_pin: I2SO.10
direction_pin: I2SO.11
disable_pin: I2SO.9
ms1_pin: NO_PIN
<Idle|MPos:20.000,0.000,0.000|FS:0,0>
ms2_pin: NO_PIN
ms3_pin: NO_PIN
reset_pin: NO_PIN
Other Information
No idea how to fix this...
The text was updated successfully, but these errors were encountered: