
https://youtu.be/dqNxaktEq-M
Moderators: TomKerekes, dynomotion
I'm not sure what you mean by "bootup". Nothing should happen at bootup as nothing should be enabled or configured unless you have flashed things to KFLOP which we do not recommend. If you have then you might remove everything by re-Flashing New Version to KFLOP.The first is a couple errors I get on bootup.
There are multiple ways to configure KFLOP. The Enable Button on the Step Response Screen downloads all the screen settings to KFLOP then enables the axis. You might read this.My X boots up saying neg limit disabled and won't allow me to enable it on the axis screen, but for some reason it's the only axis that reads correctly as a DAC Servo on startup. I checked my limit switch readings on the digital I/O tab and they respond normally so I don't know why I start up with a limit error. As with the other axis I can enable it without issue on the step response screen and then afterward it acts normally on the axis screen as well.
The encoders count quadrature transitions which there are 4 for each "line" or "pulse" which is good to have higher resolution. You can configure KMotionCNC to what works for your machine. It seems you have 800 * 25.4 = 20,320 counts/inch.My other issue is my lead screws are 5mm pitch with 1 to 1 belt drives so my 1000 count encoders break down to 200 counts per mm, however when I tested a 100000 count move I only moved 125mm. Or 1/4 of my expected movement. I can only guess it has something to do with being quadrature encoders with 4 pairs going to the kanalog? Is there a setting for this or do I only feed the kanalog one pair?
That is all correct but not recommended as it can be confusing and necessary. Once you have a C Program to configure the board and initialize your system this can be used when necessary. No need to flash anything to the board. The problem with flashing things to the board is that there is no way to recover what changes have been made to the board. Its up to you to keep track of everything you did. You can remove all the changes made to KFLOP by re-flashing New Version. See also here.Breakthrough! So I think finally rooted out why I was having so many issues with the machine retaining my settings. My understanding based on the wording was that the save, compile, download, and run button on the C program page was a "do-all" button that updated the C-program on the K-flop that gets referenced when the board powers on. This is what I meant by boots up btw. NOW I realize that button is not how to update the board. I have to hit the flash user memory button on the config and flash screen to update the c program on the board, hit reboot on the console screen and then hit download channel on the config and flash screen to have a faithful representation of my settings after a power cycle of the board. Now I can power down and back on without wondering what the machine will actually do.
Once you have a C Program that fully configures and initializes all the axes, all the axes working and tuned, and you have determined all the maximum velocities, accelerations, and Jerks for all the axes then it would be time to configure KMotionCNC.Now I just need to figure out what to do next. Do I finally get to move over to Kmotioncnc? I can move the machine around and the limit switches read correctly in digital I/O.