Forum Replies Created
Here are the links to the version 4.1 (provisional) in Automation:
And finally Automation also has a real documentation files:
The version 4.1 it's completely different than previous.
Ci sono i Breakpoint, i Watch, the FullsScreen, the Select-Case and many other new instructions.
With a sequence of X Y Z written in the error automation there has not been?
XYZ was just like the one that was wrong? Did I get it right?
At this point, then we must focus on the differences between the two to figure out where the problem lies.
Always pay attention to the value that is on the Slot 5 (asse Z) on application HAL.
That value must always end with zero (or the value you set as the final value)
It seems to me that you have already confirmed that it is so, but I want to make you see that that value is the safest response we. If he is right then the problem may be only after, then the Master, in driver driving signals, o no driver, o nei motori
You write that the Automation little program gives you an error, in fact it was written with version 4 which has many new instructions. We will publish it today or tomorrow and maybe in a few hours I send you a temporary post or add a link.
This little program of automation should help, It produces random movements XYZ very similar to your example.
If you need to edit it to add the comparator location Call me and I'll help.
The idea would be to be able to get the error even without Theremino CNC and then delete a large part of possibilities from research.
v1 = 0 ' Random Minimum v2 = 10 ' Random Excursion v5 = 1 ' Counter start v6 = 50 ' Counter end Label MainLoop Gosub WaitAllMotOrs Slot(1) = v1 + v2 * Rnd Slot(3) = v1 + v2 * Rnd Slot(5) = v1 + v2 * Rnd v5 = v5 + 1 Print v5 & " of " & v6 If v5 >= v6 Goto End EndIf Goto MainLoop Label End Slot(1) = 0 Slot(3) = 0 Slot(5) = 0 End Label WaitAllMotors Wait Seconds 0.1 ' ---- ensure motors really started Label WaitAllMotors2 If Abs(Slot(2)) + Abs(Slot(4)) + Abs(Slot(6)) < 0.01 Return EndIf Goto WaitAllMotors2 ' End of WaitAllMotors
To better explain this sentence pleasure:
“…After each test marked CNC Theremino 0 in Z but the machine mechanically NO. But marking Z axis micrometer always in tune….”
Marking Z Axis thing is ???
OK, for even answer me pleasure to some questions and shake some more’ the field of action (and forgive me if I repeat some questions maybe you've already answered, I have many things on my mind and I do not remember everything, and then it is good to repeat in different words).
1) Have you tried using a different machine to see if it does too?
2) You may even shorten codes, for example, making only ten lines that make 0.1 mm error one o'clock?
3) You could eliminate any line does not strictly necessary, eg X0 Y0 Z10 and G4 and M30) and only use the G1
4) Could (as I wrote to you) As an example also in automation that does exactly the same movements, and who is wrong?
And now let's focus on what we already know.
I tried your example XYZ and end slot 5 The Z was perfectly zero.
This should be totally excluded from the problem Theremino CNC.
So if we wrote a code in Automation (Three RND functions that drive x, y e z) He should also make mistakes
The firmware of the Master is the three axes totally independently so it should not change anything if we move only Z or X,Y,FROM
I can not think of any possibility.
We must do other tests to isolate the problem better.
Please try another machine.
I would help with my cutter but it's too slow (700 mm/min) to run your code in a reasonable time and then I have little time.
Major improvements to all HAL !!!
- We have fixed dozens of small defects.
- The list is updated more quickly, and not blinking, even if it is very long.
- The list is more readable (eliminated the column "Dir")
- The oscilloscope is improved.
- Changes to the numerical values are now faster, usando PageUp e PageDown
- You can also use the arrows combining them with the SHIFT, CTRL ALT e
Download the latest HAL 8.0, ArduHAL 2.0 the NetHAL 2.0 from the site Theremino (page: Downloads / Basic Applications)
What happens somewhere RESET the Master module caused by voltage drops?
But they should also make mistakes the other two axes…
You tell me that does not happen with automation…
could you please make a Gcode with only the vertical axis and that does exactly the same operations up and down an automation program and then compare them?
E (if one of the two causes errors and the other does not) then maybe you could send them to me that both of them I also compared.
(maybe there is something that you consider harmless and yet it is not)
“…The engines have the encoders and according to the manufacturer performs and controls with precision the number of inputs received…”
My intuition tells me that the problem might be in these encoders, that they are not simple stepper, and that under certain conditions mistaken.