Well the (2) in the filename indicates which Thread the C Program was Compiled to run in. The Program may or may not have been downloaded and Flashed to KFLOP. For example pushing the Home button in KMotion CNC may compile, download, and execute the program in a Thread but not Flash it.I just noticed that in my KFlop folder there are files with the .out extension that may indicate which thread they were flashed to, for example K2_Home(2).out. Are these files created when the C programs are compiled, and do the numbers in parentheses indicate the thread number? If so, I've never compiled any C programs, so I'm assuming they were created by K2. Does that sound correct?
Flashing User Memory Flashes the entire state of KFLOP. Which includes all the Threads memory spaces, Axis Settings, and Persist Variables. The last programs downloaded to KFLOP will be Flashed. The current Axis settings will also be Flashed, but I think K2CNC normally did something like set persist variables to values to define the machine configuration. Then used a generic C program that would read the variables and based on that configure Axis Parameters.When you flash the user memory, does it flash all of the C programs that are currently assigned to a thread, and all of the settings on the Step Response and Config & Flash screens? I guess I don't quite understand what gets flashed and what is just controlled from KMotion. I'm mostly wondering about the servo tuning parameters--would these be embedded in K2's C programs that are flashed, or are they controlled from KMotion in real time?
HTH
Regards