STUMPED : Slicer sending Garbage Start.g GCode to 1LC toolboard

fcwilt

@sputnikoc3d

What "flavor" of gcode have you selected in Prusa ?

Frederick

SputnikOC3d

@fcwilt

RepRap ... for these examples. reprap / sprinter exhibits same issues tho.

got the error again too

Warning Discarded std reply src=121 RID=4094 exp 206""

Separate issue:

Error: in file macro line 1 M221 Parameter 'D' too high

filament config.g error
M221 S0.94 D121.0 ; set extrusion multiplier

Seems I do not address the E0 toolboard extruder via the 121 prefix. ; super noob

fcwilt

@sputnikoc3d said in STUMPED : Slicer sending Garbage Start.g GCode to 1LC toolboard:

@fcwilt

RepRap ... for these examples. reprap / sprinter exhibits same issues tho.

Odd.

got the error again too

Warning Discarded std reply src=121 RID=4094 exp 206""

Error: in file macro line 1 M221 Parameter 'D' too high

Well that should be an easy error to find and fix.

How about exporting from Prusa the config bundle with printers and post it here. I will import it into my Prusa install and see if I can find what you are doing that I am not doing which is causing the differences we are seeing.

Frederick

SputnikOC3d

@fcwilt

well as much as I appreciate that ... I think Id be wasting your time brother.

Im heading towards your macro methodology. I think long term it will serve me better. Prusa Slicer keeps driving more and more prusa centric interface and stuff into their fork, and Superslicer dev[s] seem agnostic to reprap and lean towards klipper. Being slicer agnostic and having more control over my well being seems prudent. Leaving the slicer to just handle basic slicing and pathing etc and besides Ive been looking closely recently at iDeaMaker. Super Slicer seems pretty nice and familiar as well. The devil I DO know sort of thing.

It seems a small price to pay to merely have to stuff a pair of M codes into the start.g if I still use that - but I think the /macro/Print_Start.g approach is where its at. Id rather spend time ironing out the details of getting that working and porting my filament profiles into that ... Seems like its working that way ... by passing my old way in start.g and using a macro to set all my environment and safeguards myself.

SputnikOC3d

@fcwilt my last code example above that uses the M98 P"Print_Start.g" - seems to have worked and generated some proper gcode.

I just need to get a good Print_Start.g macro written

that said - Im trying to get my head round my filaments config.g. So far here's what I think I need to have in each one.

M221 - extrusion multiplier
M207 - retraction / de retraction / speeds and distances
M568 - nozzle print and standby temps
M140 - bed temps
M572 - Pressure Advance

uncertain items
Input shaping settings ? have no idea how that works yet

Global Var's - not sure what needs to be set and where else they will be used.

fcwilt

@sputnikoc3d said in STUMPED : Slicer sending Garbage Start.g GCode to 1LC toolboard:

@fcwilt my last code example above that uses the M98 P"Print_Start.g" - seems to have worked and generated some proper gcode.

I just need to get a good Print_Start.g macro written

that said - Im trying to get my head round my filaments config.g. So far here's what I think I need to have in each one.

M221 - extrusion multiplier
M207 - retraction / de retraction / speeds and distances
M568 - nozzle print and standby temps
M140 - bed temps
M572 - Pressure Advance

uncertain items
Input shaping settings ? have no idea how that works yet

Global Var's - not sure what needs to be set and where else they will be used.

Well I think I posted most of my print_begin.g file - didn't I?

And the global variables are something that can be used or not. Nothing special about them. In my case it just allowed me to change certain priming/retract settings as needed by different filaments, in the filament config.g file and later use them in the print_begin.g file.

Frederick

SputnikOC3d

@fcwilt - yes I have your macro saved and Im going thru it ... stealing what I understand and incorporating that and finessing my stuff in there - fingers crossed

thanks for all the help.

SputnikOC3d

@fcwilt just went all in on 3.4.0 beta 3 - lol fingeres crossed ..

fcwilt

@sputnikoc3d said in STUMPED : Slicer sending Garbage Start.g GCode to 1LC toolboard:

@fcwilt just went all in on 3.4.0 beta 3 - lol fingeres crossed ..

You are braver then I - I wait until the release version is out .

Frederick

SputnikOC3d

@fcwilt - heres a solution for Super Slicer ...

https://github.com/supermerill/SuperSlicer/issues/425#issuecomment-913036749

found the setting [ if it were a snake it have bit me ]

lukeslaboratory created this issue in supermerill/SuperSlicer

closed Improved G10 Implementation #425

fcwilt

@sputnikoc3d said in STUMPED : Slicer sending Garbage Start.g GCode to 1LC toolboard:

@fcwilt - heres a solution for Super Slicer ...

https://github.com/supermerill/SuperSlicer/issues/425#issuecomment-913036749

found the setting [ if it were a snake it have bit me ]

I like that. Every slicer ought to have that option rather than having to figure which other settings will stop the generation of this or that bit of code.

Good work.

Frederick