Advanced Search

No idea how this happend i will post and check it this time

The ui files are 0 kb for some reason

I'm not expert too, I've just been experimenting with AI and looking at the halscope, trying to wrap my head around things in general, it helps to just chat about these things, even just to make sure I'm not persuing a weird irrational tangent, and I'm actually making sense not just to myself lol. YangYang has the math down, he is the main arbitror, nothing goes to master without his stamp of approval, and he checks on what the AI comes up with, and so far nothing really sticks, only what he write himself works best. I've found something with the arcs, I want him to take a look, and I think we maybe possibly be able to do similar tricks with Béziers, but I don't want to keep your hopes up, I think it is possible that, the fact that Béziers change curvature, may not fit with the current tp lokahead/blending architecture, but maybe... maybe I am wrong.

Yeah for sure these are the files, the error code is already above.

Actually, when I think about the proposed integration of 9axis blending, it might indeed be wiser to stick to the circular arc.


In any case, at the end of the day it will always be better to have something that works than something that might be even better but never gets done. So thank you guys for working on this.

PCW wrote:

You MUST set the 7I97 PWMgens offset mode to true or runaways are guaranteed.
 

Yep, that fixed everything! Thanks a million! 

For those who run into this in the future, I needed to add to each axis definition in the .hal:

Where "xx" = joint number. 

Now the machine is stable and jogging smooth and silently. Beauty. 

please post your ui and handler file and the exact error message please.

Ive integrated your handler File now into the Main handler. Problem is that the Error Code is exactly the Same as before.

Hello,

Just for fun i also created a Polygon program where you can change direction (G2/G3), position, number of point/rounds and the corner radius.

For what option is chosen, doesn't the user choose with P-parameter of G64, how much the controller can deviate from the programmed points? Also by option 1, and acute angles should there be a user option to tell what is acute.

(long time reader, trying to do something back to the community, keep up the good work!)

I guess my question was, can I do this:That way I can split my config into different files and not need to coordinate use of components centrally.

You cannot maintain velocity, follow the exact programmed path, AND have smooth jerk.

This is physically impossible. What I am saying is I would sacrifice velocity rather than programmed path on G2/G3 programmed arcs. At the moment if you run something with tangent arcs even with G61 the velocity is kept, this messes with jerk. G61 with jerk will have to slow down more.
For many line segments G64 Pxx it also slow down more, the more tight the tolerance, the smaller blending arcs the slower you have to move.
Béziers will give you better speed, because you can run them faster, but they are NOT arcs, meaning when you program a square for example, just 4 lines, you set G64 to 0.5 let's say, what kind of path error would you accept? A 0.5mm perfect radius which I have to slow down more to make smooth, or a squashed up Béziers which I can run faster?

I don't understand this focus on not changing toolpaths.
The important thing is that we can define how much we deviate from the exact path.
The less deviation we allow the more we have to slow down. 

Even with perfect g2 continuous path blending there is jerk limiting needed at the beginning and the end of the blended paths as well as for jogging. So it's really always going to be Option 1 plus ideally Option 2.

Béziers complicate things

Well, that is certainly true. MUCH easier working with circular arcs. I won't argue there

Slow down at curvature changes: reduce Vel so the centripetal acceleration change is manageable. (this defeats high-speed machining)

This is what I mean is feasible, not ideal, but what we are working with that moment.

YangYang I think tends toward Béziers and smooth High Speed, but this changes toolpath, I'd rather slow down when necessary to make things smooth, and stay on path, which is generally more important than High Speed in our line of work.
I think slowing down on arcs is simpler to implement, Béziers complicate things, and I think, we will still need to slow down or at least calculate the proper speed to execute and stitch in the blend smooth Béziers at, which could prove to be a headache in my opinion, even though the path is smooth doesn't mean you can run tangential speed jerk control and get rid of jerk spikes, I don't think it works like that, but I'd be glad to be proven wrong, but still you would not be following a programmed arc and I don't like that...

There are 3 clocks because there are 3 BISS channels in that configuration

in addition you mast set the DPLL timer so that the BISS read completes before the nominal read time
something like:

setp hm2_5i25.0.dpll.01.timer-us -200

The 7I74 only outputs 5V signals so no 10V signal is possible other than
perhaps overshoot on an unterminated line.

The outputs swing from ground to +5V, so If you measure between
outputs, you could read +5V or -5V depending on the output state.

 

I think he is right, I tend for option 1 as well, actually already have it work pretty well in my testing.
Option 2 which is what the big boys use, Siemens Fanuc etc. as far as we understand, requires a complete TP rewrite