3
« on: March 19, 2023, 08:52:21 AM »
Thanks joeaverage,
I will definitely experiment with the Mach API's.
I guess the Mach3 Velocity mpg functionality was quite similar (more correctly I was using "Step & Velocity" mode). It worked in mpg incremental mode until axis velocity was maxing out (and mpg could then potentially get ahead of motion) it would then switch to velocity move until mpg rate was below max speed again at which point it would drop back to mpg controlled moves, starting from the position the velocity jog stopped.
It's probably cleverer than that in Mach3 and probably takes any cause for mpg windup including acceleration and velocity limits into account. It probably also employed some filtering/hysteresis on mpg speed so that it wouldn't rapidly jump back and forth between modes. Even if I could only implement a simplified version it may prove to be functional.
Knowing very little about the Mach4 API at this point I'll take a look and see if it is possible to do something similar. If not then potentially look at the options back at the mpg encoder end.
I could potentially see a couple of approaches. Have to find out more about what's feasible to read and control in the API.
A quick look for other options appears to show that custom functionality can be programmed in the Pokeys device using Poblocks so that may give another option to try and achieve some functionality without resorting to making my own microcontroller pcb, although again I currently have no experience of Pokeys/Poblocks programming.