DXF and GCode correct but showing incorrect on ArcDroid

Sorry ,@Matt_UK - this was meant to be addressed to @ANDREW Miller

Hi @ANDREW Miller,
LatchMount.gcode (5.2 KB)
LatchMount.dxf (14.9 KB)


Hi Andrew and all,
Firstly, thanks for a great product that we use in a school setting. It is a perfect product for us.

We are making progress, but we are having a lot a issues with DXF files doing strange things: This file loads ok but produces random lines as shown on the upload called “dxf”. The DXF file is LatchMount.dxf.

We also have issues with the same project as GCode (LatchMount.gcode). When we load this, we get the error shown on the image called “error”. Note that the DATUM is right in the centre of this file, so this error is hard to understand. Furthermore, you cannot do anything about it - all you can do is press OK but it does not load.

We can open and run this G-code on a number of other emulators, such as CNC Program Simulator and products such as VCarve. I all cases, this G-code file looks perfect but gives an error on Arcdroid.

Finally, I am aware of the G-Code line limit and how to work around that - there has been plenty of discussion on this forum. However, as a programmer and electronic engineering, I am stumped about “WHY” this line limit exists. It seems to be a major limitation. A you wold all be aware - G-Code is just a basic text file, so even the most complex shapes generate a very small. A G-Code file with 100,000 lines (with an average of 30 characters per line) would result in a file size of just 2.9MB. So, clearly, this cannot be a memory issue. If this is true, then what is the limitation? The 3900 line limit (assuming 30 characters per line on average is just 114 KB - that’s tiny. I could fit over 18,000 of these on a 2GB USB Drive (18,393 to be exact). I get that we can make file sizes smaller and reduce tolerances, etc, but please help me understand the actual limitation (and will it be addressed in the future?)

First thing, Welcome to the forum.

I think the message that you are getting is because the part is too close to the Arcdroid.

Try rotating the part 90 degrees using Simple Trace.

I hope this helps.

Happy cutting!

@Cope01

Hey There

Sorry for the delay was travelling in Hong Kong/china for the last week.

My first question is what software are you creating these files in?
I have no problem loading the dxf but the G-code is definitely broken. Not sure why or how to be honest

If you are getting “outside the cutting area” errors check your original drawing for orphan points that are somehow off in the distance.

re the line limit
it is 100% a memory thing. Remember this is not a pc this is an embeded microprocessor with limit onboard RAM. and every motion needs to bee turned into a line of code. AND needs to be resembled on the screen AND needs to have kerf applied (if applicable)
2.9MB is WAY more then we have available to do this. It is not strictly a KB limit of the file and more a Lines of G-code limit

We do not stream from the USB we reassemble the code in onboard memory and fill the motion planner buffer from there.

+We can stream in fact if you go into the diagnostic menu via Settings-Tap logo 5 times ther is some legacy stuff there from 3D printer control this is based on that will allow you to stream a file of Gigabytes. However you lose all the Simple trace functions including the visualization.

That being said the limit is approx. 5500 lines of code which at reasonable tolerances is enough to Fill the screen with cutting. So the vast majority of our users don’t hit the hard limit that often.

Next generation of machine will have nearly 10X the memory on board

Cheers
AM

1 Like

@Andrew will the current generation models be able to be upgraded to to 10x onboard memory or will we need to buy the new machine?

Hi Andrew. Thanks for the reply. Sorry for the delay - I too have been on leave (school holidays), but nothing as exciting as your trip :-(.

This was created using Vectric VCarve and then processed with the VCarve Post Processor from your site VCarve Post Processor. It would be helpful to know if we can resolve this issue; you should be able to reproduce it.

Thanks for the clarification re memory - thanks makes sense. I am an electronic engineer, so I get the issue with microprocessor onboard RAM - I have often had to cut info and recompile code to fit in 2K RAM - no fun, especially when you are within one or two bytes.

It looks like there is some interest in the new version. When will details about this be released, along with the dates? Likewise, what will the upgrade path be for existing users?

Regards,
Craig D. Cope

@Cope01
Wish the Hong king this was for excitement…mostly for bankers lawyers and accountants…

Yeah the V-card post is the least stable of all the ones we have as V carve was never really intended for plasma. Still find edge cases where it doesn’t work. If you know anyone with good post editing capabilities let me know

and … Yes ther will be a version of the new controller that will be back compatible with ArcDroid Classics and provide all the updated features and memory without having to invest in 100% new hardware
We’re a bit later than hoped releasing this one but rest assured I’ll be posting here as soon as we are ready to go.

Cheers
AM

1 Like