flatcam

Open full view…

Offset problem between G-code files

vag_01
Wed, 17 Oct 2018 11:57:30 GMT

Hello, I created 3 G-code files that are perfectly positioned on the FlatCAM (8.5) screen. One is for the tracks, the other for the edges and the third for the holes drilling. The Gerber files have been created with KiCAD. When I import them in WinPC NC, they shift by some millimeters between them. This makes that the drill holes are not at the right place for instance and the edges are cutting in the middle of the tracks. Of course the origin is exactly the same for the G-code 3 files in WinPC NC. I repeated the operation for multiple times and had always the same problem. Any idea on what I could do wrong ? Thank you

Marius Stanciu
Wed, 17 Oct 2018 17:22:31 GMT

Hi, Try to contact the guys from WinPC NC and asked them what they see that is happening when importing the G-code from FlatCAM. Maybe they expect a certain format, perhaps a number of decimals. I think that it is likely to be a bug on their side, I have not encountered such a behavior with FlatCAM. I used the GCode output from FlatCAM with bCNC and with MACH3 with no problems. You can also try to use the FlatCAM Nightly X64 version that I post in the topics below and see if the problem can be reproduced using this version, too. It has many improvements over FlatCAM 8.5. You could also post here the files through a file-sharing site (Dropbox, Mega, online sites etc). so we can have a look.

vag_01
Wed, 17 Oct 2018 19:38:26 GMT

Hi Marius, Thank you for your reply. I submitted the question to the WinPC NC support. I tried the FlatCAM Nightly X64 version, but on my system it generates some weird shapes around the tracks and quite far away from them. So for the moment I cannot try any G-code exported from it. In the meanwhile, here is a copy of these 3 files: https://www.dropbox.com/sh/n96vw5qq69satd0/AADMg1syNPU1P6EBoe3plgjOa?dl=0 Thanks again

Marius Stanciu
Wed, 17 Oct 2018 20:19:54 GMT

Most likely it's a problem with the WInPC NC software. Attached is a picture with your GCode files fused together and loaded in MACH3. As you can see everything is OK exactly as in FlatCAM (nightly). Regarding the issues you had with the Nightly I would appreciate if you can post a few screenshots depicting the issues, also the version used. It will help me iron out the bugs because for me it works without problems. [Mach3](//muut.com/u/flatcam/s3/:flatcam:2owR:mach3.jpg.jpg) [Nightly](//muut.com/u/flatcam/s1/:flatcam:4U6p:nightly.jpg.jpg)

vag_01
Thu, 18 Oct 2018 07:19:49 GMT

Hi Marius, I tried several times to reproduce again the weird shapes, with FlatCAM (nightly), without success. I was using version 12102018. Maybe it had something to do with my PC. The only difference was a reboot in between. Anyway, if it happens again, I'll post a print screen. I didn't had yet the opportunity to export G-code with version 16102018, that I just installed. I'll post the results as soon as I test it with WinPC NC.

Marius Stanciu
Thu, 18 Oct 2018 08:53:25 GMT

Hi, I think Juan said at some point that he had issues with the vispy branch of FlatCAM (on which Nightly is based) if the PC was going to sleep (or hibernation). I don' t remember if the app itself was active when sleeping or just because the PC was waken up from sleep / hibernation and FlatCAM was launched. But, my bet is that the Win PC NC interpret something wrongly because the GCode from FlatCAM is plain GCODE. Who knows, perhaps it needs spaces between X,Y coordinates or whatever else.

vag_01
Tue, 23 Oct 2018 06:26:59 GMT

Hi, I contacted the support of WinPC NC but there is no answer from them. I don’t think that there is a real “support” with that software. Anyway, in the meanwhile I continue my trials... After having installed the Nightly build 19102018, I still have the same problem: an offset of a few millimeters on the drill G-code file only. I also tried merging the 3 files in one (the F.Cu, edge cuts and drill), by simply adding them one after the other in a text editor. When I open then the merged file in WinPC NC, everything is correctly placed like on your picture Marius. The only problem with such a file is the fact that it doesn’t stops to allow me changing the tool, while 3 different (tools) are needed for it. Of course I could manually add a line to stop in G-code, in order to change the tool, but this is not the most efficient way of working.

Marius Stanciu
Tue, 23 Oct 2018 09:16:19 GMT

Hi, Unfortunately Gcode is just plain text and I can't see the issue myself therefore there is little I can do to help you since I also don't have access to your Gcode sender software. What you can do is: - try to use a different FlatCAM postprocessor and I mean instead of using the Default one use the manual_toolchange postprocessor - try to adjust the Gcode by removing the commentaries from the beginning (everything inside the parenthesis () ) - try to remove the space in between the X coordinates and Y. Actually try to remove all the spaces on each line For your trials you can create a matrix of holes, each at 1mm distance of each other, or a square that you will isolate. A simple shape so it is easier to debug. You can do this in your CAD software and import Gerber/Excellon in FlatCAM or directly in FlatCAM by creating an Excellon object in Excellon Editor or by drawing a square in Geometry Editor and then generating GCode. You can edit the Gcode directly in FlatCAM, there is that possibility, too, and then save it.