Tyvok Spinder A1: Error:9 G-code locked out during alarm or jog state

Hello everyone, recently I purchased the Tyvok Spinder A1 and intended to use it as a graduation gift for my friend. However, I am encountering a recurring ‘Error: 9’ problem. Despite exploring the platform and discussions, I haven’t been able to find a solution. Therefore, I am reaching out here to seek your assistance. Thank you.

Here is the console and my device settings:
Waiting for connection…

)�-�-�To���i�ok

ok

[V4.00(8M.H35.20240311)]

[VER:1.1h.2024031101:]

[OPT:VPH,63,256]

Target buffer size found

[MSG:Using machine:MKS DLC32]

ok

[MSG:No Wifi]

ok

ALARM:8

Homing fail. Cycle failed to clear limit switch when pulling off. Try increasing pull-off setting or check wiring.

ok

Grbl 1.1h [‘$’ for help]

ok

[MSG:‘$H’|‘$X’ to unlock]

ok

[MSG:Caution: Unlocked]

ok

ok

<Idle|MPos:0.000,0.000,0.000|WPos:0.000,0.000,0.000|FS:0,0|WCO:0.000,0.000,0.000>

ok

ok

<Idle|MPos:0.000,0.000,0.000|WPos:0.000,0.000,0.000|FS:0,0|Ov:100,100,100>

ok

Starting stream

Stream completed in 0:08

ok

<Idle|MPos:0.000,0.000,0.000|WPos:0.000,0.000,0.000|FS:0,0|Ov:100,100,100>

ok

Starting stream

Stream completed in 0:08

<Idle|MPos:0.000,0.000,0.000|WPos:0.000,0.000,0.000|FS:0,0|Ov:100,100,100>

ok

Starting stream

Stream completed in 0:08

Starting stream

Layer C00

Grbl 1.1h [‘$’ for help]

ALARM:1

Hard limit triggered. Machine position is likely lost due to sudden and immediate halt. Re-homing is highly recommended.

On or near line 0:

Job halted

Stream completed in 1:13

error:9

G-code locked out during alarm or jog state.

error:9

G-code locked out during alarm or jog state.

[MSG:Caution: Unlocked]

<Idle|MPos:16.020,-153.960,0.000|WPos:16.020,-153.960,0.000|FS:0,0|Pn:X|WCO:0.000,0.000,0.000>

ok

<Idle|MPos:16.020,-153.960,0.000|WPos:16.020,-153.960,0.000|FS:0,0|Pn:X|Ov:100,100,100>

ok

<Idle|MPos:16.020,-153.960,0.000|WPos:16.020,-153.960,0.000|FS:0,0|Pn:X>

ok

ok

<Idle|MPos:0.000,0.000,0.000|WPos:0.000,0.000,0.000|FS:0,0>

ok

ok

<Idle|MPos:0.000,0.000,0.000|WPos:0.000,0.000,0.000|FS:0,0>

ok

Starting stream

[MSG:Program End]

Stream completed in 0:00

<Idle|MPos:2.000,0.000,0.000|WPos:2.000,0.000,0.000|FS:0,0|WCO:0.000,0.000,0.000>

ok

Starting stream

[MSG:Program End]

Stream completed in 0:00

<Idle|MPos:2.000,0.000,0.000|WPos:2.000,0.000,0.000|FS:0,0|WCO:0.000,0.000,0.000>

ok

<Idle|MPos:2.000,0.000,0.000|WPos:2.000,0.000,0.000|FS:0,0|Ov:100,100,100>

ok

<Idle|MPos:2.000,0.000,0.000|WPos:2.000,0.000,0.000|FS:0,0>

ok

Starting stream

Stream completed in 0:08

Starting stream

[MSG:Program End]

Stream completed in 0:00

<Idle|MPos:5.000,0.000,0.000|WPos:5.000,0.000,0.000|FS:0,0|WCO:0.000,0.000,0.000>

ok

Starting stream

Stream completed in 0:08

<Idle|MPos:5.000,0.000,0.000|WPos:5.000,0.000,0.000|FS:0,0|Ov:100,100,100>

ok

Starting stream

Layer C00

Grbl 1.1h [‘$’ for help]

ALARM:1

Hard limit triggered. Machine position is likely lost due to sudden and immediate halt. Re-homing is highly recommended.

On or near line 0:

Job halted

Stream completed in 0:38

error:9

G-code locked out during alarm or jog state.

error:9

G-code locked out during alarm or jog state.

[MSG:Caution: Unlocked]


You have a a series of homing related issues, error 9 is simply the firmware telling you “there was errors”

Alarm 8 usually is linked to the pull of phase of your homing
Alarm 1 is a hard limit, when the machine slams on the switches outside homing

I would suggest reviewing the hardware specially belt tensions. as without a proper homing cycle all other errors might be a consequence of a bad homing

3 Likes

To add to Gil’s comments — sometimes this means the limit switches are stuck down, or the laser head is stuck up against them. Check both switches to make sure they’re moving freely.

If your laser head is already up against the switches in the bottom left corner, make sure the power supply to your laser is securely plugged in and functioning properly. A USB connection is enough to power the laser’s control board, but not the stepper motors, so your laser could be connected and able to send commands/messages, but not able to move off the switches.

2 Likes

Thank you to both of you. After checking and adjusting the engraving speed, I realized that the issue lies with the belt tension of the x-axis. Once I decreased the speed to no more than 4400 or the width of the image I was using, the hard limit didn’t occur again. Therefore, I believe that the x-axis cannot handle such large movements at high speeds due to the tension problem.

2 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.