-
-
Notifications
You must be signed in to change notification settings - Fork 768
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
UGS wont connect under FluidNC drop down #2604
Comments
What is the output of |
[VER:3.8 FluidNC v3.8.2:] |
What is the controller state after you connected using the GRBL_ESP32 profile? Can you disconnect, enable verbose logging (right click in console and select "Enable verbose logging") and connect again with the FluidNC profile and paste the messages here. Can you attach your config.yaml. |
After Connecting to grblesp32 profile, the machine and controller are ready to be used. Ive run a program with it. Heres the output of Fluidnc connection profile:
ok
spi: sdcard: kinematics: axes:
y:
z:
[MSG:INFO: Huanyang PD015 Decel:5.000] control: estop_pin: NO_PIN coolant: probe: macros: start: parking: user_outputs: web_commands: wifi: ota: mdns: wifi: telnet_server: notifications: Huanyang: modbus_id: 1 arc_tolerance_mm: 0.002000 This is the output and state of controller after connecting to grblesp32 profile:
Yaml file: |
I loaded up your config to a controller and tried it. I don't have TMC drivers or the Huangyang spindle so I am not able to simulate your scenario fully. But I think that this is a clue:
It looks like the controller has not completed the boot before UGS starts quering the controller. Can you connect and power up your controller and wait a minute before connecting to the controller through UGS. This should not be a problem, but looking through the lines after there are some wierd things happening. The reason it fails to connect later on looks to be caused by it either getting duplicated messages from the controller . Here is an example, it receives the line with
|
So, I did what you asked and still nothing. Then I unplugged my vfd and it connected but nothing has changed unless for some reason theres a variable in the huanyang vfd I need to change? I havent changed anything. I unplugged and reconnected several times....it works now. But if I plug the spindle in, it wont connect. |
I noticed these two lines though when you connected to it using the GRBL profile and remember that there was another issue where UGS would try to initiate the connection twice on certain device setups (think it was when connecting to it via WiFi):
I fixed that particular issue in version 2.1.9, you could give that version a try: Other than that this will be really hard for me to debug and fix as I don't have a controller equipped with RS485 and VFD supporting it. |
Sorry for the late reply, another user had the same problem and I think that I've fixed it. Please try the latest nightly build from here: |
Version
2.1.8
Hardware / Firmware
FluidNC
What happened
UGS Wont connect to machine using the FluidNC drop down, it keeps telling me...
*** Fetching device settings
*** Could not establish connection with the controller
*** Connection closed
*** Could not establish connection with the controller
But when I choose grbl esp32 from the drop down, it connects and runs fine. Runs a job if I load it.
I tried everything thinking it was a hardware issue, its not a hardware issue that I can see.
How to reproduce
If I choose FluidNC from drop down, it will not connect and gives the same response. But grbl esp32 connects every time and works with the machine.
Operating System
Windows 11 Pro
Anything else
Every time.
The text was updated successfully, but these errors were encountered: