Sword wrote:I haven't tried this yet, but just a thought I had when first reading it. Vectric products can save a 'Job Sheet' in html format.... Could this somehow look for this file and if present, open it for viewing? Would be kind of nice if it opened in a stand alone window instead of a browser in this case. Possibly adding a line to your PostP file that would ask if you would like to see it or not when loading a file. Just some thoughts on making use of this.

What kind of html is it? Does it contain pictures or just a description? Is is a fixed file name or the same as the g-code?

Hi Dezsoe . YES you have pictures and not code. I was asked to NOT post code that could only run in dev versions as it it confuses users that do NOT run that Version. THEN they email Balazs as to WHY it does not work . THAT just addes to Balazs work load which he does not need.

When UCCNC get further along in Developement I will release a TON of Wizards,macros,Plugins,etc that were developed/tested and gives UCCNC some of the special features OTHER CNC controls have that UCCNC does not.AND may give UCCNC features that others do not have. OR UCCNC may choose to apply them as internal features of UCCNC just like teh big boys have.

UCCNC needs to grow at a controlled rate.

Until then I respect teh wishes of UCCNC and you just get pictures to SHOW it can be done. And if you can figure it out from there go for it.

Just a thought but when you do this it may be best to rely on your cam to assign teh reference picture the same name as teh Gcode program is.

Test123.tap Gcode programTest123.png Picture file.

Then from the macro you can query teh Gocde file NAME and change teh extention to call teh Picture file into play. That way teh M130 macro can be generic in nature and it works for all files without having to add in the ( reference file path). Also it would be best IF UCCNC had a dedicated folder to place all teh reference picture files into. That way the macro would KNOW exactly where to look for the picture file.

C:\UCCNC\ReferenceFiles

We have been doing this with Sheetcam for years now as Sheetcam can produce a PNG file that shows the part. It uses the SAME filename for both the Gcode file and the png file. The ext is different of course.

That way YOU do not have to remember what Picture file is related to a particular Gcode program.

ALSO I did teh reverse feature where you look through teh Reference file folder images and found teh part and autoloaded teh Gcode program into UCCNC. Most time I can remember what teh part looked like BUT not what I called it. So if I find teh correct image then I know what teh file name should be because teh names are teh same.

Yes! Aaaaand! If you name the image file the same as the g-code then I can change the macro to look for that file. The advantage is that it would not use any function that is not in the latest stable release (1.2047), so it could be run on that version too.

(Terry, the needs are different. I really hate anything that is fixed. While you like to have things in fixed folders, I prefer having them anywhere, but together. My jobs are sorted in a folder structure, so I would be very dissatisfied to store pictures in one folder and other files in another etc. And what I wold dislike the most is to store any data in the UCCNC folder! I almost never store programs and data on the same disk.)

Hi Bezsoe, I do understand how you think . Years ago I made a small fortune straightening out machines that teh Operators were allowed to store Program files anywhere across a LARGE corp server system. Sometimes they would get to teh point that they could not make anything because no one knew where everyone else ended up putting the files to make parts.

SO after some very expensive visits to fix it it was EASY to get teh IT dept to LOCKOUT machines and everyone getting to do their own thing with files.

Gcode went into a dedicated Gcodes folderSubs went into a dedicated Subs folderMacros went into a dedicated Macros folderPlugins went into a dedicated Plugin folderetcetc

From that point on EVERYONE knew exactly where teh files they needed were.

I like teh way that LESS over at Sheetcam did with sheetcam. You have teh option of assigning dedicated directories for all teh processes or doing it your way.

When I generate my gcode, Fusion creates automatically the same image shown in the top right corner of this setup sheet showing the placement of the work offset and the stock in transparent around the part.The image is named the same as the gcode file.

Fusion also has the option of generating tool image and linking them in the gcode with M130 before each tool change! But I haven't managed to have Fusion generate the tool images and I don't know how. Images aren't generated but M130 is present for the tools.