-
-
Notifications
You must be signed in to change notification settings - Fork 406
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: Issues with uploading *.yaml to FluidNC (latest version) #1172
Comments
Added note...the steppers powered on with an green LED and the power led etc. on the root controller was indicating "on", VFD powered as well |
Let's fix the start errors first. I see an error in your config file. For the Huanyang, the uart parameters are not indented under the uart: line. This causes all the uart parameters to issue warnings. Huanyang:
uart:
txd_pin: gpio.17
rxd_pin: gpio.16
rts_pin: gpio.4
baud: 9600
mode: 8N1
modbus_id: 1
tool_num: 0
speed_map: 0=0% 0=25% 6000=25% 24000=100% I suggest using the new style separate uart section as described here. http://wiki.fluidnc.com/en/config/config_spindles#huanyang-vfd-with-rs485 uart1:
txd_pin: gpio.17
rxd_pin: gpio.16
rts_pin: gpio.4
baud: 9600
mode: 8N1
Huanyang:
uart_num: 1
modbus_id: 1
tool_num: 0
speed_map: 0=0% 0=25% 6000=25% 24000=100% |
Thank you very much. Please see my updated file below and I will test ASAP. What about the error I got when trying to upload a new config (ref in picture incl. in my post). It was written as Returned -2 and if it happens again I will not be able to upload the corrected yaml :( Also could this "double enter" become an issue for the config? Corrected yaml: board: Root Controller ISO stepping: axes:
y:
z:
i2so: spi: sdcard: control: coolant: probe: macros: user_outputs: start: uart1: Huanyang: Laser: |
We can't verify your corrected YAML because it was pasted without three-back-tick quotation, so github reformatted it and removed the indentation. Can you edit that post to quote it correctly, or else add a .txt suffix to the yaml filename and attach the file? Re the "Returned -2": It's hard to know exactly what caused that. Reset the machine and retry. Maybe it will work the second time. Extra linefeeds are not a problem. |
The Root Controller people told us here that they offer support via email at [email protected] and Discord at https://discord.gg/93Ue5SwthW |
Thanks...as I'm unsure how to add the three back tics correctly (should it be both in the start and the end of the file) I have renamed the Yaml to a txt file. If possible please have a look if there is something "structually" wrong with the file. and how I have formatted it...most of it is a copy from a config downloaded from the Root Github but maybe I have mad a mess of things in the structure (even if I have not changed much) Please have a look. Thanks :) |
@MitchBradley
|
Yes the quoting is correct. If you select the Preview tab you can see what it looks like before posting. I will look at the file. Typically the startup messages will complain if there is a structural problem, usually with a message about indentation or about some item not being recognized. |
Your yaml loads on my controller without complaint. |
Here are the startup message from your yaml. This is on a midtbot controller that I used for some kinds of testing. The firmware version is essentially 3.7.15 plus a couple of changes that are unrelated to anything we are discussing here. The fact that it is not a Root Controller does not affect the ability to parse the yaml file. It does result in the
|
I compared the attached file with the quoted version and they are identical, thus verifying the quoting correctness. |
Thank you very much Mitch for your support👍😊 Much appreciated.
I will test the config on my machine and report back with my findings/end
result. Thanks!
Den ons 20 mars 2024 23:09Mitch Bradley ***@***.***> skrev:
… I compared the attached file with the quoted version and they are
identical, thus verifying the quoting correctness.
—
Reply to this email directly, view it on GitHub
<#1172 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3INKEPXW4HRB4IWKUIZMGLYZICLDAVCNFSM6AAAAABE7WQ4LWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJQG4ZTCNZUGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Got everything up and working, Both the 2.2.kW spindle and laser is now fully operational and interchangable within the GCode Sender. Thank you @MitchBradley & @bdring for your gr8 assistance and I'm now looking forward on with my journey wit Fluid NC. Appreciate your support on this forum so much! :) 💯 🥇 |
Wiki Search Terms
Root controller, Huanyang VFD, Yaml indentations etc.
Controller Board
Root Controller ISO. The config should be an exact copy when it comes to sections described in the root controller WIKI (base config, axes (common cathode), rs485 etc. etc.)
Machine Description
Gantry milling machine (QueenBee Pro) with dual y steppers (X,Y,Y, Z) and Huanyang VFD and 2.2 kW spindle. Controller is Root Controller ISO
Input Circuits
No response
Configuration file
Startup Messages
User Interface Software
FluidTerm
What happened?
Nothing. No movement or sound of power to steppers etc. The steppers are wired to the controller as common cathode and acc. to wiring instructions on the controller.
No comms with the VFD although I cheked the wiring and parameter settings in FluidNc Wiki....
GCode File
No response
Other Information
No response
The text was updated successfully, but these errors were encountered: