Additional utility

Want something added to the software or web-site?
daedelus
Site Admin
Posts: 377
Joined: Tue Oct 01, 2013 1:41 pm
Location: London, UK
Contact:

Re: Additional utility

Post by daedelus » Sat Oct 19, 2013 5:13 pm

My fault with downloading the zip. I messed up some stuff when I moved the files from my old host. The zip works fine now.
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

Zig
Posts: 27
Joined: Wed Oct 02, 2013 12:29 pm

Re: Additional utility

Post by Zig » Sun Oct 20, 2013 9:29 pm

I hope the information is sufficiently indicative of utility requirement.

Zig
Posts: 27
Joined: Wed Oct 02, 2013 12:29 pm

Re: Additional utility

Post by Zig » Sat Oct 26, 2013 2:13 am

Any comments..opinions.. ideas?

Anybody...?

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

Re: Additional utility

Post by daedelus » Sat Oct 26, 2013 11:02 am

I am itching to get stuck in to the 'toolpath optimiser' but I figure I should make a decent gcode parser / library first. This will not only make the optimiser easier to make but I can also use the library to improve the autoleveller.

To cover all bases, I have ordered a 2nd hand book on gcode through amazon, and despite the fact that it dispatched on Thursday, it quoted the delivery estimate as 19th November. If this is true then they must be circumnavigating the globe a couple of times before they deliver.

My thoughts on the opimiser are that it not only needs to rearrange the toolpaths but also needs to optimize the cuts within a toolpath to alter the starting point. This is so that it can find the nearest point in a toolpath from a previous path and not the nearest starting point of a path 'as is' (before optimising).

It sounds to me that JayC focused on the original start point of a toolpath, which kept everything nice and simple as there was no optimising of the original toolpath to be done but caused some of the issues you raised before.
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

Zig
Posts: 27
Joined: Wed Oct 02, 2013 12:29 pm

Re: Additional utility

Post by Zig » Sun Oct 27, 2013 9:36 pm

Getting the library organised would be the right step.
Not only would it make later work easier but the initial effort of building up the library would help crystalise the problem and necesary algorithms to resolve issues.
What language do You program in?

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

Re: Additional utility

Post by daedelus » Mon Oct 28, 2013 9:01 am

I like Java so will probably do everything in that. In my opinion and from a software engineering point of view Java is very flexible in that it allows me to use the tools and techniques that I rely on very easily. Tools such as JUnit and techniques such as design pattern usage.

Having said that, I realize a fast GCode parser could be useful in many low-level and embedded systems such as various control boards, and they might prefer a C / C++ version. I can always re-write it in those languages if nesessary. :)
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

Zig
Posts: 27
Joined: Wed Oct 02, 2013 12:29 pm

Re: Additional utility

Post by Zig » Mon Oct 28, 2013 7:42 pm

I have ot uttered a sylable of Java in the past ten years. I still say a few things in ( embedded ) C now and then.
If You think You need a sounding board I may be able to say a few less than sage things.

Post Reply