-
-
Notifications
You must be signed in to change notification settings - Fork 383
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: XPro V5 Machine file Converter problems & TMC Driver issues #723
Comments
Startup messages are saved and can be displayed with $SS. Please get those messages and edit your first post. |
I have since reverted to ESP32 grbl. I'll pick this back up after #485 closes and be sure to collect the necessary start-up data if I have issues then. Unless there's something key here you'd like to see. I am willing to go back to fluidnc temporarily if there is a piece of data there needed to unblock it. |
I have an xPro at home. I should be able to check it when I get home from vacation. |
It works perfectly for me. I restarted in 10 times without issues
|
Please note the orientation / configuration of my machine. Y has two motors and my config follows the XYYZ nomenclature. You'll find most use cases for the xPro (at least those where it is bundled with the BM QB) to use this configuration. |
With your config
|
@synman: In the past I regularly have had to issue a motor disable command ( |
I promise to revisit this just as soon as I'm back on the xPro. I'm working on another controller at the moment. |
I can pick this back up again. Will wire up my xPro over the next couple days and see what I can see. I've learned quite bit about FluidNC since opening this so yeah... don't be surprised if this gets closed as user error. |
Finally was able to find the time to power up the xPro V5 and play around. Everything is working fine with it. In fact, it appears FluidNC fixes a bug that is present in (current and possibly older) GrblESP32 builds for it that make holding and running current unreliable. The Spark-Concepts issue page is full of complaints of fried drivers and I believe this to be root cause. Actual Holding Current (commanding 1.25A): Actual Holding Current (commanding 1.8A): Actual Running Current (commanding 1.8A): Here's what a 1.25A holding current under FluidNC looks like: And a 1.8A running current under FluidNC: |
@bdring closing this out -- thought you might find the "current" situation interesting. |
Controller Board
XPro V5
Machine Description
Queen Bee Pro - 750mm x 750mm - XYYZ
Input Circuits
No response
Configuration file
Startup Messages
User Interface Software
WebUI and CNCjs
What happened?
The machine file converter did not work (bdring/Grbl_Esp32#1324). I was able to work around this by using the XPro V5 config.yaml template on the wiki.
However, a couple issues:
Other Information
No response
The text was updated successfully, but these errors were encountered: