HTML Comment Box Messages

Discuss all things

Moderator: Country_Bubba

Post Reply
daedelus
Site Admin
Posts: 387
Joined: Tue Oct 01, 2013 1:41 pm
Location: London, UK
Contact:

HTML Comment Box Messages

Post by daedelus »

The following are all the HTML Comment Box messages which were on the main page. I have removed them from the main page but you can review them here if you need to check the history:

On 2013-09-26 19:52:22.595150 by pknoe3lh

Thanks for your help!
It was not so easy to get the formula right ... i think it took you a long time! People can be happy to have it!
I will spend you a coffee ;-)
greetings Patrick
On 2013-09-26 10:21:20.310280 by Daedelus1982 (mod)

Fantastic Patrick,
Anyone using Marlin will be more than interested im sure. Kobus mentioned Marlin a few comments ago in fact.
On 2013-09-25 23:11:51.078280 by pknoe3lh

Autoleveling is working ;-)
github.com/pknoe3lh/cncgcodecontroller/wiki/CNC-GCODE-Controller
On 2013-09-23 23:51:35.624140 by pknoe3lh

@Daedelus1982
I don't know why ... maybe becaus of http://www.indiegogo.com/projects/fabto ... fabricator
Its like "i have a 3d Printer too O_o i also want to mill something^^"
I have a Proxxon FM70 and add the reprap electronics for controlling (because i already had it)
But there is a big intrest anyway: http://www.reprap.org/wiki/PCB_Milling

Thanks a lot for the hint! I will try what i can achieve ..
greetings Patrick
On 2013-09-23 14:18:19.086940 by Daedelus1982 (mod)

@Patrick, Looks like a really good bit of software. I had not heard of Marlin a week ago but two people have mentioned it in a week now.

With regards to how my AutoLeveller works... its all about bilinear interpolation. Have a look at interpolateX() and interpolateY() in probe/probe.java on GitHub. These methods essentially mimic the formula found here: http://www.eng.fsu.edu/~dommelen/course ... ds/intpol/.
On 2013-09-23 11:26:38.200120 by Patrick

subscribed
On 2013-09-23 11:22:18.609970 by Patrick

Hello

Im working on a solution for reprap
The Problem is that Marlin (or others ) is not very smart => you need the host Software to do it for you! (inteprate hit endstop)
Im working on a software https://github.com/pknoe3lh/cncgcodecon ... Controller
Auto Level is not supported yet but i will try to implement it!

Daedelus1982: Can you give me an overview how you make it that i can implement it in the controller (it would just be for reprap community) i dont want to go through all troubles ....
On 2013-09-20 12:56:25.557430 by Daedelus1982 (mod)

The GCode, in short probes an area and stores the results in variables. These probe points tell me where Z0 is for each of the probed points despite any uneven parts of the surface material.
Then when it comes to the actual etching stage it uses these probe points to work out where the Z height SHOULD be and make the necessary adjustment. Where you see the #102, #101 and #100 lines in the GCode those are the actual bilinear interpolation formulas used for the working out. For the linear interpolation formula, see: http://www.eng.fsu.edu/~dommelen/course ... ds/intpol/.
Therefore, for every X Y coordinate in the original file, I have 4 points (the probe points) round it where the Z is known and these points are used in the formula.

I am new to GRBL myself and have no idea how to write or read to an external file in it.
On 2013-09-20 11:44:33.577990 by Kobus

I am still learning all these things. Now I also know it is GRBL. Just need to figure out what that means :)

If you can point me in the right direction I can write a converter maybe to convert what you produced to something we can use.
I had a look at your gcode. What does it actually do? I am thinking I need to execute your gcode to do the probing and then I need to write the results to a file so that your app can use the results again to translate. I am not seeing how everything fits together
On 2013-09-20 09:18:56.766510 by Daedelus1982 (mod)

@Kobus,
I just did a quick search for Marlin and it tells me its a firmware derived from GRBL amongst others. So, by 'complicated' I presume you mean it doesnt accept variables (#xxxx)? Which is the same problem that Henrik had with GRBL. So, I may be able to add a seperate file or something in the future. Not sure whats possible yet. Sorry I cant be of immediate help.
On 2013-09-20 06:43:56.144360 by Kobus

Hi

The gcode that it outputs seem a bit complicated. Is it possible to create a version that will run on Marlin from the RepRap community?

Kobus
On 2013-09-19 14:48:23.622500 by Daedelus1982 (mod)

@Henrik,
I have only just added the code to GitHub (2 or 3 hours ago) and I have only just started with Git myself after using SVN for several years. Most generated GCode does not use loops or variables etc. so I guess GRBL works fine for most cases.
Anyway, if you or anyone have any questions about the code or any bugs to report etc. (maybe I should refactor and add some comments to make it clearer) let me know.
On 2013-09-19 14:10:02.124820 by Henrik

@Daedelus1982
Thanks for your answer, GRBL has the limitations on running on an Atmega328 and it only has 2k of ram, so i dont think it doable there.
But if you are the man its surely nice to have. GRBL philosophy is that it will only do 'generated' code in the terms of no loops and precalculated values.
I found your code on github (I didnt know about that yesterday), It will be much easier for me to fork your code and tweak it since its plan java and not mad c.

Henrik
On 2013-09-18 15:28:55.123180 by Daedelus1982 (mod)

@Henrik,
Right at this moment I am not at all familiar with GRBL, I see what you are saying though and I do have plans for a log type file at some point anyway.
It might be easier if I chip in with the GRBL project and add support for variables at some point.
As I say, I am not familiar with GRBL at the moment but I do have some experience with AVR chips. I will look into it. thanks.
On 2013-09-18 10:36:28.023670 by Henrik

Hi a real cool piece you have made!
Im using GRBL as controller software and its not capable of using variables.
I have implemented a probing mechanism (G38.x) to get height values form GRBL and they are reported in the log.

So I was thinking if its possible to generate one file with the probing grid and take the log as an input and generate a second file with hard coded auto leveled values in?

I know it gets a little awkward, but thats the price you have to page when you are using a simple controler.'

Henrik
On 2013-09-15 12:09:08.397940 by Country Bubba

Herman,
Which version of Windows are you using?? You may need to place the program in some other folder than the "program files" as later versions of windows is very jealous of anybody except windows writing to that folder!

art

On 2013-09-14 09:57:54.267280 by Daedelus1982 (mod)

@Herman,
Very confusing. You got it working with Mach 3, but you are getting a message saying that the file is incomplete whenever you try to install it in program files?
The file is standalone so there is no install program. The best thing to do is create a shortcut to it then add the shortcut to your start menu. Not sure why it tells you the file is incomplete though. Maybe re-download it?
On 2013-09-14 08:43:36.145820 by Herman

The program works fine with mach3. It is amazing how the smallest height differences are detected
and corrected. I want to install the program permanently to use it for all pcb work. However for some reason I cannot
install a working edition in my program files.When I open the file I get a message that the file is not complete.

On 2013-09-04 20:35:53.350960 by alain

now download the lasted version and see that all works great now must looking now he zero not on x0 y0 buth before al the rest works wonderfullllllllllyyyyyyyyyy thanks i tested it on greater pcb's also
great job MIKE
On 2013-09-04 20:35:34.932920 by alain

now download the lasted version and see that all works great now must looking now he zero not on x0 y0 buth before al the rest works wonderfullllllllllyyyyyyyyyy thanks i tested it on greater pcb's also

On 2013-09-04 20:28:09.242640 by Daedelus1982 (mod)

Thanks Alain, Email me at daedelus@autoleveller.co.uk or report them here if you need any help with any issues and troubles.

All, I have not stopped with AutoLeveller, I am currently trying to add the source to GitHub. Just need to sort out some GPL licensing issues first. I shall announce and link to the source here when it gets there.
On 2013-09-04 20:06:19.744070 by Alain

works it perfectly in mach3 i have troubles ????? buth wonderfull software :) :) :)
On 2013-08-30 12:04:40.618040 by Daedelus1982 (mod)

Fantastic, thanks Mike.
Thanks for the info about the linuxCNC version. I have only ever used the version thats on the live ubuntu / linuxCNC CD so didnt know that. I shall add that to the site ASAP.
On 2013-08-28 06:07:39.511960 by Mike

Working well for me once I upgraded to linuxCNC 2.5.x. that is a minimum requirement that I'm not sure is mentioned on this page. Very well done! I did a SMD board on my Zentoolworks 7x7 the other night for the first time.
On 2013-08-23 20:00:25.925130 by Daedelus1982 (mod)

@Gashmore,
Thanks for the comments, really good to hear.
If you use a touch plate you generally don't use the Autoleveller software I would expect. You just use the plate to probe once to find the Z height and thats all. And you generally do that with the original GCode file and directly from Mach 3. Maybe I misunderstood your setup but yes, if you did use the Autoleveller, you should be able to edit the 2nd G92 to the touch plate thickness.

Hope this makes sense.
On 2013-08-22 12:11:40.383380 by Gashmore

Great program! I am cutting PCBs on a home brew 24"x48" router. The bed is MDF so squareness can vary a few thou with humidity. Not a problem with wood but bad for PCBs. Autoleveller solved my problems. One request though. How about adding a touch plate offset? I am engraving face plates in plastic sign laminates and Autoleveller would make them much cleaner.

Alternately, would editing the G92 to the touch plate thickness work?
On 2013-08-21 20:08:02.740800 by Daedelus1982 (mod)

I have added a 'probe guide' (link at the top of this page) if you need any help setting up a probe.
On 2013-08-19 21:13:13.040490 by Daedelus1982 (mod)

@Shannon Haworth,
Not yet but I plan to release it shortly.
Right now I've got half about half a dozen projects on the go.
Currently I'm working on a probe setup tutorial since a number of people requested one.
On 2013-08-19 19:42:45.743340 by Shannon Haworth

Is the source available?
On 2013-08-18 23:07:41.103320 by Juank

Hi when I press donate button the browser send to the paypal login and no more optons, if is possible send me your email of your paypal acount to send the donation
On 2013-08-15 20:18:24.430370 by Daedelus1982 (mod)

@Juank,
Thanks for the feedback and the intentions. I believe after you click on 'Donate', you just enter any donation amount you want and login to your paypal account or enter your credit card details.
I didnt fix the amount but I'm really not expecting much. If you want a guideline, I would be more than grateful for £5 even.
Hope this helps a bit. Let me know if not.
On 2013-08-13 04:23:07.734850 by Juank

How Can I donate to you? I pressed the button but I only enter to my paypal acount
Your work is great
On 2013-08-05 20:54:25.657450 by Daedelus1982 (mod)

@Adam,
You are correct P refers to the coordinate system and can be 0-9. However, whilst some sources tell me that P should be in the range 0-9, others seem to say 1-9. Maybe you have a different version of linuxCNC to me but since this line only occurs twice at the beginning of the file, try changing P to 1 at these lines for now. P1 is G54, P2 is G55 etc.
On 2013-08-05 17:07:34.474860 by Adam

My original issue was that my PCB was too small. I've designed a larger board now for testing and I am having another issue. When I load the file into linuxCNC (after running Autoleveller) I get the error that "P value out of range of G10 L2 or G10 L20" When I check the line number, I have "G10 L20 P0 Z0" I thought P could be anything from 0-9. Thanks for the help!
On 2013-08-05 10:34:20.807810 by Daedelus1982 (mod)

@Nigel,
It will detect the board size but you can change the X, Y, X length, Y length values to whatever you want. Smaller or bigger. I'm not sure why you would need to make the probing area bigger than working area since there are no cuts to autolevel beyond this point? But you can.

If you want to engrave some text on the circuit for example, you can add the text to the end of the file, then run it through the Autoleveller.

With regards to repeatability, I have plans for a future version to save the probing results to an external file so that you have the option of reloading that into your post-processor, this way you can avoid re-probing and you can still use the same (half-milled) board if it went wrong last time.

It could me more difficult to probe outside pads and traces especially if the circuit is complex and there are lots of traces close together for example, but I will have a think :-)
On 2013-08-05 09:49:45.258120 by Nigel

Hello Daedelus, I've got a couple of interesting questions for you. Repeatability? Last night I was routing a board and found that whilst probing, the tape had given way lifting the board in one corner. I hadn't realised this and started cutting and halfway through cutting found out the board had lifted, not sure of when of course and pressed it back down. The trouble then is then when cutting in that area, I had a massive air cut missing the board entirely.

Because the probing area itself includes the confines of any traces and pads, the board was lost as re-probing the board isn't an option.

Would it be possible for the autoleveller to probe outside of any traces/pads so that if the need arises to probe again, it can be done?

Also, another thing, the circuit I was cutting was to be the same size of the board i.e. use the whole board for an LED panel. When autoleveller runs, it automatically detects the working area of the cuts to be made but doesn't take into account the size of the board. Would it be a possibility to include an optional option that takes that into consideration?

Thanks.
On 2013-08-05 09:48:08.745320 by Daedelus1982 (mod)

Hi Sean, I suspect you just need to update Java. Type "java -version" in the terminal to find out what your current version is. Mine says.. java version "1.7.0_09"
Go to: http://java.com/en/download/index.jsp and install the latest Java, see if that helps.
On 2013-08-05 06:37:59.006540 by Sean Greven

Trying to get this to work, however Java is complaining about a major.Minor version number (I am using a MAC) 0.7.3 as well as 0.7.4
java -jar Autoleveller074.jar
Exception in thread "main" java.lang.UnsupportedClassVersionError: autoleveller/Autoleveller : Unsupported major.minor version 51.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)
at java.lang.ClassLoader.defineClass(ClassLoader.java:615)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)
at java.net.URLClassLoader.access$000(URLClassLoader.java:58)
at java.net.URLClassLoader$1.run(URLClassLoader.java:197)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:249)
at org.eclipse.jdt.internal.jarinjarloader.JarRsrcLoader.main(JarRsrcLoader.java:56)
On 2013-08-04 18:27:35.249010 by Daedelus1982 (mod)

Hi Adam, yeah, its those Not a Number (NaN) lines I expect. I need to fix it when I get a chance. Another user had the same problem when the Probe spacing value in Autoleveller was bigger than the area to be milled. I think that the default 'probe spacing' is 0.375" but if your X and/or Y length is smaller (lets say X length is 0.3 and Y length is 0.2) then make the 'probe spacing' 0.125. Regenerate the output and check there are no NaN lines. If this does not help, please email me the pcb-gcode file to daedelus@autoleveller.co.uk. Thanks.
On 2013-08-04 16:16:27.124930 by Adam


I'm running pcb-gcode 3.5.2.11 with all the default values and I am getting the same error with both version 0.73 and 0.74 of your Autoleveler. The error is as follows:
"The milling area is not contained by the probing area. This is OK but, only the probed area can be levelled."

When I load the resulting file into EMC,. I get the following error:
"Near line 18 of <path to file>: Unknown word where unary operation could be."

My code looks ok to me. Here is everything from line 18 and above:
(Autoleveller Software, Version: 0.7.4)
(Copyright 2013 James Hawthorne PhD)
(Original file: untitled.bot.etch.tap)
(Creation date: 04/08/2013 time: 12:09)

(prerequisites)
(1. need a working probe)
(2. tool needs to be within 3/8" of copper board for the 1st probe, )
(i.e. Z0.000 should be no more than 3/8" above the board initially)
(Note: The first probe will touch off Z to 0.000 when it first touches to copper, )
(all other probe values are relative to this first point)

G20 (Inches)
G90 (absolute distance mode, not incremental)

(begin initial probe and set Z to 0)
G0 XNaN YNaN Z0
G38.2 Z-0.375 F5


On 2013-08-01 09:01:50.852110 by Daedelus1982 (mod)

@Anonymous, I think you are right. IMHO though, all GCode files should explicitly state the units if only for clarity. Maybe I should add a default when reading the input file into AutoLeveller, but then what should the default be. I shall have a think. Thanks.

On 2013-07-31 21:29:14.837310 by Anonymous

@Daedelus1982, I suppose Mach3 use the default units when units are not specified in the Gcode, I have make a test loading the file with imperial units by default and my board size become 250x125 inchs!!! ;) so I think here the explanation. May be an option into the software mask (inch or mm) in case the units are not explicited in the Gcode file can fix this problem?


On 2013-07-31 20:40:43.418130 by Daedelus1982 (mod)

Hi Carlos, just sent a reply to your email. I assumed that all GCode generating software must add either G21 or G20 otherwise your control software will not know whether the numbers are millimeters or inches. For example if a line contains X1.25, is that 1.25 inches or 1.25 millimeters? I am confused. Still, the main thing is, it works. :)
On 2013-07-31 19:09:34.654570 by Carlos

Hello!!! Adding the G21 word and setting the probe distance it WORKS!!! Tonight I will try to make my CNC driver version 2.0 finally routed with a CNC!!! You are a GENIUS!!! Thanks a lot for this gift!!! for sure i will donate!!! Thank you a lot again!
On 2013-07-31 17:23:09.191100 by Carlos

@Daedelus1982, Thank you for the fast response, i have sent you the e-mail with the gcode and two screenshots. I have added the G21 command to the code and the program recognize the unit and dimensions but when you try to generate the code it says that the milling area is not inside the probing area.
Thank you


On 2013-07-31 09:20:54.517600 by Daedelus1982 (mod)

Hi Carlos, thanks for the interest, the GCode file should contain a line which is either 'G21' or ' G20', which tells it all the units are in millimeters or inches respectively. I would find it strange if these lines were not there and you should add one or the other if you can. It is more likely that something else is causing the problem however, so can you email me the coppercam GCode file so that I can have a closer look: daedelus@autoleveller.co.uk.
I am very keen to fix these 'core' problems as an immediate design goal of AutoLeveller is that it works with any GCode created from any software.
On 2013-07-31 00:11:23.980340 by Carlos

Hello, first of all thank you for the great job! I am trying to use the software with a gcode file generated by coppercam, when I try to open it in autoleveller the software do not recognize the units and any othe parameter, just only the board size on the right window, and then it can generate the probing code. What can I do for fix this problem? I have to add any line at the gcode?
Thankyoi so much for your time.
On 2013-07-21 21:48:16.262230 by RickW

I would make it an option, or make it min(3/8, probe-spacing). You could have "advanced options" to keep from adding to the number of basic options.
On 2013-07-21 20:43:28.501100 by Daedelus1982 (mod)

Hi Rick, the software does indeed sub-divide long segments but the user cannot change this value currently (I am trying to reduce the number of options given to the user and therefore make it easier to use). The probe spacing has little to do with segment length and represents the distance apart the probe points are during the probing stage only. When it comes to milling, each segment is divided if it is longer than 5mm for metric gcode files and 3/8" if the original file is in imperial. Therefore you should never see a segment in the output which is greater the 3/8" and you can conceivably have 0.1 probe spacing and 3/8" segment length. If you think 3/8" is too long, let me know and I can add an option to change it. Bear in mind though that the output file size will increase if the segment size is reduced.
On 2013-07-21 16:53:44.760670 by RickW

