Starting A new (for me) topic for my Genmitsu 6050 XL Pro Issues - STILL

MillMage Hardware Compatibility
, ,
1

Hello

I’ve tried this before but now I have the sold version and licensed. I spent 4 hours trying MM for my Sainsmart Genmitsu 6050 XL Pro. I’ve tried this in Mac native and Windows VM (I did receive permission to use with VM’s) with same or similar issues.

Before I go on and this is repeated but I’m trying again and starting this new topic. None of the previous suggestions in another topic worked.

Within MM, I can manually turn on/off the spindle. I can move the spindle along the X,Y, and Z axis. I set workpiece axis to zeros. I can home. I can then say to travel to workpiece X,Y zeros and watch the spindle travel to the left front of the CNC (the corner to my left, closest to me as I stand at the front of the CNC). I can do the framing for a vector that I set an operation for. I do have multiple operations set to not output and one set to output.

There are multiple issues. Be aware I am very frustrated!

I have been exporting my operations to gcode then running them with Gsender (GS). Gsender works BEAUTIFULLY and maybe people on Youtube that say to only use Gsender have it right but I’m trying and trying and trying with MM. The only thing I set in GS is the probe thickness and the workpiece xeros after homing it.

Please know I have, multiple times, removed and reloaded the device via the wizard to choose Sinsmart then the model. I have gone in and set the Zprobe to be allowed and then, via the probe wizard, entered the thickness of the probe as .767 inches.

The USB port is set to the same as GS, FYI. I believe this wouldn’t be an issue though because I have intentionally set the speed wrong with no manual movements working. I then set it back and manual commands work.

First Issue to Tackle

I have set the Max S Value (BTW, I think misnamed from the description the flyout gives) to 10000, and then tried 18,000. I can manually turn on the spindle. The spindle does NOT turn on when running an operation. There are multiple other issues but I’d like to get the spindle to come on then tackle the other issues. I have confirmed the device toggle for manually turning on the spindle is NOT enabled. The command in the device config does show the right command for turning on the spindle. This isn’t a delay thing. I have enabled the delay up to 6 seconds with no difference. I will say that when exporting the operations with that delay configured in the start spindle setting and running that gcode via GS that it waits that 6 seconds to continue but its after the spindle turns on. In MM, no such action. I really don’t believe a delay, at least where I have been told to put it, is the cause of this problem.

The 1/8” endmill from the toolbox I think was set for 18000 RPM. I have changed that value to multiple values. I have displayed the settings and the G30 (I forget as I type this) does show 10000. I have changed that as well.

I want to fix the auto on/off first but let me give the other issues at a high-level in case they give hints to a larger or accumulative issue that may be the real cause behind the auto start/stop.

A. Z probe. It seems that I can do my own z probe, complete it, and “Finish” it with me then starting an operation with it saying I’ve haven’t Z probed it for this time around. I hit the button to do the z probe. I complete it. Then it says the same dialog box again. BTW, I’m not a fan of the default to bring the spindle to home to do the zprobe. So at times, and its doesn’t seem to cause or cease my other issues, commented out the line to move to home and then move back to workpiece zero.

B. When, at times, and a pattern I can’t determine, the start actually gets the z axis to move and seem to working, the z axis (I’ve read here to remove the bit, I’ve broken three before this from MM) moves way lower then it should.

C. For the last two tests, I hit start the the z axis goes up and hardware limits out. I don’t know why. This is after also reloading the device from scratch.

So any suggestions on how to get the spindle to auto on/off going for the first thing are beyond greatly appreciated! Once this gets working then I will ask again about the other issues.

What makes GS so much better to run things out of the box then MM?

Do I sound very frustrated? I am. Like I said I spent 4 hours trying different things. Looking at settings, testing, going back to look again. That’s 4 hours this time but many hours before this finally using GS to get something done.

Is there a debug mode that will allow me to set breakpoints in the gcode? I want to personally let a line say its being executed to turn on the spindle, take a video to show if the spindle is spinning, and be able to check other variables at the time of the execution of that line of gcode. I am not an expert at gcode but I was a developer for many years, a Sysadmin, and a MySQL DBA. I know my way around a keyboard and am methodical in testing. There must be some obscure issue but again why does GS work? What tools do you use at LB to test the device is operating as expected at a per-line-of-gcode ?

Thanks

2

Doesn’t sound like a comms issue. Under advanced for the machine settings, do you have 'Spindle Manual Start / Stop set?

image (When you check the gcode do you see for example, m3s18000 near the start of the op? (You can just search for M3))

can you post the generated gcode here?

1 Like
3

Hi @fourpaw

I uploaded the entire file. At line 22, is the M3 S30000 line. I also uploaded a screen shot showing the option to manually need to start the spindle NOT on.

Thank you

Allen Gate Sign-90 vbit letters Profile.gcode (30.5 KB)

Screenshot 2026-03-15 at 2.07.28 AM
Screenshot 2026-03-15 at 2.07.28 AM1152×1240 102 KB

4

You’re right, it’s definitely telling the controller to start the spindle. Would be interested to know if that gcode turns the spindle on in gsender. It’s possible its mapped to the wrong output, but if m3s10000 [for example] works when you type it in console on millmage or gsender, it’s not that either.

If you are sure the spindle turns on manually and with gsender, its not a wiring or comms issue. (no vfd either to worry about)

