GearHeads Forum

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

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

The files all renamed so I can post them here

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

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

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

Thx Roman:

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

Art

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

Hello Art

I downloaded, installed and tested it. Findings so far:
- The PokeysMotion screen included in the actual download does not contain the Laser Panel any longer. But now instead the milling spindle panel. So I tried my old, own Laser Screen again.
- My old, reduced Laser Screen (which was based on the former PokeysMotion) works just fine.
- Yes, when I first started Auggie I had to set the feedrate as it showed a zero. But I had to do this with two decimals, so enter i.e.  '1000.00' or it would not accept it.
- Form the second Auggie start onwards the '1000.00' was pre-filled in the DRO and now can be changed without entering the two decimals. Just i.e. '2000' and it takes it and displays '2000.00' in the DRO.

I will test the real motion and burn something later today and will give feedback.

Thanks a lot and have a nice Sunday.

Roman

Hello again


[font=Verdana]UPDATE: Does not work again, very strange errors, see next post[/font]

Testing done, It all works with my reduced Laser Screen, I am back to play

On thing observed is strange: When a Gcode execution has ended, without error, image burned then some messages run on the xcreen for a long time. It is always the same message, written out about 20 to 50 times.
See the screen copy attached.

Thank you and best regards
Roman