Why is Plasmac and QTplasmac pausing at the end of a cut for no reason?

Yeh M67 is the one synchronised with motion. I've used this post before...

That does look odd.

This is using your code as-is, the delay is <=16mS. I could probably do a bit work on that to make it shorter...

snowgoer540 wrote:

Just had a look at the cut file you posted.

Your temporary material line is this:

(o=0, ph=4.1, pd=0, ch=2, fr=2239, th=1, cv=99, pe=0.5, jh=0, jd=0)

pe = Sets the pause at end delay.

So your temporary material is set to have a pause at end delay of 0.5 seconds.

Perhaps it got set by accident, or there is an error in the post?

Thanks for the eagle eyes. I must have the post set to use temp settings. It must be that way by default. I'll check that out. I would not have thought I had a pause in any of my Sheetcam tool settings.

There is still the issues that render QTplasmac unusable. Eg. cycle start issue mentioned earlier. To me thats a worry when the one that works for me is depreciated.

rodw wrote:

There is still the issues that render QTplasmac unusable. Eg. cycle start issue mentioned earlier. To me thats a worry when the one that works for me is depreciated.

I have never seen that issue. Can you duplicate it in a sim.

Really strange I don't get updates despite bring subscribed to this thread.
I have not had any time to revisit this.
Its a bit of a mess right now. Error messages are not being displayed and the default Mint theme does not display Sheetcam's screen controls so its unusable too. The only redeeming thing is the touch screen finally decided to work after an apt-get update.

So until I update the OS, its not going forward,

But if you really want to see a messy software project, you should see a C++ Windows project we are just finishing which integrates an Intel Depth Camera, serial port scales, a Zebra Barcode scanner and a Zebra label printer on the network! The purchased Intel API and the Zebra Barcode API would not play together so we had to use a seperate application to control the barcode scanner and use an IPC pipe to send the data to our application. Now if we can just get Windows give us a correct timezone offset, we have it licked!