When you generate the gcode from the original, do you sub-divide long cuts so that the maximum cut doesn't cross a probe point? It doesn't appear that that happens. I have the probe spacing set to 0.1 in., but I see cuts that are much longer. The problem is that this can miss changes in board height as one cut may go past a probe that had a height change. I'm using version 0.7.4 and pcb-gcode 3.5.2.11. Is there a setting I should be making to correct this?
On 2013-07-18 20:27:07.638740 by Daedelus1982 (mod)

Hi Rick, thanks for the interest. The best answer is, yes its probable but depending on circumstances, it may not be possible. By keeping it closed for now, I am keeping my options open.
On 2013-07-18 18:35:16.544460 by RickW

Are you planning to open source this software?
On 2013-07-18 00:52:07.345270 by KenH

Hello James, you should have a email with test results of version 0.7.4 - You've sure been making progress!!!

Ken H>
On 2013-07-15 10:08:41.975840 by Daedelus1982 (mod)

Thanks Ken, got it
On 2013-07-14 21:22:27.452760 by Ken H>

A file will be in the mail shortly<:) ken h>
On 2013-07-14 20:14:34.002750 by Daedelus1982 (mod)

Thanks guys, I cannot take credit for the new look web page though. The design and layout was done by a friend.
Ken, could you email me an F-Engrave GCode file, pre-autolevelling? It would obviously be better if you or anyone else did not need to do any tweaking. :-)
On 2013-07-14 16:30:45.184850 by Ken H>

New website layout looks good. Hope the home move is going good. I've ran PyCam, F-Engrave, and pcb-gcode files thru AutoLevel and they all work good. F-Engrave files need a bit of tweaking, but nothing drastic. Keep up the GREAT work.
Ken H>
On 2013-07-14 12:47:17.145650 by Country Bubba

Like the new layout:}) I think it is better organized and more logical.

On 2013-07-10 10:25:47.444890 by Daedelus1982 (mod)

Uploaded version 0.7.3. This is the most robust version yet. Removed all previous versions.
On 2013-07-04 16:04:29.305840 by Anonymous

Not sure what the deal was - maybe I wasn't doing the first Z touchoff correctly with the PyCam file, but this morning it's working just fine. GREAT program. I downloaded the new 0.7.1 version and the PCB-Gcode.upl gcode still has the "Y-6.0E-4" type error. Not really a big deal to change, but I'm sure you'll have it with next version, OR - perhaps it's something to do with the way I created the brd file?

Ken H>
On 2013-07-03 23:04:28.211640 by KenH>

Sure, I'll be happy to email those files to you. with you providing all the effort you are to help the world in CNC work - I'll be happy to help anyway I can. I'll have the files a bit later tonight.

Ken H>
On 2013-07-03 08:12:03.313450 by Daedelus1982 (mod)

@Ken H>, Looks like I have a copy of issues to iron out here. The numbering issue should be easy enough to sort but not sure yet about the pyCam issue. The "Probe is already tripped when starting G38.2 or G38.3 move" error usually appears if contact with the surface is made before when it is not expecting it, but the probing code should be identical to the PCB-GCode probing code apart from the X and Y coordinates.

Would you be able to email me the original files from PCB-GCode and pyCam? My email: daedelus@autoleveller.co.uk. Thanks.
On 2013-07-03 02:09:59.783650 by Ken H>

I didn't finish the error msg: "with gcode from PyCam, it loads, but on first probe it halts on error "Probe is already tripped when starting G38.2 or G38.3 move" This stops the program and I'm not sure how to proceed from there. Any ideas?

Thanks again for all your hard work,

Ken H>

On 2013-07-03 02:01:39.461950 by KenH

