RAMS for use w/JGRO

[Thinwater]

I bought a Maxnc mill two years ago and got the RAMS gold to go with it. I sold the mill because it was to small (But it was very precise). I am building a JGRO router now. RAMS allows you to select the machine you are making the code for. A homemade router is not listed as an option to create code for.

Will RAMS work with any of the software normally usde to run a Geco based stepper system?

If so what software should be used so the RAMS can still be usefull?

JIM

[b0gh0s]

Rams will generate toolpathing using any of the stock machines in there, and the tool pathing will work (in general) on most machines that can use step and direction gcode but you still need to address zeroing and jigging/fixturing as well as the way some commonly used code (such as comments or peck drilling) are formatted.

Mind you that my hacking here is mostly for 2d type pathing and cutting, not complex 4 axis machining.

I created my own configuration file for my K2 cnc bed which is driven by stock xylotex hardware and Mach 3. It works great and I have only done minor tweaking over time. I'm attaching a zip file to this message which contains a ".ppc" file which represents my semi custom configs for Taig and K2 machines.

I spent a bunch of time trying to decipher a lot of what is going on in these files and RAMS was decidedly unhelpful even though I purchased the full package and specifically paid for "tech support". They wanted to charge me to write a new file, instead of answering basic questions about how the files work and what the variables, etc mean. I finally got some answers after a lot of pestering and complaining.

If you have questions about this I can try to walk through in more detail where I changed stuff and what i did. I tried to add comments where things were not obvious.

I made changes to address in flight tool changes against the library of tools, etc in the Taig file. The K2 file I mostly made cosmetic changes to make the files easier to read once generated and fixed the peck drilling routine which was not generating the Gcode correctly for the Mach controller to understand.


******DISCLAIMER*******
I take/accept NO responsibility for the use of the attached configuration, or any loss/damage/injury/death associated with it's use.
*********************************