Unfortunately I think you need to wait for support to chime in, because the only things I can think of are (and neither should really stop it working, as M3S30000 should apply the max allowed pwm) are:

The Gemnitsu spindle is only rated to 12000rpm according to their docs.
image

Millmage or the controller may have something that doesn’t allow you to run that fast so skips the lines. It’d be a bit unusual, as grbl would usually just run at the max allowable speed set by $30.

Or, $32 (laser mode) is set to 1. This also in theory shouldn’t affect an M3S30000 mode, as it would still max out the pwm sent.

I’d probably guess this isn’t a millmage issue, but wouldn’t like to pre-empt it. I wish you good luck though.

I am also new to the program and finding the switchover tough (A lot is just to do with ‘what I’m used to’). It’s very promising though, and I am assured by some smart people that there are smart and engaged people behind it, so I’d stick with it.

1 Like
5

If you can generate the GCode with MillMage and export it to GSender, where it runs, we are missing something. MillMage streams the same file it exports, so there should be no difference. The only difference is that MillMage can interject priority commands, like stop and pause, during the streaming process.

Be aware you are not the only one. New software, maybe new process (CNC milling) to you; it will take time for everyone to come up to speed.

That description is accurate. They must match (1:1) so 5000 programmed as the spindle speed will be processed as 5000 by the controller.

Are you sure it is completing automatically? I do not use the probe, but many others do.

This suggests a missmatch between setting Zzero and tool length in the Tool Library. Maybe you can go through both slowly to see if you can find something strange. By the way, this sometimes happens to me too, but I shake it off and start over. :roll_eyes:

6

Its a fake number just to go higher. This CNC has a variable speed physical controller knob. I was trying all different speeds, some sane some rediculous.

7

This is an annoying thing for sure. There are multiple issues like the Z slammed up the other day when starting a project. I have learned to remove the bit but then MM never believes the z-probing worked so then I put the bit back in and …. well, for such a common model. So if gSender didn’t work I would say the CNC or the controller or something but gSender works out of the box.

The laser setting is off on the devices manager too. Go figure why its showing 1?

Signed,

Frustrated!

8

Then you say…

If we are talking about the spindle, we have a contradiction. Our image of the machine, and what you are doing, is set entirely by what you show and tell us. Making a diagnosis is not practical without good information.

9

Hi

Yes, I agree and understand how anyone can only know what I describe. Let me try to clarify. The CNC has a box with a rotating knob that controls the speed of the spindle. That knob does not control the spindle activation. The activation of the spindle is via software in both gSender and in MillMage confirmed by the fact that gSender works for the gCode created by MM and that in MM, I can control the spindle by the manual spindle control. The fact that I said the speed isn’t controlled by MM wasn’t meant to say the on/off of the spindle also wasn’t controlled by software.

So I went through the first few lines of gCode and saw this below, in bold. This appears controlled by the Device Settings option “Output Tool Change”. This didn’t affect gSender when running the same gCode. I “suppose, not confirmed” that gSender skips lines it doesn’t understand?

if I’m supposed to, I never see a popup or any indication to change bits and continue. Also the behavoir with that line the spindle doesn’t turn on AND the z axiz will drive the non-spinning bit into the material.

Question - where is the safe retract of 29.999 (30) coming from? I don’t see that value in “Device Settings”

;MillMage Core 0.8.00
;Custom GCode device profile, absolute coords
;Bounds: X11.35 Y11.165 to X530.834 Y119.115
;Project Units: Inch
;Safe Retract = 29.9999
;Stock Thickness: 19.05
;Z Zero: Top
;Workpiece origin is at the Bottom Left
G00 G17 G40 G21;Restore metric mode
G54

G90;Restore absolute mode
G0 Z30
G90;Restore absolute mode
;90 vbit letters Profile @ 1501.14 mm/min, 18000 RPMs
M5
; T{tool}.

@T ← This seems to be the culprit. I removed this line and the tool comes on
G21;Restore metric mode

M3 S18000

For another issue with zprobing. This is the code that is set in the device settings after doing the zprobe configuration. Of the instructions below, what sets the Z to the value after the probe does its thing?

M5

G21;Restore metric mode

G53G1 Z-19.507F2400

G53G1 X0Y0F2400

G91;Restore relative mode

G1 Z-0.1F150

G38.2 Z-100 F150

G1 Z1.499F2400

G38.2 Z-3.505 F30

G90;Restore absolute mode

G53G1 Z-19.507F2400

G90;Restore absolute mode

G54

G1 X0Y0F2400

Thanks

10

the retract distance is in the “project setup” located under the “file” tab.

if set to high; the z axis may hit limit (soft or hard) and prevent tool activation

11

Do you mean the spindle comes on?

Posting about Tool changes:

If you want tool change halts between operations, you will need to modify the Custom GCode for Tool Change. You cannot just turn it on and it will work. Otherwise, you must turn the Operation steps on and off one-by-one to enable a tool change. I like the no-hassle part of it moving to my desired location and returning when I say ok.

Here is my setup for manual tool changes. If you want to use a touch probe, you will need to set that up as well.

Tool Change GCode
Tool Change GCode907×676 104 KB

My retract is to Zzero, not the Zhome position which would be higher up.

12

Yes, the spindle turns on.