Control Interface version 1.422 Beta

[Pplug]

Awesome! I'm gonna try it tonight!

[dennyz]

I recently installed V1.422beta on my Techno Patriot. I am having a problem with the spindle not turning on (or door locking) when the tool path starts. If I pause the process and resume, the spindle starts up (and the door locks). This does not happen on V1.421.

I also noticed that I am not able to start the spindle manually as I have always been able with earlier versions.

Any suggestions?

[Pplug]

I sent feedback about this problem directly to techno:

Hi folks,

I just d/l'ed the new beta last night and ran a few jobs on it. Earlier I had a problem where the interface would crash when skipping at the beginning of a job. The new beta behaves oddly when doing that. Here is what happened:

I paused a job.
Reset the job.
Pressed start with the mouse.
Skipped to 93%.
Pressed start again with the mouse to advance to the skip point.
The machine went to a part of the job that was not the toolpath and proceeded to drop the the z axis. It would have ruined the material if I did not hit the e-stop.

I had another error on pause but I want to troubleshoot it before I report it.

Thanks guys!

[jmb]

Hey dennyz, we'll take a look. It sounds like a Beta problem, so there's probably nothing you can do right now. Thanks for posting the problem!

Pplug, you opened a whole can of worms with the skipping problem. Apparently, it's an old problem that people just dealt with. Jaime's fixing it now, but it's fairly involved. He'll let you know when we have an updated Beta up.

Oh, and if any of you noticed that the machine would speed up sometimes for apparently no reason (like when pocketing out a circle), that's been fixed in 1.422.52 (thanks Aaron!).

[Pplug]

M3 error on pause is still there! Its a bugger because it's completely random. I also had several interface lockups on skipping and resuming jobs!

[jai123]

Pplug, Randk:
The M3 error seems to be quite random, but I believe I got the source of the problem and I have updated the code respectively.

Due to the randomness of the bug, the fix is really hard to validate. Being the only option that comes to my mind, the release of a new beta and validate that users do not get it anymore. That said, I have released a new beta version in the website, and I would greatly appreciate if you could let me know if the error is gone.

dennyz:
I sent you a private message, please feel free to get in touch with me, and we will further delve on the error that you are experiencing.

Thanks to everyone for your help and time.

Best wishes,
Jaime
---
Techno CNC | Engineering

[jai123]

Hello everyone,

The origin of the Command M3 error has been discovered. The guilty bug is a quite fundamental and ancient bug, which has been in the system before the 421 release was available.

In order to solve the bug, I will need to modify some core things in the system as well as fully test them again. Given this, it has been decided that the bug fix will be included by our next beta release.

I would like to specially thank Pplug, who pointed out the sequence of events that triggered the bug. This was extremely important to find the bug.

Best,
Jaime
---
Techno CNC | Engineering

[Pplug]

What! No prize! Just kidding! Glad I could help.
- chris

[Pplug]

New beta out!

[Dave's_Not_Here]

How is the latest Beta working for everyone?

Thanks!

[Pplug]

No unexpected or undocumented problems here.

[SamoLebon]

I want to know where the option to don't have to uncheck everytime "copy File to Default Directory" when I load a file.

thank you