Post a URL to the data sheet or provide a part number.
Understood and acknowledged above.
We need to see the $SS outputs and the config.yaml.
Pretty much stuck until then.
Above I posted the config.yaml file he is using. Here:
Here is his $SS output.
$SS
<Idle|MPos:0.000,0.000,0.000,0.000,0.000|FS:0,0|Pn:Z|WCO:0.000,0.000,0.000,0.000,0.000>
[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:config.yaml]
[MSG:INFO: Machine MPCNC]
[MSG:INFO: Board Jackpot TMC2209]
[MSG:INFO: UART1 Tx:gpio.0 Rx:gpio.4 RTS:NO_PIN Baud:115200]
[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:20000000]
[MSG:INFO: Stepping:I2S_static Pulse:4us Dsbl Delay:0us Dir Delay:1us Idle Delay:255ms]
[MSG:INFO: User Digital Output:0 on Pin:gpio.26]
[MSG:INFO: User Digital Output:1 on Pin:gpio.27]
[MSG:INFO: Axis count 5]
[MSG:INFO: Axis X (0.000,1220.000)]
[MSG:INFO: Motor0]
[MSG:INFO: tmc_2209 UART1 Addr:0 CS:NO_PIN Step:I2SO.2 Dir:I2SO.1 Disable:I2SO.0 R:0.110]
[MSG:INFO: X Neg Limit gpio.25]
[MSG:INFO: Axis Y (0.000,2440.000)]
[MSG:INFO: Motor0]
[MSG:INFO: tmc_2209 UART1 Addr:1 CS:NO_PIN Step:I2SO.5 Dir:I2SO.4 Disable:I2SO.7 R:0.110]
[MSG:INFO: Y Neg Limit gpio.33]
[MSG:INFO: Axis Z (-100.000,200.000)]
[MSG:INFO: Motor0]
[MSG:INFO: tmc_2209 UART1 Addr:2 CS:NO_PIN Step:I2SO.10 Dir:I2SO.9 Disable:I2SO.8 R:0.110]
[MSG:INFO: Z Neg Limit gpio.32:low]
[MSG:INFO: Axis A (-100.000,200.000)]
[MSG:INFO: Motor0]
[MSG:INFO: tmc_2209 UART1 Addr:3 CS:I2SO.19 Step:I2SO.18 Dir:I2SO.17 Disable:I2SO.16 R:0.110]
[MSG:INFO: A Neg Limit gpio.34]
[MSG:INFO: Axis B (-100.000,200.000)]
[MSG:INFO: Motor0]
[MSG:INFO: tmc_2209 UART1 Addr:3 CS:I2SO.14 Step:I2SO.13 Dir:I2SO.12 Disable:I2SO.15 R:0.110]
[MSG:INFO: B Neg Limit gpio.35]
[MSG:INFO: X Axis driver test passed]
[MSG:INFO: Y Axis driver test passed]
[MSG:INFO: Z Axis driver test passed]
[MSG:INFO: A Axis driver test passed]
[MSG:INFO: B Axis driver test passed]
[MSG:INFO: Kinematic system: Cartesian]
[MSG:INFO: Using spindle NoSpindle]
[MSG:INFO: Flood coolant gpio.2]
[MSG:INFO: Mist coolant gpio.16]
[MSG:INFO: Probe gpio.36:low]
[MSG:INFO: STA SSID is not set]
[MSG:INFO: AP SSID FluidNC IP 192.168.0.1 mask 255.255.255.0 channel 1]
[MSG:INFO: AP started]
[MSG:INFO: WiFi on]
[MSG:INFO: Captive Portal Started]
[MSG:INFO: HTTP started on port 80]
[MSG:INFO: Telnet started on port 23]
ok
Our use of end stop switchesā¦
- simple switch, only two wires.
- each pair of pins (in the end stop switch block of pins) is all thatās needed or used.
- Should be āNormally Closedā (N/C) not āNormally Openā (N/O).
Maybe some other approach could work, but I tend to think some tinkering with the setup would be needed. Do you have a simpler normally closed switch to try with, using only the two pins?
Yes. I tried a simple normal closed two wire switch last night. Same result. When it comes time to install the switches I can wire them differently and accomplish NC but Iād rather run them normally open if possible. Definitely not a deal breaker though and far down the list of priorities.
Also thanks a million for posting the pics and info Iāve been sending you.
Itās more clicks to send them to your email than to just post them in a forum so Iād much rather post them in the forum but for now you are saving my bacon by posting them for me. Thanks, Doug!
Thanks in advance to all the guys that are helping with this project.
Also Iāll add that one of the reasons Iām hopeful for the FluidNc Jackpot board to work is because I need a very easy to use and less fāupable interface for the end user that will be operating it. Mach3 will allow sweeping changes with nothing but a misplaced press of a button and I canāt have that happening with me not around to troubleshoot it.
FluidNc seems to have an extremely easy to use interface so nothing but a short training video and some shadow training should have a n operator capable of necessary functions within a day. So I may have some questions when this problem is solved on how to modify (if possible) the interface to remove all functions that would be detrimental such as the delete button on the ymal file haha
1 Like
From the FluidNC wiki on this:
Normally Open (N.O.) vs. Normally Closed (N.C.)
You can use N.O. or N.C. switches. Both will require a pulling resistor for the open state. The closed state has lower impedance because the open state uses a resistor to set the voltage and the closed state is a direct connection. This means N.C. is less likely to falsely trigger due to noise during normal operation.
I still recommend you get it working as is with a V1 config. Make sure XYZ work, no need to even worry about the cloned axes.
Then change one stepper. Do not edit everythign at once take baby steps.
1 Like
Hereās a link to the steppers Ryanās store has, which are known to work with Jackpot:
I checked the listing to see if it identified which stepper wire is what, but that level of detail is not shown.
I donāt know if itās worth it to you to spend $11.50 + shipping to get one, to know for sure itās not an issue of different wiring config on yours.
He tried first using the pre-flashed config, and got no movement. Heās brand new to FluidNC / Jackpot and still working to get some movement other than a strange grumbling stutter.
Ok Iāll try it with that wiring pinout. I think thatās one of the wiring configs I tried yesterday but it canāt hurt to be sure.
Do you have a model number on those motors?
Iām thinking motors too, not config, because it should at least move a little bit, even if briefly or in the wrong direction.
Then do not edit the file, figure out why it does not work as is. This is a know good file on a tested board.
Any 4-6 wire stepper will work, if it does not move but makes funny noises the coils are wired wrong, not a bad firmware edit.
2 Likes
Ok I tried the standard wiring that works for all the other machines and got nothing but what it is in the video above.
It just tried the wiring in the picture sent of that small pancake stepper in the pic above that someone sent. It locked the stepper and if reversed entirely it produces heat in the driver.
If you donāt have a model number, you can determine the motor coils this way:
- Unplug the motor from the board.
- Measure resistance on the connector from 1 to 2 and 3 to 4. These should be low resistance.
- Also measure 1 to 3 and 1 to 4 and 2 to 3 and 2 to 4. These should all be open circuit.
If your resistance values donāt agree with above, report what you do get.
1 Like
Yep, good approach. So far it does sound like a wiring issue.
I checked the stepper pinout with my meter and the pairs are going to the correct pins and all of my steppers have the same pinout. Basically on the 6 pin side starting from the left I would put one side of a pair and move four pins over to where the other side of that pair goes and then repeat but opposite starting from the right.
No movement.
I tried on a grbl board and a Mach3 and the steppers all worked fine.
You are not using the ānormalā stepper drivers though, are you? If not, just ignore, I only had time to skim the post.
Thanks for any input you may have, Philipp.
I do have various steppers that are used to accommodate certain torque needs etc but after realizing nothing moved I ditched all that jazz and went to the most basic of setups possible while I troubleshoot. I have tried all my steppers at this point but the majority of my trouble shooting is with a regular standard Nema 17 that would come on any retail cnc router. As a mater of fact I think the one in front of me is from a Genmitsu router. Nothing special.
1 Like
I am talking about the drivers, not the steppers. 
Skimming some more you seem to use the 2209. Hmmā¦