Vertical Raster feature needed

[BCChad]

Thank you for your code, which gives me good results. My suggestion - the raster lines run horizontally in the x-direction. When a piece requires me to rotate it 90 degrees in the machine, the raster lines now are vertical which is not always a pleasing look. It would be good to have a feature option to run the raster lines in the y-direction.
Thank you.

[rktech-de]

Hi, because of other changes I need, I did the GCode generator completely new, but it now is also possible to change also the scan direction (tab: G-Code, config: Scan image lines ...). If you like you could be my first external tester of this new code.
Take a look here: https://github.com/rktech-de/Inkscape

[BCChad]

Yes, thanks. I am happy to test this. Did you see my additions of dwell (G4), and scaling the the laser power S? I find the latter was marginally useful. Bruce

…

On Sat, Jan 8, 2022, 1:53 PM rktech-de ***@***.***> wrote: Hi, because of other changes I need, I did the GCode generator completely new, but it now is also possible to change also the scan direction (tab: G-Code, config: Scan image lines ...). If you like you could be my first external tester of this new code. Take a look here: https://github.com/rktech-de/Inkscape — Reply to this email directly, view it on GitHub <#34 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJNU5OB2UWIJGHYGSPKUWX3UVCBZBANCNFSM5H76IJ2A> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[BCChad]

First impression - it loads well into inkscape, and the features are impressive. I'll be busy trying these out (enthusiastically!). So it is for Inkscape .92 or should it also work for 1.1.? I know I was having problems with png.py in Inkscape 1.1 Thanks for now, continuing... Bruce On Sat, Jan 8, 2022 at 7:40 PM Bruce Chadbourne ***@***.***> wrote:

…

Yes, thanks. I am happy to test this. Did you see my additions of dwell (G4), and scaling the the laser power S? I find the latter was marginally useful. Bruce On Sat, Jan 8, 2022, 1:53 PM rktech-de ***@***.***> wrote: > Hi, because of other changes I need, I did the GCode generator completely > new, but it now is also possible to change also the scan direction (tab: > G-Code, config: Scan image lines ...). If you like you could be my first > external tester of this new code. > Take a look here: https://github.com/rktech-de/Inkscape > > — > Reply to this email directly, view it on GitHub > <#34 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AJNU5OB2UWIJGHYGSPKUWX3UVCBZBANCNFSM5H76IJ2A> > . > Triage notifications on the go with GitHub Mobile for iOS > <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > or Android > <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. > > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

-- Bruce Chadbourne 306 Fern Circle Lebanon PA 17042

[rktech-de]

it is for inkscape 0.9x, that's the version I'm currently using, I'm sure currently it will not work with 1.x but I will do this if later on, when I know the new GCode generator is working fine.
Waiting for your response...
Rainer

[rktech-de]

if I get you right, the dwell time should be awaited after each scanline.

Then this could be added to the "Start of line code" configuration. For example this G-Code configuration:
"Init code" = G90 G21{NL}F{FEED}
"Post code" = G4 P400{NL}M2
"Start of line code" = G4 P400{NL}G0 X{XPOS} Y{YPOS}
"Power level change code"= G1 X{XPOS} Y{YPOS} S{POWT}
"Minimum laser power value" = 0.00
"Maximum laser power value" = 10000.00

this will create the GCode like this (for a 2mm thick vertical line):

G90 G21
F800
G4 P400
G0 X-10 Y0
G1 X0 Y0 S0
G1 X2 Y0 S10000
G1 X12 Y0 S0
G4 P400
G0 X-10 Y-0.2
G1 X0 Y-0.2 S0
G1 X2 Y-0.2 S10000
G1 X12 Y-0.2 S0
... (and so on)
G4 P400
M2

Or maybe the "distance for acceleration" setting will help you. This will generate a (short) distance at the beginning and the end of a scan line in the same direction while the laser is switched off. this will allow the machine to accelerate to the Engraving speed, so the energy (gray level) for each dot is constant. It will also prevent the laser be switched on when the g-code parser of your machine already calculate some deceleration and curves when going to the next line. So maybe the G4 is not needed any more with a sufficient distance setting.

BR
Rainer

[BCChad]

Hello, Here are my comments thus far, in no particular order 1. Comment to self - I am unfamiliar with the M62, 63, 65, 66, 67, 68 digital controls. This may give me additional capability I don't understand right now - my system is MACH3 with a "simple" Genmitsu 3018-MX3 control board (non GRBL). Please tell me a little about this aspect of your implementation. 2. Resolution steps - I suggest adding 3,4 pixels per mm (as I did in my fork) - easily done.. Perhaps also 7 or 8. 3. FLIP X, FLIP Y - the gcode is flipped but not the preview .PNG - consider the advantage (or confusion, if not doing it) 4. Full Page - with it selected you print everything in the page, as I expect. With it unselected, you printed objects outside the page boundary, even though they were not selected. Is this intentional? 5. Scan image lines - I like the feature, and the different options. However- my 40x48mm test image was oriented at 0,0 at the left bottom corner. When I selected "Zig zag Y", it started the image at x47 and finished at x86 - something buggy here. Some of the other options were also offset to the right. 6. My system presently does not utilize M62...etc. I used the "Power Level Change Code" field and modified it to use the M03 S command. This works, however there is no POWER OFF (M5) command found in the code. I think the laser should be off when traveling(?), such as the 10mm acceleration zone you have implemented? (Perhaps I need to understand better). Thank you, so glad that you are working on this

…

-- Bruce Chadbourne 306 Fern Circle Lebanon PA 17042

[rktech-de]

Hi Bruce,
Now we are talking here about my fork in this foreign repository, could you please put your comments as separate issues in my fork-repository? THX

[BCChad]

Yes, will do that later today.

…

On Mon, Jan 10, 2022, 3:17 AM rktech-de ***@***.***> wrote: Hi Bruce, Now we are talking here about my fork in this foreign repository, could you please put your comments as separate issues in my fork-repository? THX — Reply to this email directly, view it on GitHub <#34 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJNU5OCGCC3Y3FO7CS6ADWLUVKIZ3ANCNFSM5H76IJ2A> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>