Thanks for all the work you've done on this program. I ran it today and it seems to work - well, after I did a bit of tweaking on the code output. I used code from Eagle's ulp PCB-Gcode.ulp and it works, BUT - there were a few places where the result was listed as "Y-6.0E-4" value that prevents LinuxCNC from loading the gcode. I can edit those places to "Y-0.0006" and the gcode will then load and run just fine. Is there a trick to preventing this from happening?

Also, with gcode from PyCam, it loads, but on first probe it halts on error.

Thanks again for the work.

Ken H>
On 2013-06-30 08:16:51.844180 by Daedelus1982 (mod)

@Nigel, Thanks very much. Really glad the software helps.
I also had trouble getting the .jar working in Linux. linuxCNC runs on Ubuntu 10.04 by default. Since this is an outdated version it seemed difficult to get the latest Java JRE version and hence it didnt run in my Linux either. When I figure it out, I might upload a short tutorial on how to do it.

On 2013-06-29 19:30:26.603190 by Nigel

Just had another go with it. Simply fantastic, much better now. As far as I can see, the divide by zero issue is gone. Also, I used it to produce a double sided PCB. It was a small board so placing the probe ground was difficult but doable. The ability to adjust the probe size so that it's smaller than the cut out board is brilliant as it means you can probe ONLY the board area. I did try getting the .jar to work on linux, but I couldn't but that's only because I don't actually know how to use linux, I only got it for linuxcnc. You shall definitely be getting a pint on me!
On 2013-06-29 13:34:23.709780 by Daedelus1982 (mod)

New version (version 0.7) now available. Click the download links to get it
On 2013-06-29 07:13:45.097080 by Giuseppe

mail
On 2013-06-28 20:21:25.939900 by Daedelus1982 (mod)

@Giuseppe, Thanks, would you be able to send the complete two files to daedelus@autoleveller.co.uk.
That is... the original GCode file and the output file from the autoleveller software.

On 2013-06-28 19:41:42.078980 by Giuseppe


Original code

%
G90
G21
G17
G00 X2.4994 Y6.5985 Z5
M3
F1200
G01 Z0
F200
G01 Z-0.15
F1200
G01 X0.8993 Y6.1698
G01 X-0.2719 Y4.9985
G01 X-0.7006 Y3.3985
G01 X-0.2719 Y1.7985
G01 X0.8993 Y0.6272
G01 X2.4994 Y0.1985
G01 X4.0994 Y0.6272
G01 X5.2706 Y1.7985
.............

F1200
G01 Z0
G00 Z5
G00 X-68.5978 Y-55.7987
G01 Z0
F200
G01 Z-0.15
F1200
G01 Z0
G00 Z5
M5
M02
%
On 2013-06-28 15:55:04.140640 by Giuseppe

the gcode was created with that but then I have to work on a machine that has Mach3 and parallel port
On 2013-06-28 13:02:45.478450 by Daedelus1982 (mod)

@Giuseppe, OK thanks, I think I see the problem. I shall work on a fix for that. I thought USBCNC included its own 'autoleveller' though? Called 'Warp'?

On 2013-06-28 12:38:47.952990 by Giuseppe

USBCNC
On 2013-06-28 12:26:57.533330 by Daedelus1982 (mod)

@Giuseppe, Which program generated the original GCode file? PCB-GCode?

On 2013-06-28 11:21:10.452150 by Giuseppe

