After 14 Month of perfect function: Error 7871 all the time

[Roman]

Hello Art
More than a year ago we had a long conversation to get Auggie running after an error (http://gearotic.com/ESW/FavIcons/index.php?topic=1980.0).
Since then flawless operation and I did not touch anything. Just used it.
Now suddenly I get an error stop (7871) every time I try to burn. GCode files I burned the day before without any problem do now this stop.
I have no idea where to search as there was no change. I switched off in the evening, started again in the morning and there it was.
Of course I tried several times, restart everything etc. No change.
When the failure happens the machine goes very fast about 20cm to the right on X and then stops.

I attach pictures of the errors.

Do you have a hint where I shall search?
Thanks a lot for any help. I need this to work again.
Roman

[ArtF]

Hi Roman:

Sorry for the trouble. I know your previous problem was due to something in the lookahead system.
The error your getting is non descript. The error number is a report that the last thing it did was a successful
execution of a script, then it failed.
  Have you tried setting back the lookahead to a low number like say 50 as a test? You may want to turn off the
spindle library to see what the effect is.. I suspect a call is being made that is confusing it and Auggie is
terrible at reporting errors, its so thread busy that finding what actually caused an exception is difficult.
When it suddenly stops runnign like that though, its likely that something in the profile has set to a wonky
number. Do you have any backups of the profile data file that you can copy in?  I do recommend when you
have a working system that you backup the folders so you can revert it if necessary as the profile will
change as it records your last state settings. A Gcode file may have changed a setting to something
bad that its missing.

    We'll have to narrow it down , perhaps by testing MDI codes to see what line it is that causes the trouble,
or what its doing then failing..

Art

[Roman]

Hello Art
The first thing I did is that I went down to lookahead 100 (normally running at 300). No effect.
Yes, I have backups of everything.
Will now
- Reload Profile from Backup
- Turn off Spindle Lib  (You means SpindleLib-Laser under GCode Scripts? Isn't this essential for Laser usage with Auggie?
- Try to run it slower, means 500 instead of 1000mm/sec

Will report back any observations.

Thanks for your help

Roman

[ArtF]

Roman:

  Yes, you need the spindlelib for actual laser, but its sometimes usefull to
run with the system only thinking the laser is on if you can arrange it. I usually go
about it by eliminating what I can.

  On the other hand, the profile contains pretty much everything that can crash a system
other than its scripts.. so replacing the profile will probably do it.

Art

[Roman]

Hello Art
I left Lookahead at 300 and also everything else as it was.
So the very first thing I did now is run the file at only 500 mm/sec instead of 1000 mm/sec. Works perfect, no fault. The Queue flickers at 299/300/301.

So it must be something speed dependent I assume. Of course I would like to be able to go back to higher speeds.

Roman 

[Roman]

Hello Art
After 500mm/min I tried 600, 700, 800, 900, 1000. At 1000 it crashes. Repeatedly. Went back to 900 and it does not crash. Repeatedly.
There is nothing else running, ther is enough CPU and enough Memory.

No clue.....

Best regards
Roman

[ArtF]

Roman:

Sorry for the delay in answering.

  I think of two things, acceleration, and jerk setting. They are codependant and may be the likely
source of the problem. Try with a lower jerk, or a higher jerk. Then try with higher or lower accleration.
Getting accel and jerk right is Auggie can be hard as few understand the real relationship there,
try a few experiments at 1200 velocity with high or low jerk to see if it makes a difference.'

Art

[Roman]

Hello Art, me again...

The above problems where meanwhile all solved (new, faster Computer probably solved it. Fingers crossed).

Somehting else I observed now by chance:
I cutted a thin masking foil. On straigt, faster moves the foil was cut just like it should. Courved, slower sections: no cut, just little burn. If I raise the power or lower the spead the curved lines ar cut just right, but the straight ones are overdone, burned.

Means that the linear relationship between actual speed and Auggie-regulated laser power is not good here. Is there a way to influence this?

Best regards
Roman

[ArtF]

Hi Roman:

Error 7871 is a macro C string execution error. Did you recently modify a script or macro?
Its a generic error, all it really tells me is the macro system executed a string in the C interpreter,
and then after it was sent for execution, something crashed. Id check my macros.. when does it happen?
Does it occur at startup, or when you try to run a file?

>>Courved, slower sections: no cut, just little burn.

The selection of "DistanceCorr" on the main screen turns on distance correction, which adjusts power to
be equal to the actual motion speed, its meant to remove as much as possible the slowdown in curves and corners
to stop them from burning. Is it on? I think there are a couepl settings as I recall that set a minimum amount
of motion time before firing.

I haven't run Auggie in a while, but I started mine up just now tro check it all still works here. I really must
get back to using my lasers..

Art

[Roman]

Hello Art

The Eroor 7871 is solved since a longer time. I tried so many things that I do not remember....

I just apendend to this old conversation the new question regarding the speed/laser power corelation.
Yes, the "DistanceCorr" is on. Because I thoght this is one of the 'essences' of Auggie ... :-)

Best
Roman