Almost there: Laser reacts strange around 1% power (and traps for beginners)

Discussions and file drops for Auggie
Roman
Old Timer
Posts: 31
Joined: Wed Nov 06, 2019 4:07 am

Re: Almost there: Laser reacts strange around 1% power (and traps for beginners)

Post by Roman »

Hello Art
I tried it but no effect: 150 lines maximum.
The only idea I have now is to erase it totally and start a clean install from scratch.
Will be back.
Best regards
Roman
User avatar
ArtF
Global Moderator
Global Moderator
Posts: 4591
Joined: Sun Sep 05, 2010 6:14 am
Contact:

Re: Almost there: Laser reacts strange around 1% power (and traps for beginners)

Post by ArtF »

Roman:

Let me know how it works out , and what version the installer claims its installing...

Art
Roman
Old Timer
Posts: 31
Joined: Wed Nov 06, 2019 4:07 am

Re: Almost there: Laser reacts strange around 1% power (and traps for beginners)

Post by Roman »

???

Hello Art
Happy new year!
After hours of trying I am at a total dead end now. It worked perfect before I tried to overcome this 150 Line look ahead limitation. Since then: Install evrything from scratch, several times, Pokeys ax movements perfect but from Auggie just a big bang on the machine when I tried to move any axes (all started for 1/10 second at the same time). Reinstall, redone profile, re done Pokeys setings etc, etc. At the end (and I have no clue why) the axes suddenly moved smooth.
So happy-happy. But....
Today I wanted to load GCode, the same I already burned without problems with Auggie 10 times before the above mess.
It shows for every line loaded an Error-19, then Error -31, then Error -19 and so on. And It show's sometimes 'Warning Cutter comp ignored'.
Or alternatively it tries to load the Gcode and then does immediately a program crash without any error. It stops and shows a few seconds again the Profile selection window.
The Version is 3.65M

I have no clue where to search any longer......

Any help is highly appreciated.

Best Regards

Roman
User avatar
ArtF
Global Moderator
Global Moderator
Posts: 4591
Joined: Sun Sep 05, 2010 6:14 am
Contact:

Re: Almost there: Laser reacts strange around 1% power (and traps for beginners)

Post by ArtF »

Hi Roman:

  Its late here.. I will look up those errors and see whats up in the morning.

IF you try to use G43, you'll get an error because Auggie doesnt use Tool compensation.
Are you sure you used that program before? You still cant set anything above 150 lines
as well? Can you tell me the version showed by the installer as it installs? (It should never
hurt to reinstall Auggie.. it wont change any settings typically. ( Though you should always
keep backups of any scripts youve written just in case.)

Art
Roman
Old Timer
Posts: 31
Joined: Wed Nov 06, 2019 4:07 am

Re: Almost there: Laser reacts strange around 1% power (and traps for beginners)

Post by Roman »

Hello Art
- Re-installed several times, also with first compleete removal of the Geraotic directory. It installs 3.65M
- No G43 in the GCode, example attached below
- It also does not work with GCode created with Auggie itself from a picture
- Either it shows 'WARNING: Cutter Comp Settting Ignored' and 'Cuttter Comp Ignored' and immediately crashes
OR
- it shows the code but for every line an error 31 (Zero Feedrate on Arc) and then Error 19 (Axis word in G80 Mode)

Look ahead works, I can set it as I want.
Lib: all Skipts are set to on , except in GCode where only the laser is set on and the other two Spindles are off
I tried also again with a blank Profile, no effect. And I am missing the 'Laser Screen' you once mentioned in one of the Videos. I have my onw which worked perfectly before.

This is the simple GCode generating immediate crash as well:

( Auggie l?uft nicht test1 )
( File created: Friday January 03 2020 - 04:28 PM)
( for Auggie by Roman Korn )
( Material Size)
( X= 110.000, Y= 110.000)
()
(Toolpaths used in this file:)
(Schnellgravur 1)
(Tools used in this file: )
(Laser)
N100G00G21G17G90G40G49
N110G71G91.1
N120T1M06
N130 (OptLaser PLH3D 6 Watt  {0.00393701 Inch})
N140S2000M03
N150(Toolpath:- Schnellgravur 1)
N160()
N170G94
N180X0.000Y0.000
N190 G00X3.840Y2.406
N200 G00
N210 G1
N220 G1Y-6.594
N230 G1X-15.660
N240 G1Y2.406
N250 G1X3.840
N260 G00
N270 G00X0.400Y7.399
N280 G00
N290 G1
N300 G2X-10.758Y-3.759I-11.158J0.000
N310 G2X-21.915Y7.399I0.000J11.158
N320 G2X-10.758Y18.556I11.158J0.000
N330 G2X0.400Y7.399I0.000J-11.158
N340 G00
M05
N360 G00X0.000Y0.000
N370 M09
N380 M30
%

Thanks for any help. Actually I can not do anything with my laser until this is back to where it was before.

Best Regards

Roman
Roman
Old Timer
Posts: 31
Joined: Wed Nov 06, 2019 4:07 am

Re: Almost there: Laser reacts strange around 1% power (and traps for beginners)

Post by Roman »

... Additional info:
I took out the standard G40 (stop cutter compensation) at the beginning of the GCode and tried: The error messages 'Cutter Comp setting ignored' are not displayed anylonger but it still crashes immediately.
Roman
Old Timer
Posts: 31
Joined: Wed Nov 06, 2019 4:07 am

Re: Almost there: Laser reacts strange around 1% power (and traps for beginners)

Post by Roman »

.. Additional Info 2:

I found an old copy of Version 3.65A
Installed it. Only difference: It does not crash immediately and it shows only errrors 31 on each line. There is not even an arc in this Gcode. (see attached screen copy)
And the look ahead is not changeable as it was in 3.65A which started the whole journey :-)


