Macro for cleaning and purging nozzle

[Exerqtor]

@fcwilt The over all goal with the random part is to split up what purge bucket (left/right) is used so that they don't fill up as fast.

And with that also make it "random" if the scrub starts right to left or left to right depending on where it did the purge.

I'm at work now so i can't look at the code to give an better explanation, but it's the main goal.

[fcwilt]

@exerqtor said in Macro for cleaning and purging nozzle:

@fcwilt The over all goal with the random part is to split up what purge bucket (left/right) is used so that they don't fill up as fast.

And with that also make it "random" if the scrub starts right to left or left to right depending on where it did the purge.

I'm at work now so i can't look at the code to give an better explenation, but it's the main goal.

I hope you will be able to make a quick video or some pictures. I would like to see what the brush and buckets are. I only know them from theory. Never actually seen any.

Thanks.

Frederick

[Exerqtor]

@fcwilt I shot a short clip yesterday before i fixed the bug in line 169. But it shows what i'm trying to do, the clip was with the hotend off since i wanted to check that it didn't try to purge or flipped out while it was cold.

As for the brush and bucket combo it's derived from this: https://github.com/VoronDesign/VoronUsers/tree/master/abandoned_mods/printer_mods/edwardyeeks/Decontaminator_Purge_Bucket_&_Nozzle_Scrubber

[fcwilt]

@exerqtor said in Macro for cleaning and purging nozzle:

@fcwilt I shot a short clip yesterday before i fixed the bug in line 169. But it shows what i'm trying to do, the clip was with the hotend off since i wanted to check that it didn't try to purge or flipped out while it was cold.

As for the brush and bucket combo it's derived from this: https://github.com/VoronDesign/VoronUsers/tree/master/abandoned_mods/printer_mods/edwardyeeks/Decontaminator_Purge_Bucket_&_Nozzle_Scrubber

Thanks.

I see the brush, look like brass but I don't see any little buckets.

What did you use for the brush? Any concerns for damaging the nozzle?

Frederick

[Exerqtor]

Not a video, but it's at least the buckets!

Not really too woried about nozzle wear to be honest, but if it turns out to be a problem other brush types is a posibility

[fcwilt]

@exerqtor

Thanks much.

Now I understand the needs of the process.

Frederick

[Exerqtor]

@fcwilt
Goodie!

As a sidenote, i downloaded the EditPad Pro demo yesterday and it for sure has alot more to offer than what i've been using! BUT, have you made or dug up a syntax highlighting profile for RRF?

[fcwilt]

@exerqtor said in Macro for cleaning and purging nozzle:

@fcwilt
Goodie!

As a sidenote, i downloaded the EditPad Pro demo yesterday and it for sure has alot more to offer than what i've been using! BUT, have you made or dug up a syntax highlighting profile for RRF?

Yes - I have created one - it's not perfect - but anything missing is easy to fix.

You ready to take me up on my offer?

Frederick

[fcwilt]

@exerqtor

Gcode Syntax File for EditPad

Here is the file. I had to add an extension of .txt to get it to upload - just remove the .txt and put it into:

C:\Users\yourwindowsname\AppData\Roaming\JGsoft\EditPad Pro 8

Frederick

[Exerqtor]

@fcwilt said in Macro for cleaning and purging nozzle:

@exerqtor said in Macro for cleaning and purging nozzle:

@fcwilt
Goodie!

As a sidenote, i downloaded the EditPad Pro demo yesterday and it for sure has alot more to offer than what i've been using! BUT, have you made or dug up a syntax highlighting profile for RRF?

Yes - I have created one - it's not perfect - but anything missing is easy to fix.

You ready to take me up on my offer?

I'm tempted, have to test it out a little bit before i decide on anything

@fcwilt said in Macro for cleaning and purging nozzle:

@exerqtor

Gcode Syntax File for EditPad

Here is the file. I had to add an extension of .txt to get it to upload - just remove the .txt and put it into:

*C:\Users\yourwindowsname\AppData\Roaming\JGsoft\EditPad Pro 8*

Don't look like that worked, i've created the filetype Gcode and added " .g;.gcode " file masks. And if i try going to "Colors and Syntax->Customize->Import" it looks for a .ini ?

EDIT:
I found and followed the guide on their website, but it don't pick it up when i refresh. Might be that it's simply left out of the demo or something.

Could you take a screenshot of how the macro we've been working on looks on your end so i can see how it is maybe?

EDIT 2:
Now i got it! Allways fun trying out and learning new stuff ey? #facepalm

[fcwilt]

@exerqtor said in Macro for cleaning and purging nozzle:

EDIT 2:
Now i got it! Allways fun trying out and learning new stuff ey? #facepalm

So you got the syntax file to work?

Frederick

[Exerqtor]

