Jogging issues et al

MillMage Software Questions
1

There’s a few issues with this. It may just be that I need to make a pendant for now, but I thought I’d log them in case others have input

  • On grblhal pressing stop during jogging requires a rehome for some reason. Something about stepping being out of whack. On most senders, it’s not an issue
  • I’m finding it hard to get used to having to type in distance, and only having one available. It would be great if there was a quick switch between say 20/5/1/0.1/0.01, rather than having only one value and having to type it each time

On the other hand, I love the framing. Is there a ‘framing offset’ button like the ‘laser offset’ one in lightburn for those of us with positioning optics?

2

On this particular point I found the same (With Lightburn also)
For me, pressing pause then either stop or resume stops the rehome alert.

2 Likes
3

When clicking Stop, we send the controller the “Abort” command, as defined in the GCode tab of the Device Settings.

For grblHAL, that defaults to \x18

image
image429×502 11.8 KB

I’m guessing, the exact message you got is this:

Reset while in motion. Grbl cannot guarantee position. Lost steps are likely. Re-homing is highly recommended.

You can theoretically clear this alarm state by sending it $X, but as the message says, the controller can’t guarantee position, and re-homing is recommended.

You can add a macro for this:

image
image326×379 16.7 KB

And (not sure if that’s the brightest idea!) even change the “Abort” Custom GCode to

\x18
$X

I’d be curious to know which other senders you are using and what they send when you click the Stop button.

Try this :slight_smile:

image
image493×402 23.3 KB

We used to show all those step sizes at once, but I personally prefer the new condensed look.

4

Can you elaborate on what you mean here?

5

I’m pretty sure he means ‘laser offset’ for using with a laser pointer for positioning.

image
image551×363 18.3 KB

6

ah of course! I didn’t think there were spindles with a red dot pointer.

We welcome feature requests for MillMage over at MillMage.fider.io :slight_smile:

1 Like
7

Thanks for the input all.

Exactly this. (in my case it’s a camera which helps with tramming and alignment, but I think a laser pointer would be more common here.

Drill the side of the spindle clamp, add a fixture for a camera or pointer, install and wire through cable chains. A big QOL improvement for 30 mins work :slightly_smiling_face:

That’s reset in grblhal, which may be causing issues:

#define CMD_RESET 0x18 //!< ctrl-X (CAN)

I’m not at my machine currently, but try \x85

from grblhal core:
#define CMD_JOG_CANCEL 0x85 // (133)

I’ll try and take a look through things later, though the menu with basic settings and custom gcode needs a search bar (ux whine, sorry!) - I wish I’d known about millmage earlier, so I could have done my moaning before it hit so many people!

Thanks. :slightly_smiling_face: I think this is more a case of me trying to get used to different workflow than anything else. I’d definitely like the option to show a couple of them, though the UI looks neater like this, so its a bit of a ui vs UX issue

1 Like
8

Here’s mine :wink:

image
image574×683 110 KB

4 Likes
9

Great minds :smiley:

If you’re at the machine can you quickly try the jogging fix I listed above please?

10

Check if this helps achieving what you´re trying:

11

That’s correct, and in my opinion, should also be what the “Stop” button in the “Job Control” window sends.

Interesting! That could be sent when using the Stop sign in the Move panel instead.

image
image465×565 33.5 KB

@JoeSpanier, thoughts?

We’ll still take it! we welcome your constructive feedback

2 Likes
12

Nice to see this.

I’m pasting the link to the recent Fider request here:

1 Like
13

Yep, that’s correct, and may be why I’m finding direct control a little problematic too. Assume that I can edit all this in the config settings, and if not there’s maybe some sort of config file I could hack around in?

I’ll head in now and have a play, may be able to publish a little grblhal crib sheet later.

15

Not that I’m aware, no.
But you can enter \x85 ; Jog Cancel in the “Abort” block here:

image
image342×336 9.01 KB

Just be aware that the Stop button in the Job Control window will stop working as intended while a job is running!

I’ve just created a request to have a separate Custom GCode option to send different commands with each of those stop buttons.

Please let us know what you discover :slight_smile:

3 Likes
16

Roger that. Depending on how creative I feel, I might connect up JTAG to do some intercept/translation.

1 Like
17

I won’t stop you from doing that, but try the “Show All” toggle in the Console window first :wink:

You’ll see exactly what MillMage sends the controller

image
image519×323 13.8 KB

18

Thank you! (The advantage of controller side debug is that I can hold it and translate it to the correct thing before it reaches the MCU, letting me do everything at once.

All tested and you are indeed correct, that it messes with the stop button (which is also wrong for GRBLHAL)

I won’t make a post for users yet, but this is the breakdown if you guys get a moment to look at stuff: [documentation will also want tweaked as these are realtime command and clear buffers]

Jog cancel - 0x85
Stop Job - 0x19
(And as a bonus for autopopulate on enable - Mist start M7, Mist Stop M9)

I suspect there’s also an issue going on as per my other post that I’ve now been able to recreate, I’ll take a look at that soon.

19

Is this the resolution you guys have decided to go with for now?