Attachments

[The extension has been deactivated and can no longer be displayed.]

User avatar
ArtF
Global Moderator
Global Moderator
Posts: 4591
Joined: Sun Sep 05, 2010 6:14 am
Contact:

Re: Almost there: Laser reacts strange around 1% power (and traps for beginners)

Post by ArtF »

Hi Roman:

  Thx for that test file , it showed the error and its been repaired.

  When Auggie see's a problem, the -x number represents an internal error
check. HEre is a l;ist of what a number means, just negate the number shown
(so error -5 is actually number 5 on this list..)

const string  ErrorStrings[] =
{
"Successful completion. ", //0
"File not found. ", //1
"Command Canceled. ",  //2
"ToolPath File Error in Create. ",  //3
"Mapping Error on Toolpath. ",  //4
"Error Parsing File. ",  //5
"Line too Long. ",  //6
"Engine pointer failure. ",  //7
"Parse Error. No command. ",  //8
"Parse Error. Missing number after word. ",  //9
"Parse Error. Variables not allowed. ",  //10
"Parse Error. Multiple Parameters. " , //11
"Feedrate Error. ",  //12
"SpindleSpeed Error. ",  //13
"Tool Change Error. ",  //14
"Exceeds limit of 1 G-Group per line",  //15
"Bad G-Code" , //16
"Inappropriate FeedMode Call",  //17
"Illegal MCode" , //18
"Axis words in G80 mode",  //19
"Axis words missing in G92",  //20
"Two GCodes that need Axis words used",  //21
"Motion with no axis info",  //22
"Unknown Motion code" , //23
"G10 must have L2, L1 not supported",  //24
"G10 must have P= 0-255" , //25
"G68 needs X,Y and R",  //26
"G68 cannot be used with G10L2Rnn",  //27
"G10 L2 cannot share with G68/G69",  //28
"IJK and R missing in Arc", //29
"IJK and R mixed in Arc", //30
"Zero Feedrate on Arc", //31
"Zero Feedrate on Line", //32
"No FWord in inverse time move", //33
"KWord in XY plane", //34
"IWord in YZ plane", //35
"JWord in XZ plane", //36
"No Plane Selected", //37
"No XY in Arc on XY Plane", //38
"No XZ in Arc on XZ Plane", //39
"No YZ in Arc on YZ Plane", //40
"R Arc with start/end identical", //41
"R Arc radius too small for endpoint", //42
"Zero Radius Arc",  //43
"Radius different from start and end in Arc",  //44
"I,J or K with no command requiring them",  //45
"End By Rewind",  //46
"Subroutime Missing name", //47
"Error in intermediate file", //48
"Duplicate Subroutine name", //49
"Error opening intermediate file", //50
"Missing MCode support",//51
"Missing GCode support",//52
"Scripted Stop",//52
};

  Let me know how this 3.70 version works. I did find that I could change the
lookahead without error, but there was a feedrat ebug due to recent fixes in other areas.
Sorry for the bug.

