gSender v1.4.11 Alarm 14 when entering console command

I’ve been going in HUGE circles attempting to get my AltMill working. Last Friday I could move and activate my PwnCNC spindle. Something went south yesterday and I could not make it move or spin. Today I issued console command $RST=$ to reset the firmware. Immediately, I could move the spindle, but when I entered m3s1200 to spin the spindle, I got an Alarm 14 (Spindle at speed timeout. Clear before continuing.)

How in the heck do I clear the error?
I did enter “$X” but this did nothing for me. I still get the Alarm14 when I reenter the command.

My guess is that you’re seeing Alarm 14 because the SLB and spindle aren’t turned on in the correct order. The controller and VFD need to “handshake” and if the conditions aren’t met, even if they’re on at the same time they won’t go through with the handshake. Now I don’t know exactly how the PWNCNC works but let’s assume that it works similarly to the Sienci spindle… Please follow these instructions in this order:

Assuming the SLB is plugged into power but turned OFF.

  1. Plug spindle into power, the VFD should blink with red text
  2. Then turn on the SLB using the power toggle

This should be the correct way to turn on your controller, each time, to avoid Alarm 14.

Have you contact PWNCNC about this issue before? If so what have they said?

1 Like

Hey, I’m having the same problem with my PWNCNC Spindle also. Not sure if I need to buy their VFD as opposed to the one that came with the oatmeal. I can’t even access any spindle options on code 395.

LOL … error correction at it’s finest :slight_smile:

1 Like

I’m just guessing, double-check your wiring. Also, open gSender, in the bottom right area, click Console. In the section where it says “Enter G-Code here…” enter “$RST=$” (no quotations, I’m not sure if the letter case is important), and click the Run button.

I purchased the PwnCNC 240v VFD, the preset the following values:
P0.0.03 = 2
P0.0.04 = 9
P0.0.11 = 6
P2.0.02 = 21
P4.1.00 = 4
P4.1.01 = 3

I don’t know if the same would be true for your VFD. I suggest that you contact PwnCNC. It would be interesting to know what they suggest. I’m totally in the dark as to what these settings mean and what other values could be used. Possibly Sienci might know what the settings should be. They might not know and suggest you call PwnCNC. You might encounter finger-pointing at this time.

Has anyone had success with the PwnCNC 2.2 water-cooled spindle, PwnCNC VFD, and the AltMill. I’ve been going in huge non-productive circles.

Sienci has remotted into my PC, and confirmed the settings. Yesterday I received a new SBL from Sienci, I installed it and made the firmware settings. When I attempt to run the spindle, after about 4 seconds when I issue a command I get the Alarm 14.

Per PwnCNC they have it running on their AltMill, they sent me a copy of their gSender settings firmware file. I imported them, shut down gSender and powered off my CNC including the VFD. Repowered the VFD, turned on the SLB, opened gSender, connected to the SLB, issued a console command (m3s7000), about 4 seconds after clicking the Run button I get the Alarm 14. The alarm is easy to clear by double-clicking on the orange/brown button on the gSender main screen. I’ve checked the firmware settings several times with no success.

Here is a screen shot of gSender

If you have it running with the PwnCNC 2.2 water-cooled spindle and VFD, please attach a copy of your gSender exported firmware settings.

I’m willing to try almost anything.

@Jgt1942 I’ve moved your issue to the gSender category so that the gSender group in Sienci will be more likely to see it.

1 Like

gwilki, now that you mention that, I’m going to find it.
A link would help.
I have the similar problem, though not the same spindle.

@RobLM I’m sorry, Rob, but I don’t know what you are referring to. What did I “mention”?

Hope I will add data and not noise, but I’m having a similar issue with my MK2 using the 240V air cooled PWNCNC spindle.

I was on the LB using PWM and everything was fine.

Migrating to SLB and ModBus can’t get it to work.

One thing to keep in mind is that I ordered a custom cable from Amazon, not wanting to wait for a US order. So I’m assuming I somehow cannot connect a 2 wire protocol correctly.

No matter how I connect the 2 modes wires, the order I boot the VFD or the SLB, I cannot for the life of my get any error other then alarm14.

I set 340 and 376 to 100 and 12 to have the maximum delays when adjusting speed, but no luck there either.

Next step for me is to hookup the oscilloscope or a logic analyser and try to see if I indeed get modes data on those wire.

Were you able to get this resolved? I have the same issue with a 2.2kw PWNCNC spindle.

Yes the issue has been resolved, I forgot to follow up. The error I had resulted from incorrect height of the spindle. All I had to do was lossen the screws holding the spindle in place, allowing it to move down (closer to the spoilboard) so it was about 1 inch distance between the spoilboard and the spindle.

I was able to surface the spoilboard using a gcode file I got from the IDC Woodcraft site.

At this point I came to another bump in the road. I decided to use the AirWeight vacuum table top. Not a big issue, it just confused me. I’m not in the process of reading the instructions on the AirWeights website and watching the included videos. I purchased the 24x48 kit and several other extras. Jace 2 AirWeights was very helpful. Also a big THANK YOU to PwnCNC for all of their help. I’m SUPER new to CNC and easily confuse, partly by being an old fart.

Were you ever able to resolve your problem with the “Alarm 14” error? I’m having the same error. Just thought I would ask. Thanks Ron