V1.0 is now

New stuff

Logic

• now both APT reader and G-code output are in switch case this makes processing much faster, and takes less memory
• line splitting is now done before actually going into the switch case for both reader and writer, mainly because then element zero in this case is basically line.startsWith, and then later in code I shaved of like 14 line splits
• invalid cycles are now rejected and aren’t even translated into KK

Bug fixes

• since I switched from line.startsWith I need only the word in the variable, and there is like a $$*CATIA0 in every file and I hadn’t put line split with * so it registered as and error
• I have had left the incomplete cycles to be completely written causing an undefined variable to be written in KK and forwarded into G-code

What if’s?

What if I was supposed to like make CYLINDR output 300 points in G-code I honestly don’t wanna do that?

New stuff

Logic

• helical interpolation in g-coder
• g-coder now remembers the last coordinate, because CATIA gives, the center, radius, direction, 2D vector for direction of movement, end point and pitch, but WinNC that reads the g-code takes end point center and number of full turns and cw or ccw, so number of turns is calculated speciffically inside the class

Bug fixes

• yes

What if’s???

No

New stuff

Input

• now the default value for APT input is CatiaV5 but only for development and it is not written that it is it just is
• default value for for G-code output is WinNC Sinumerik

Logic

• added logic for CYLINDR which is essentially just a sinusoidal path, not just one period pr it but can be multiple or just a part of one
• logic for PSIS which is supposed to be like a sign that the CYLINDR is to be defined and that it starts at this coordinates and then some random vector that defines that the movement will be projected in a PLANE that does not contain that vector
• logic for ROTABL is incomplete but here I would need to look into it but it seems like it is used in MULTI axial machines, but only when it does 3 axis work idk it is a bit emptly defined
• TLON,GOFWD is now the new definition for circular movement, so it takes the line in the correct logic for both CIRCLE and CYLINDR
• I undiscovered what CUTTER with 7 tool data defines but for now it just outputs it as 7 comments

Bug fixes

• for SWITCH or setting tool compensation had .trim instead of .trim() same thing happened on the g coder side
• for some reason maybe a bad commit, the text enter pop-up window didn’t pop-up, resolved

What if’s???

What if the sinusoidal movement isn’t horizontal yet at an angle what would happen then?

• The angle isn’t specified, but I do have the circle center and the first point that is on that circle
  Note that the path is on the surface of the cylinder this is a sinusoide

What if the sinusoide isn’t set in 2D?

• since 3D circular intepolation is off it should be just a set of close points

What if there was no AI that could by pass the main page and end up to a sub-page that isn’t locked to me, unlike the main page?

-Would I be ******?

NEW VERSION INCOMING

• once I get to it v0.9 is going to be official and running on my website

New stuff

Visual

• re-organised quick settings
• fine tuned the spacing’s inside and between blocks

Input

• now you can manually write code to test how output would look like
• mostly for me for developing so I can have some APT code loaded in keyboard cache for Ctrl + v
• comes with a pop-up text box for a nicer visual

Solved bugs

• Rapid logic is renewed by hand I literally have a page in a notebook filled with possible logic combinations and solutions for it
  (in APT, RAPID is only for the next line, in G code however it is on until set to work in cutting motion )
• some other issues where it would save CYCLE the wrong way, it would have saved 2 number with out spacing
• I have forgotten that x y z in cycle aren’t always saved as just numbers but rather 2 of em had X Y or Z before written so it would have double letters

New stuff

For Catia

• TLAXIS now defines which way does the tool need to go to complete the cutting motion
• MULTAX defines this is a multi axial process
• SWITCH defines a change in tool compensation *see under DOCUMENTATIONS - Images - Image.png
• Complete cycle support some cycles are excluded from support due to a possible bug causing to have incomplete information about the cycle
• GOTO/GODLTA between CYCLE start and the CYCLE/OFF log the coords in a variable
• CYCLE/ON activates the function to start collecting coords
• CYCLE/OFF puts out all of collected data for that cycle

WinNC Sinum

counting that you can set it in ISO-Mode

• Complete canned cycles for the cycles that are matching with Catias idea how the cycle should look like
• MULTAX support
• TLAXIS support
• Added a fall-back for CYCLES that are not matching, except this one can use any format of the given CYCLE

Errors

• I did AI’s job, which is making sloppy code, and instead of sectioning Catias TLAXIS I replaced the commas, and replaced / with : causing mayhem, i got empty strings a string that contains double data
• I tought I could use Autodesk,s logic for parsing, They might be onto something but I have no idea what is going on there soo
• I made ChatGPT quit (I just wanted him to help me with finding out why was I getting bugged lines fed to my g-coder (it was magically fixed I still have no idea what had been happening))

Devlog 14

New stuff

Nothing much just did some documentation on Catias apt output
Added a few guides on how to set up the APT correctly very likely prone to changes

SWITCH

As it turns out SWITCH means a change on tools compensation look at image.png in DOCUMENTATIONS
Completed output for the g-code on that switch but I think that it might cause problems bc in WinNC sinumerik it look like it doesn’t do that sooo yeah

Fun fact, *picture, this is what you get when you set a random curve as a tool path
Found out that https://archive.org/details/numericalcontrpol0000stan is tottaly right about every single bit of stuff that I tought wasn’t in Catia so yeah

I added a background

So i have been tinkering with ChatGPT on what to do to up the looks on my project, and I had some ideas for the background but my CSS and JS skill are beyond wanted so he helped to find https://neat.firecms.co/
And it is a MUST have for any project, it just looks SOOO good.
But with every edit there are bugs, so erm yeah.

CYCLE SYNTACS

It is going to be a long one since CATIA V5R21 likes to vary and I feel like an archeologist uncovering this secrets

Finished editing and preparations for a Ship and launched it on http://karlougrin.com/apt_gcode-web/index-apt.html

Completed some needed bugs and excess output

I should prolly add some fire background (any suggestions??)

Another 4 hours down the drain

Pretty much just destroying my brains out why it didn’t want to make an output file, then why it didn’t write anything down<

DEBUGGING FOR 5 HOURS

<(Writing code for +/-9min)>

I REVERSE ENGINEERED CAM APT CODE

So basically what I needed to do was to like just make up my own kind of universal data tranfer standard via JSON so I can translate from different APT into different G-code, and so I made up KK (Karlov Kod). To make it a first ship just need to write another 400 lines but Hey!, this part at least has some documentation. (Unlike CATIA APT1.0)

Edited the CSS it looks so fire, just need to finish my website firstly. Then there goes the first ship!!

OH! MY! WORD!
(it finnaly works after trouble shooting for 4 hours)

Made it to display ts, just left to translate like 600 pyhton lines into JavaScript. YAAY cant wait for allat.(lowkey hidden menus wont show up but its ok)

I did it, rapto comand now works!!>’*’<

adding code so i might get rapto to work

The last one before first shipping.

I may or may not have renamed the git repo so i kinda lost some minor time but- a lot left to do

Yess, finnaly got the wakatime running, exept i have spent like 40hours of my life on this beafore i installed waka. And it says that i used more ai than actual code, not true (bc of those 40h).