I will wait for few days more for better firmware. I think I have more problems with image2 code than with Marlin.
Perhaps becouse I scaled down the pictures? If I leave images for laser to be 200mmx150mm the laser needs 5 hours and thus troubleshooting takes a lot of time. I would really like to get the images with laser as the ones in previous posts…
I tried meanwhile to make a square with gradient. PNG didn`t work , only when I converted to jpg, image2code created proper gcode.
I was using the 1.1 version from here, but I think they are all the same.
1-For me Where the “F” command is placed has no effect on the program. but if you move it to the end of a “G” command it works perfect.
[attachment file=33621]
[attachment file=33622]
2- The resolution/spot size is pretty extreme. It is defaulting to .18mm with is the theoretical min and .23 being the average size. Changing this allows for a much smaller file size and seems to be a faster F value. Link to the info I found https://jtechphotonics.com/?product=2-8w-445nm-9mm-laser-diode-component.
3-With the full graphic LCD running F1300 (21.67mm/s) is the fastest I could push it with a resolution/spot size of .23mm before the LCD refresh caused stuttering. With the regular reprap lcd I could go to 1800, Might have to put these back up for sale in the shop. With no LCD selected in the firmware I never get a stutter but it seems to not move any faster than about 1800, I can only guess the “slowdown” buffer safety kicks in at that point.
I think this is the number that should be used and the laser strength adjusted accordingly. Or less.
Hello to all who reads this!!! Regarding modifications of the software, the version that is published here or on github, do not generate code for Windows 7 64 bit but work on 32 bit system. Can anyone fix this? and I found an error, if the feedrate to try to introduce the letter then the program immediately closes with an error.
This post details my investigations to date of the problem where Image2Gcode doesn’t produce the correct GCODE when the pixel is black, instead it produces M106 S0. This has been reported before for example
and I have certainly found that the program reliably sets the power for gray and white but doesn’t cope with black. I have reported one workaround by increasing the gamma function but thought there was probably an underlying programming issue.
After acquainting myself with Visual Studio and C# (yet another IDE and language!) I have discovered the following. The data relates to the software on GITHUB (https://github.com/Uthayne/3dpBurner-Image2Gcode) although this is the source code for V1.0 dated Mar 7 2016. The version Ryan recommends now is Version 1.1 but I can’t find the source for that.
Clearly the program correctly acquires the image and then produces a grayscale image as is evident from the display. The problem comes with producing the gcode. On lines 818 and 865 there is the if statement:
Color cl = adjustedImage.GetPixel(col, (adjustedImage.Height - 1) - lin);//Get pixel color
sz is subsequently used to set the M106 S gcode. cl.R is the value of the red component of the relevant pixel.
As a quick and dirty test if I amend these lines to if (cl.R <= 0.0 * 255) { sz = 0; } then the program only encodes M106 S0 once very early in the code sequence and appears to work correctly.
I am unclear what the relevance of cl.R being <= 38.25 but in all my investigations to date blacks are encoded with R,G and B = 0 and the alpha component being 255 (e.g in Inkscape). It is of interest that the original program on the 3DPBurner GITHUB
doesn’t have these 2 if statements.
I don’t know if Leo69 or @uthayne are still active on this board but I would be interested in their comments as they modified the original program
Is there a guide for dummies? I have tried to burn some images but it usually ends up in a square that is 1/4" by 1/4". It seems I have to scale the image by 1000% to get anything larger than 1" by 1". I am sure I am doing something wrong.
I am using Marlin and was wondering if you could ditch the parens you use in the generated gcode? Parens are taken as errors so this is an error (Generated by 3dpBurner Image2Gcode v1.0)
(@Sep/22/2017 03:40:14)
Now if you want to add comments like that to the gcode just put a semi colon at the start of the comment so in this case before each line as such ;(Generated by 3dpBurner Image2Gcode v1.0)
;(@Sep/22/2017 03:40:14)
edit: Another real error is a dangling F for feedrate as there needs to be a G1 Fxxxx to set a global feedrate (or set it per axis but no need for that for this).
G28 X Y
G90
G21
F600
G0 Y112.05; Move to top left corner and begin box
The above is some of the code and see that F600? It is a flat out error so the feed rate is never ever set.
Consider these a very simple request and really easy to implement so more can use this software and I thank you for the continued work on this.
edit: I just found something else that is an error “G1 X0 G1 Y0” that extra G1 is an error and it should be G1 Xx Yx and in this case would be G1 X0 Y0. I think a button added for these changes would be nice and make it so it has a broader user base.
For anyone who needs the change to the G1 command (only really need it when using diagonal) load up notepad++ (in windows) and hit ctrl-h. Check the regex radial button so it turns black (it is at the bottom of the search box we opened with ctrl-h) and in the search put this exactly (G. X.?) G.( Y.?) Mind you the spaces. In the replace with put this $1$2 and the gcode file will be Marlin ready. While in the notepad++ don’t forget the other two things and just do those by hand. I have a 19meg gcode file and this takes a dang long time on even a Ryzen 1600 OC’d (I was wondering if it had crashed honestly) so I hope the author implements the changes I mentioned.
Regex can do anything. It can even do magic, if you’re a wizard.
Other places that regex works are with atom (the editor), sed (part of Unix), Python, perl. If you want command line tools like sed, awk, grep in windows, I can say that mobixterm and cygwin both work very well.