@fcwilt said in Macro for cleaning and purging nozzle:

So you got the syntax file to work?

Yup! Working on trying to get the color pallete to match the DWC editor atm.

[fcwilt]

@exerqtor said in Macro for cleaning and purging nozzle:

Yup! Working on trying to get the color pallete to match the DWC editor atm.

atm??? Automatic Teller Machine???

The syntax editor has predefined palettes which are crafted with usage in mind, not colors, so much.

If you read about the issue in the help for the Syntax Coloring Scheme Editor they talk about the rational behind their system.

Frederick

[Exerqtor]

@fcwilt said in Macro for cleaning and purging nozzle:

atm??? Automatic Teller Machine???

At The Moment

The syntax editor has predefined palettes which are crafted with usage in mind, not colors, so much.

If you read about the issue in the help for the Syntax Coloring Scheme Editor they talk about the rational behind their system.

Can't look at the Syntax Coloring Scheme Editor since it's not included in the demo.

The reason i want it to look like it does in DWC is mainly so that i have one "reference" so to say. Between what i make in my editor and what DWC / RRF does.

[fcwilt]

@exerqtor said in Macro for cleaning and purging nozzle:

Can't look at the Syntax Coloring Scheme Editor since it's not included in the demo.

Yet another great reason to take me up on my offer.

I just discovered a small "bug" in my scheme - but the scheme editor will make short work of it - I think.

The system is based on regular expressions which I have not done a lot with - so I am learning as I go.

Frederick

[Exerqtor]

@fcwilt
Yeah it's getting more and more tempting, not gonna lie!

I saw your syntax profile has some minor bugs that should be pretty easy to iron out i guess. Don't know how "translateable" the syntax highlighting part is from the DWC sourcecode over to that of EditPad though.

Would be nice to make a "solid" RRF syntax and have it uploaded to the database

[fcwilt]

@exerqtor said in Macro for cleaning and purging nozzle:

@fcwilt
Yeah it's getting more and more tempting, not gonna lie!

I saw your syntax profile has some minor bugs that should be pretty easy to iron out i guess. Don't know how "translateable" the syntax highlighting part is from the DWC sourcecode over to that of EditPad though.

Actually I was mistaken. It's the DWC Editor that has it wrong. It threw me off for a bit because mine worked differently. A little more study shows mine is correct - or at least "less wrong".

Consider this from the DWC editor:

The text global.g_tool_exists is the name of a variable and should be all one color - the color assigned to variables.

But the global part seems to be treated the same as if. Both assigned the color for reserved words.

The 0 seems to be treated as a number even though it is part of the variable name

The exists seems to be treated as a function even thought it is part of the variable name.

Now here it is in EditPad Pro

In the second line you can see exists is recognized as a function but works fine as part of the variable name

Frederick

[Exerqtor]

@fcwilt said in Macro for cleaning and purging nozzle:

@exerqtor said in Macro for cleaning and purging nozzle:

@fcwilt
Yeah it's getting more and more tempting, not gonna lie!

I saw your syntax profile has some minor bugs that should be pretty easy to iron out i guess. Don't know how "translateable" the syntax highlighting part is from the DWC sourcecode over to that of EditPad though.

Actually I was mistaken. It's the DWC Editor that has it wrong. It threw me off for a bit because mine worked differently. A little more study shows mine is correct - or at least "less wrong".

Consider this from the DWC editor:

The text global.g_tool_exists is the name of a variable and should be all one color - the color assigned to variables.

But the global part seems to be treated the same as if. Both assigned the color for reserved words.

The 0 seems to be treated as a number even though it is part of the variable name

The exists seems to be treated as a function even thought it is part of the variable name.

Now here it is in EditPad Pro

In the second line you can see exists is recognized as a function but works fine as part of the variable name

Hm yeah i see what you mean, i must admit i prefer the way it's shown in DWC though.

The operators are different in DWC too:

While in EditPad they are all one color.

Given that you're an actual programmer, have you taken a look at the DWC source code for any "pointers"?

[fcwilt]

@exerqtor said in Macro for cleaning and purging nozzle:

Hm yeah i see what you mean, i must admit i prefer the way it's shown in DWC though.

You don't mind that one thing, a variable name, is incorrectly identified and has colors applied to it for four different things - reserved word, variable name, numeric value and function?

Frederick

[Exerqtor]

@fcwilt
Clearly not to the extent it does you

For the record:
@chrishamm said in Making Notepad++ look like DWC g-code editor?:

@exerqtor You can have a look at https://github.com/Duet3D/DuetWebControl/tree/master/src/components/dialogs/FileEditDialog for details about the syntax parsing/highlighting in DWC. Because the current CodeMirror component is rather outdated now, I may eventually replace it with something else in v3.5.

So that behaviour might be something that get's reworked in v3.5.