Art
Roman
Old Timer
Posts: 31
Joined: Wed Nov 06, 2019 4:07 am

Re: Almost there: Laser reacts strange around 1% power (and traps for beginners)

Post by Roman »

Hello Art, you where up early today. Thanks a lot..

I installed and I tested Geraotic and Auggi 3.70 (after removing all traces of Gearaotic and Auggi with a special uninstaller).
Following observations:
- When I start it for the very first time, create a first, empty profile (do nothing in the EngineConfig) and select the 'PoKeysMotion screen': It works, GCode is read correctly, all fine.
- When I then copy my Profile file and my Hotkey file (to Profiles) and my screen file (to Screens) it does not work any longer. Same errors as described above.
I re-created the profile but without effect. Jogging etc works perfect. Only reading in GCode does not work.

Attached are the 3 files, mybe it helps to find the error.
Thanks a lot
Attachments

[The extension txt has been deactivated and can no longer be displayed.]

Roman
Old Timer
Posts: 31
Joined: Wed Nov 06, 2019 4:07 am

Re: Almost there: Laser reacts strange around 1% power (and traps for beginners)

Post by Roman »

The files all renamed so I can post them here
Attachments

[The extension txt has been deactivated and can no longer be displayed.]

[The extension txt has been deactivated and can no longer be displayed.]

[The extension txt has been deactivated and can no longer be displayed.]

User avatar
ArtF
Global Moderator
Global Moderator
Posts: 4591
Joined: Sun Sep 05, 2010 6:14 am
Contact:

Re: Almost there: Laser reacts strange around 1% power (and traps for beginners)

Post by ArtF »

Roman:

  I cant seem to load your screen, it may use panels or controls you made? The screen file doesnt contain them
if so, but the profile errors out loading bitmaps for some reason.

It may be your error is coming from your profile as it stores the last gcode state,
so it can happen that your in some strange feedmode or G mode thats sticking.

What error are you getting when you load the Gcode?  What happens after it loads, any display on the toolpath?

Art
Roman
Old Timer
Posts: 31
Joined: Wed Nov 06, 2019 4:07 am

Re: Almost there: Laser reacts strange around 1% power (and traps for beginners)

Post by Roman »

Hello Art
I repeated now everything and did not touch any of my previous screens, Profiles etc.
- Total blank Auggie Installation from scratch
- Profile name given: Test1
- Auggie starts. I select screen 'PokeysMotion'. It displays some fileds just in grey, see attached picture
- I can import GCode just fine, no errors all good.
- I close Auggie and start it again, same Profile Test1, Screen PokeysMotion comes up, some fields are grey.
- I try to import GCode: Error 31 at every line. See attached picture.

Removed the whol installation and did it again: 100% same result.

So this happens with a total virgin installation, no Roman screen nor profile used.

Difficult....

Best Regards
Roman
Attachments

[The extension has been deactivated and can no longer be displayed.]

Roman
Old Timer
Posts: 31
Joined: Wed Nov 06, 2019 4:07 am

Re: Almost there: Laser reacts strange around 1% power (and traps for beginners)

Post by Roman »

and here is the Logfile from the second start of Auggie where G-Code could not be imported any longer
Attachments

[The extension txt has been deactivated and can no longer be displayed.]

User avatar
ArtF
Global Moderator
Global Moderator
Posts: 4591
Joined: Sun Sep 05, 2010 6:14 am
Contact:

Re: Almost there: Laser reacts strange around 1% power (and traps for beginners)

Post by ArtF »

Thx Roman:

Ill try the same test here and see what I get..

Art
User avatar
ArtF
Global Moderator
Global Moderator
Posts: 4591
Joined: Sun Sep 05, 2010 6:14 am
Contact:

Re: Almost there: Laser reacts strange around 1% power (and traps for beginners)

Post by ArtF »

Roman:

  It seems a feedrate bug has slipped in on startup. Your feedrate DRO is zeroing. This will be a two
stage fix. First, Ive updated the screens to reflect changes over the past year. You shouldnt get any more
blank spots on the screen. I suggest you load the Pokeys Motion Screen after install, then save it under a name you like
and reselect that name. That way future updates wont corrupt your screen.

  Until I fix the Feedrate bug, just type a feedrate into the DRO, and reload the Gcode.. should load OK..

Ill have the feedrate fixed shortly.

Art
Post Reply

Who is online

Users browsing this forum: No registered users and 82 guests