V1.4.3 start at line # does not start spindle

MtrDLP · March 25, 2024, 2:13am

Start at line# moves does not restart the spindle. It moves around like it is starting from the right place but doesn’t spin up.

MtrDLP · March 30, 2024, 11:16pm

No response here? No one else having this issue?

gwilki · March 30, 2024, 11:23pm

@MtrDLP Does it work in 1.4.5?

MtrDLP · March 31, 2024, 3:21am

in 1.4.5 it starts the spindle but ignores the dwell time

gwilki · March 31, 2024, 11:50am

@MtrDLP Here is an old thread on this same issue.

If the recommended solution is out of date, you may want to open a support ticket with Sienci. I’m sure that their gSender group will reply.

MtrDLP · March 31, 2024, 3:22pm

It is very disappointing that this issue isn’t fixed yet. How do I open a support ticket?

gwilki · March 31, 2024, 3:38pm

Go onto the sienci support website. The form is there. (I’m assuming that the solution proposed by Kevin the linked post does not work for you.)

MtrDLP · March 31, 2024, 8:06pm

It doesn’t look like Kevin posted a solution. It just looks like suggestions on what a fix might possibly be. I guess I was saw the blurb in the documentation that said it retained the speed setting for recovery and thought “good, they fixed it”, but if it isn’t going to wait for it to spin up recovery is not going to work. I guess if you are using a router with just on/off it is okay.

I guess the kludge fix is start the spindle via command line, wait until it is at speed, then start from line#. It will coast a few seconds so give it a higher RPM via command line so it will be up to speed before movement starts.

gwilki · March 31, 2024, 8:41pm

@MtrDLP I’m likely misunderstanding Kevin’s “solution”. I thought that the said that you could put a dwell code in the start event field in gSender and that would do what you want.

At any rate, I’m sure that you will get results from your support ticket.

CrookedWoodTex · March 31, 2024, 8:49pm

So, if this is something that happens often, then perhaps there are other issues involved?

chrismakesstuff · November 11, 2024, 5:40pm

@MtrDLP if your spindle is set up for ‘spindle-at-speed’ then this should be taken care of automatically, if not then can you point me to the “dwell time” value that you’re referencing it’s missing? Is the dwell time in your g-code or in gSender in the start/stop g-code settings

espresso-shot · December 31, 2024, 10:40pm

I’m also having this issue where there’s no 5sec delay when I “start from line,” here’s the relevant settings page in 1.4.11

Spamming_Eddie · January 1, 2025, 9:31am

Hi Michael,

Here is the relevant manual for the spindle.

Does a spindle even work with spindle/laser toggled off?

espresso-shot · January 3, 2025, 4:28am

Got it, it appears I misunderstood a few things:

The spindle/laser toggle is to enable/disable. I thought it was to choose either spindle/laser.
This toggle is for the manual spindle control tab.
Reading the other thread, it sounds like this issue is due to spindle delays not being parsed with “start from line”.

Does this delay impact only manual enable/disable of spindle, or will it also add time between “start from line” spindle speed command and first movement? If it doesn’t, should I add a delay to the program start/resume event, or should I manually startup the spindle and wait for it to come to speed before “start from line?”