Open maxoutny opened 1 month ago
The messages indicate that the indentation of the uart1: section is wrong. I don't know how to say it more clearly.
It also appears that you tried to comment out the huanyang: section but did not comment out its contents. If the config file parser does not "see" the huanyang line, it cannot interpret the following lines which only make sense in context.
Was reviewing the working config for the Root4 Lite and uncomment huanyang and uploaded it to the controller:
uart1: txd_pin: gpio.15 rxd_pin: gpio.16 rts_pin: gpio.14 baud: 9600 mode: 8N1
Huanyang: uart_num: 1 modbus_id: 1 tool_num: 0 speed_map: 0=0% 0=25% 6000=25% 24000=100% off_on_alarm: false Got error:
[MSG:ERR: Ignored key uart1] [MSG:ERR: Skipping key txd_pin indent 4 this indent 2] [MSG:ERR: Skipping key rxd_pin indent 4 this indent 2] [MSG:ERR: Skipping key rts_pin indent 4 this indent 2] [MSG:ERR: Skipping key baud indent 4 this indent 2] [MSG:ERR: Skipping key mode indent 4 this indent 2]
rts_pin is not connected to VFD, not sure where to connect it
Changed config to:
uart2: txd_pin: gpio.15 rxd_pin: gpio.16 rts_pin: gpio.14 baud: 9600 mode: 8N1
Huanyang: uart_num: 2 modbus_id: 1 tool_num: 0 speed_map: 0=0% 0=25% 6000=25% 24000=100% off_on_alarm: false After restarting the firmware no error but, io14 LED blinking, the spindle not starting
The 6x wiki page has an example rs485 config.
http://wiki.fluidnc.com/en/hardware/official/6x_CNC_Controller#rs485
My config is the same now, if I use uart1 I have an error, if I use uart2 in config no error but the spindle not starting. Changing the combination of wires doesn't help. What else should I try?
" if I use uart1 I have an error"
What is the error? If the error is in the startup messages, please paste those in a reply.
It will take forever to solve your problem unless you ask questions more clearly. For example
Was reviewing the working config for the Root4 Lite
What exactly is "the working config for the Root4 Lite". I searched the internet for "root4 lite fluidnc config" and did not find a clear answer, so I'm not sure exactly what config you are referring to.
uart1: txd_pin: gpio.15 rxd_pin: gpio.16
Indentation, i.e. the number of spaces at the beginning of a line, matters a lot for yaml, so if you paste in a way that loses the indentation, we cannot be sure what you have. The way to preserve indentation is to mark the lines as a "code block" usint this control in the github form
Then use Preview to see if it worked right.
The error messages:
[MSG:ERR: Ignored key uart1]
[MSG:ERR: Skipping key txd_pin indent 4 this indent 2]
tell me that your indentation is bad. uart1:
must be at the beginning of a line with no spaces before it. The lines from txd_pin:
to mode:
must be preceded by the same number (more than 0) of spaces, like this.
uart1:
txd_pin: gpio.15
rxd_pin: gpio.16
rts_pin: gpio.14
baud: 9600
mode: 8N1
My config is the same now
The same as what?
rts_pin is not connected to VFD, not sure where to connect it
None of those pins - neither txd_pin, rxd_pin, nor rts_pin - are directly connected to the VFD. Instead, they are connected to an on-board RS485 interface chip whose two outputs "RS485 A" and "RS485 B" should be connected to the VFD
if I use uart2 in config no error
Either uart1 or uart2 should work. I suspect that you fixed the indentation when you changed to uart2.
but the spindle not starting.
It can be very difficult to get a VFD setup correctly, especially with RS485, because there are a lot of VFD settings that must be just right. http://wiki.fluidnc.com/en/config/config_spindles#variable-frequency-drives-vfd-controlled-with-rs485 . It is often much easier to use 0-10V control.
Thank you for the clear explanation. Updated my config:
uart1: txd_pin: gpio.15 rxd_pin: gpio.16 rts_pin: gpio.14 baud: 9600 mode: 8N1
Huanyang: uart_num: 1 modbus_id: 1 tool_num: 0 speed_map: 0=0% 0=25% 6000=25% 24000=100% off_on_alarm: false
No more errors on startup:
[MSG:INFO: FluidNC v3.8.0 https://github.com/bdring/FluidNC] [MSG:INFO: Compiled with ESP32 SDK:v4.4.7-dirty] [MSG:INFO: Local filesystem type is littlefs] [MSG:INFO: Configuration file:root4l.yaml] [MSG:INFO: Machine 6x Default] [MSG:INFO: Board 6x CNC Controller] [MSG:INFO: UART1 Tx:gpio.15 Rx:gpio.16 RTS:gpio.14 Baud:9600] [MSG:INFO: I2SO BCK:gpio.22 WS:gpio.17 DATA:gpio.21] [MSG:INFO: SPI SCK:gpio.18 MOSI:gpio.23 MISO:gpio.19] [MSG:INFO: SD Card cs_pin:gpio.5 detect:NO_PIN freq:8000000] [MSG:INFO: Stepping:I2S_stream Pulse:10us Dsbl Delay:0us Dir Delay:1us Idle Delay:255ms] [MSG:INFO: Axis count 4]
But, the spindle not start after: S6000 M3 command
in console: S6000 M3 ok
On Mon, Aug 5, 2024 at 12:30 AM Mitch Bradley @.***> wrote:
It will take forever to solve your problem unless you ask questions more clearly. For example
Was reviewing the working config for the Root4 Lite
What exactly is "the working config for the Root4 Lite". I searched the internet for "root4 lite fluidnc config" and did not find a clear answer, so I'm not sure exactly what config you are referring to.
uart1: txd_pin: gpio.15 rxd_pin: gpio.16
Indentation, i.e. the number of spaces at the beginning of a line, matters a lot for yaml, so if you paste in a way that loses the indentation, we cannot be sure what you have. The way to preserve indentation is to mark the lines as a "code block" usint this control in the github form
image.png (view on web) https://github.com/user-attachments/assets/42e1a3da-ba41-411d-811e-2334ecef207e
Then use Preview to see if it worked right.
The error messages:
[MSG:ERR: Ignored key uart1] [MSG:ERR: Skipping key txd_pin indent 4 this indent 2]
tell me that your indentation is bad. uart1: must be at the beginning of a line with no spaces before it. The lines from txd_pin: to mode: must be preceded by the same number (more than 0) of spaces, like this.
uart1: txd_pin: gpio.15 rxd_pin: gpio.16 rts_pin: gpio.14 baud: 9600 mode: 8N1
My config is the same now
The same as what?
rts_pin is not connected to VFD, not sure where to connect it
None of those pins - neither txd_pin, rxd_pin, nor rts_pin - are directly connected to the VFD. Instead, they are connected to an on-board RS485 interface chip whose two outputs "RS485 A" and "RS485 B" should be connected to the VFD
image.png (view on web) https://github.com/user-attachments/assets/6e5ecf6a-8f68-4263-966e-803f39fe06bb
if I use uart2 in config no error
Either uart1 or uart2 should work. I suspect that you fixed the indentation when you changed to uart2.
but the spindle not starting.
It can be very difficult to get a VFD setup correctly, especially with RS485, because there are a lot of VFD settings that must be just right. http://wiki.fluidnc.com/en/config/config_spindles#variable-frequency-drives-vfd-controlled-with-rs485 . It is often much easier to use 0-10V control.
— Reply to this email directly, view it on GitHub https://github.com/bdring/FluidNC/issues/1286#issuecomment-2268150359, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJUVME3LNLMDWAPRIU437DZP35VZAVCNFSM6AAAAABL7HL4LGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRYGE2TAMZVHE . You are receiving this because you authored the thread.Message ID: @.***>
The 6x wiki page mentions using LEDs to help debug the rs485.
Tell what happened?
io14 - blinking LED14 - is led up and off at the same time as io14 led.
Found additional settings on VFD for Communication function parameters: F163 set to 1 (communication address) F164 set to 1 (communication transmission speed 9600 default is 2- 19200) F165 set to 0 (0- 8N1 for ASCII was 3- 8N1 for RTU) F169 default 0 (0- Communication 0201H register adopts 1 bit decimal, 1- Communication 0201H register adopt 2 bit decimal)
On Mon, Aug 5, 2024 at 8:03 AM bdring @.***> wrote:
The 6x wiki page mentions using LEDs to help debug the rs485.
Tell what happened?
— Reply to this email directly, view it on GitHub https://github.com/bdring/FluidNC/issues/1286#issuecomment-2268908749, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJUVMFBHY6WG5KNRMEL6KTZP5SZPAVCNFSM6AAAAABL7HL4LGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRYHEYDQNZUHE . You are receiving this because you authored the thread.Message ID: @.***>
As the wiki says...If LED 14 and LED15 are blinking the controller is talking to the VFD, but the VFD is not responding.
There are a lot of registers that must be set on the VFD. See this wiki page for that.
http://wiki.fluidnc.com/en/config/config_spindles#huanyang-vfd-with-rs485
Make sure that you read all relevant wiki sections and pages before trying any config sections or wiring. It is easy to break the controller if you make mistakes like sending outputs in shorts, etc.
One more question about RS485 from controller to VFD what would be a proper setting for:
0- 8N1 for ASCII was 3- 8N1 for RTU?
On Mon, Aug 5, 2024 at 9:39 AM bdring @.***> wrote:
As the wiki says...If LED 14 and LED15 are blinking the controller is talking to the VFD, but the VFD is not responding.
There are a lot of registers that must be set on the VFD. See this wiki page for that.
http://wiki.fluidnc.com/en/config/config_spindles#huanyang-vfd-with-rs485
Make sure that you read all relevant wiki sections and pages before trying any config sections or wiring. It is easy to break the controller if you make mistakes like sending outputs in shorts, etc.
— Reply to this email directly, view it on GitHub https://github.com/bdring/FluidNC/issues/1286#issuecomment-2269105201, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJUVMGQLDSM655IRBQ436DZP56A7AVCNFSM6AAAAABL7HL4LGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRZGEYDKMRQGE . You are receiving this because you authored the thread.Message ID: @.***>
8n1
Have you seen this? It is on the wiki.
Yes, TY. Trying to much it with my settings on my VFD, my not PD... on my it is F..
On Mon, Aug 5, 2024 at 1:19 PM bdring @.***> wrote:
Have you seen this? It is on the wiki.
image.png (view on web) https://github.com/user-attachments/assets/5649a293-5f5c-47c2-ac95-36c5f97e02f4
— Reply to this email directly, view it on GitHub https://github.com/bdring/FluidNC/issues/1286#issuecomment-2269546502, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJUVMDG6OSXXZPIITL4TYDZP6X2XAVCNFSM6AAAAABL7HL4LGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRZGU2DMNJQGI . You are receiving this because you authored the thread.Message ID: @.***>
Show a picture of your VFD
Wiki Search Terms
RS485, H100, VFD
Controller Board
6x CNC Controller
Machine Description
Root 4 Lite
Input Circuits
Configuration file
Startup Messages
User Interface Software
Webui, UGS
What happened?
Updated VFD setting:
F011 100 F005 400
F001 default 0 (keyboard) changed to 2 (communication port) F002 default 3 (operate potentiometer) changed to 2 (communication port)
GCode File
No response
Other Information
[MSG:ERR: Ignored key uart1] [MSG:ERR: Skipping key txd_pin indent 4 this indent 2] [MSG:ERR: Skipping key rxd_pin indent 4 this indent 2] [MSG:ERR: Skipping key rts_pin indent 4 this indent 2] [MSG:ERR: Skipping key baud indent 4 this indent 2] [MSG:ERR: Skipping key mode indent 4 this indent 2] [MSG:ERR: Skipping key uart_num indent 4 this indent 2] [MSG:ERR: Skipping key modbus_id indent 4 this indent 2] [MSG:ERR: Skipping key tool_num indent 4 this indent 2] [MSG:ERR: Skipping key speed_map indent 4 this indent 2] [MSG:ERR: Skipping key off_on_alarm indent 4 this indent 2]