The correct line should be
G01 X-35,0001 Y-18,0366 Z[#100 + -0.15]
I saw that the lines are all wrong with the decimal value of Y = 0 for example :

G01 X-1,5481 Y16.0 Z[#100 + -0.15] ,7307
G01 X20,2945 Y3.0 Z[#100 + -0.15] ,9913
On 2013-06-28 11:08:17.488080 by Daedelus1982 (mod)

@Anonymous, Not really sure how this could happen, I shall check. Was '0366' in the original GCode file?

On 2013-06-28 11:03:44.230520 by Anonymous

MACH3 Bad character usedline
G01 X-35,0001 Y-18.0 Z[#100 + -0.15] ,0366
if i deleted 0.366 MACH3 is OK
On 2013-06-28 09:00:02.849010 by Giuseppe

opened!! installed JAVA Version 7 Update 25,
Now I try to create the gcode and milling, thanks again
On 2013-06-28 08:37:31.385160 by Daedelus1982 (mod)

@giuseppe, the 'jar' file is executable, there is no need to unzip it. You should be able to double click it the same as the 'exe'. It was provided for non-Windows users but since you are using Windows just stick with the 'exe'. It is exactly the same.

Unfortunately I am unable to replicate the issue you are having, but possibly I am using some later functions of Java in my code. Maybe you should try Java 1.7 or whatever the latest version is then go to 'http://www.java.com/en/download/installed.jsp' to verify. At the time of writing, I receive the following message when I verify 'You have the recommended Java installed (Version 7 Update 25)'.

On 2013-06-28 08:07:10.414340 by Daedelus1982 (mod)

@Shannon Haworth, To be honest I haven't decided yet. It depends on several factors but in general I am in favor of open source software so this is a big possibility.
On 2013-06-28 08:04:06.095600 by giuseppe

hello, thanks for the reply
I tried it on two different PC OS Windows XP - Windows VISTA,I do not work on any machine.
I also downloaded from the link Autoleveller.jar, I Autoleveller download. Zip
I unzipped the file I can not find autoleveller.jar but only junit.jar - vecmath.jar - org.hamcrest.core_1.1.0.v20090501071000.jar.
Probably something wrong, I thank you for the help
On 2013-06-28 03:21:04.759540 by Shannon Haworth

Any plans to release the source? Thanks!
On 2013-06-27 17:18:55.802530 by Daedelus1982 (mod)

@Giuseppe, Not sure about this. Which OS are you using? Have you tried it on other machines? Does it work on them?

On 2013-06-27 17:03:15.134360 by Daedelus (mod)

@Nigel, Thanks, I have found these 'divide by zero' errors myself recently and have fixed the issue for the next version which should be released shortly. The problem occurs when a milling point lay exactly on a probe grid line, so if you change the x and y probe settings so that you probe an bigger area than the job, you should be able to get round the problem. Try different values until LinuxCNC stops complaining.


On 2013-06-26 16:03:52.481490 by Giuseppe

Hello, I am very interested in the software that would solve a big problem.
I downloaded the executable file and java 1.6.0 but I do not work, the hourglass appears for a few seconds and then returns the pointer.
Do you have any advice?
thanks
info@gp-project.it
On 2013-06-26 14:19:21.876210 by Nigel

Excellent piece of software, works very well. Very much commended. The only issue I'm having when using the output code with LinuxCNC is a 'divide by zero' error. It crops up quite a bit and is something to do with the board size compared to the x/y lengths.
On 2013-06-18 13:28:57.505100 by Lee

You can find the forum thread for this great app located here: http://www.mycncuk.com/forums/programme ... tware.html
http://www.autoleveller.co.uk/. Software to probe and adjust a GCode file for PCB's or any probe-able surface.

http://www.autoleveller.co.uk/cnc-probe-guide/. A short guide to setting up the probe.

-James
rossjulie
Posts: 1
Joined: Wed Oct 20, 2021 7:24 am

Re: HTML Comment Box Messages

Post by rossjulie »

Those familiar with bootstrap helps a lot with description boxes
Giovanni20
Posts: 1
Joined: Mon Nov 01, 2021 11:32 am

Re: HTML Comment Box Messages

Post by Giovanni20 »

Thanks. The thread will help those who want to review.
MikaelaLinnea
Posts: 1
Joined: Tue Mar 19, 2024 1:12 pm

Re: HTML Comment Box Messages

Post by MikaelaLinnea »

rossjulie wrote: Wed Oct 20, 2021 7:34 am Those familiar with bootstrap helps a lot with description boxes
Moving to Tailwind CSS could improve.
Post Reply