Thank you for the reply freed.
I cannot remove those delays as the microsecond delays are the actual pulses which initiate a step on our stepper driver/motor. If there is not delay then it is not a pulse. It makes no difference if I change those values anyway as I have tried.
I can cheat and make it work kind of correctly by putting the getblocks portion in an if statement that only runs every 20-50 loops. Then the machine comes to life and runs quite fast but stutters every 20-50 steps when the whole code waits on the next frame. Here is an example of the cheat I am referring to.
If (i >= 20)
{
pixy.ccc.getBlocks(false);
i=0;
}
i++;
I am self taught so please excuse my methods if they are unorthodox or inefficient.
Since adding this statement speeds up the machine dramatically (it goes from a crawl to a pace so rapid it shakes the table when it starts and stops) I can see no other possibility than that the false statement as I have implemented it in my arduino code does not work. I am adding code and operations to the code but it is running faster…so it is definitely not just giving me the most recent frame when I use pixy.ccc.getBlocks(false).
Am I using this correctly? Does it only work in Java? Do I need to update my Pixy2?
Thanks all