Stuck at ALARM10

[tcurdt]

I am trying to use a Pico for some grblHAL testing.

I've build a generic pico firmware with the webbuilder at http://svn.io-engineering.com:8080/
Based on grblHAL build 20240817.

I've tried gSender (and UGS).
I connect and get an ALARM10.

gSender - [grblHAL]
Connected to /dev/tty.usbmodem0000000000001 with a baud rate of 115200
[VER:1.1f.20240817:]
client $$
[OPT:VNMSL,100,1024,3,0]
[NEWOPT:ENUMS,RT+,ES,SED,RTC]
[FIRMWARE:grblHAL]
[SIGNALS:HSEP]
[NVS STORAGE:*FLASH]
[FREE MEMORY:219K]
[DRIVER:RP2040]
[DRIVER VERSION:240817]
[DRIVER OPTIONS:SDK_1.5.0]
[AUX IO:3,2,0,0]
[PLUGIN:MODBUS v0.16]
ok
$0=10.0 (Step pulse time, μs)
$1=25 (Step idle delay, ms)
$2=0 (Step pulse invert, mask)
$3=0 (Step direction invert, mask)
$4=7 (Invert step enable pin, boolean)
$5=0 (Invert limit pins, boolean)
$6=0 (Invert probe pin, boolean)
$9=1
$10=511 (Status report options, mask)
$11=0.010 (Junction deviation, mm)
$12=0.002 (Arc tolerance, mm)
$13=0 (Report in inches, boolean)
$14=0
$15=0
$16=0
$17=0
$18=0
$19=0
$20=0 (Soft limits enable, boolean)
$21=0 (Hard limits enable, mask)
$22=0 (Homing cycle enable, mask)
$23=0 (Homing direction invert, mask)
$24=25.0 (Homing locate feed rate, mm/min)
$25=500.0 (Homing search seek rate, mm/min)
$26=250 (Homing switch debounce delay, ms)
$27=1.000 (Homing switch pull-off distance, mm)
$28=0.100 (G73 pull-off distance, mm)
$29=0.0 (Step Pulse Delay, μs)
$30=1000.000 (Maximum spindle speed, rpm)
$31=0.000 (Spindle Mode, )
$32=0 (Laser-mode enabled as spindle, boolean)
$33=5000.0 (Spindle Frequency, Hz)
$34=0.0 (Spindle Duty Cycle, %)
$35=0.0 (Minimum spindle speed, %)
$36=100.0 (Maximum spindle speed, %)
$37=0 (Deenergized Steppers, %)
$39=1 (Printable Command Characters, boolean)
$40=0 (Soft Limits Jogging, boolean)
$43=1 (Homing Locate Cycle, )
$44=4 (Axis Mask, )
$45=3 (Axis Mask, )
$46=0 (Axis Mask, )
$62=0 (Sleep Function, boolean)
$63=3 (Disable Laser on Hold, boolean)
$64=0 (Alarm on Startup, boolean)
$65=0 (Allow Feedrate Override, boolean)
$100=250.00000 (X-axis travel resolution, step/mm)
$101=250.00000 (Y-axis travel resolution, step/mm)
$102=250.00000 (Z-axis travel resolution, step/mm)
$110=500.000 (X-axis maximum rate, mm/min)
$111=500.000 (Y-axis maximum rate, mm/min)
$112=500.000 (Z-axis maximum rate, mm/min)
$120=10.000 (X-axis acceleration, mm/sec^2)
$121=10.000 (Y-axis acceleration, mm/sec^2)
$122=10.000 (Z-axis acceleration, mm/sec^2)
$130=200.000 (X-axis maximum travel, mm)
$131=200.000 (Y-axis maximum travel, mm)
$132=200.000 (Z-axis maximum travel, mm)
$341=0 (Manual tool change mode, )
$342=30.0 (Probing distance, mm)
$343=25.0 (Probing slow feed rate, mm/min)
$344=200.0 (Probing seek feed rate, mm/min)
$345=200.0
$346=1
$370=0
$372=0
$374=3
$375=50
$384=0
$394=4.0
$398=100
$481=0
$484=1
$486=0
$673=1.0
ok
ok
ok
ok
ok
0 - PWM
ok

When I try to unlock the machine I am getting this:

client \x18
client $X

Since it's just the bare board without a NC connections I assume I will have invert some pins for this to startup correctly?

But it seems like gSender does not allow me to change any of the firmware settings.
Not sure whether that is a gSender problem or a grblHAL protection of some sort.

Any pointers?

[terjeio]

Any pointers?

This Wiki page.

[tcurdt]

So I should be able to manually flip in the input logic.
And the fact that gSender doesn't allow for changing firmware settings in the alarm state is a gSender problem.

Correct?

[terjeio]

Correct. AFAIKT recent gsender versions supports the advanced settings handling/UI possible with grblHAL.

[tcurdt]

Yes, they do. But it seems like they are not accessible when there is an alarm.
I might report that with them then.
Thanks for the help! 🙏

[tcurdt]

I changed it manually

$2=0 (Step pulse invert, mask)
$3=0 (Step direction invert, mask)
$4=7 (Invert step enable pin, boolean)
$5=7 (Invert limit pins, boolean)
$6=0 (Invert probe pin, boolean)
$9=1
$10=511 (Status report options, mask)
$11=0.010 (Junction deviation, mm)
$12=0.002 (Arc tolerance, mm)
$13=0 (Report in inches, boolean)
$14=70

but I still get an alarm 10 - but it does not show any inputs causing it 🤨

<Alarm|MPos:0.000,0.000,0.000|Bf:100,1023|FS:0,0>

[tcurdt]

Ah, I had to clear the previous alarm somehow. Now all is good.

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