Mesa 7I44-7I70/7I71

Thanks I will try them. I do already have similar files.

I did this-

I hooked up in Hal the z pos-fb <= hm_25i23.0.resolver.00.velocity and I can read the velocity just fine on the Axis screen in the z pos readout. I did the same with the Position and I can see that on the z readout. My question is what exactly is the pin called for the velocity readout on the Axis screen and where do I find that information?

I understand the broken wire or link but I don't know where to find the pins that are already named by the Axix interface or maybe I am totally in left field and I can not see the obvious. I just don't know why I can hook up signals in one area and not another except I don't know what they are called. I am learning tons, Thank all of you for the help. I would buy beers or coffee's all around if I could.

you have these in your hal file ?

spindle-vel-fb <= hm2_5i23.0.resolver.00.velocity
spindle-vel-fb => motion.spindle-speed-in

if the resolver velocity is what you wish to display then the above should do it

or change in the pyvcp_options.hal
spindle-vel-fb => pyvcp.spindle-speed

i.e direct spindle-vel-fb to pyvcp window in spindle-speed box
( or words to that extent ) LOL

Is it supposed to be this hard?

1) What should show up in the Velocity display of Axis?

2) net spindle-vel-fb <= hm2_5i23.0.resolver.00.velocity
net spindle-vel-fb => motion.spindle-speed-in
Yes, I do have these two lines and nothing shows up
I am treating number two as my priorty because I want to understand why nothing shows but if I change the line to connect to net x pos-fb it reads just fine.

3) I am working on the filter portion to try and get the rpm to display in the spindle speed widget.

I am starting to wonder if I need to fun an update on the version of 2.5 that I have. It has bee in the machine since December.....Really grasping. I really am starting to understand some of this. But why I can not get the velocity display to display my resolver velocity. I figure If I can get that far I can scale it to read what I actually want.

Thanks again.....I keep waiting to be banned....LOL

could be theirs been plenty of updates to drivers etc for resolvers it may well be
ok i'll put you out your misery ur banned ....

once we get Chris's resolvers working we may be in with a chance ! to help further
or maybe no ones written the resolver part for spindles .

Does axis even have a spindle RPM readout?

if it did would it not have a signal that starts with "axis."?
for example:

net z-pos-fb => axis.2.motor-pos-fb

is how the Z pos gets to axis

I doubt any of this is resolver related as all the resolver pins seem to be doing what they are expected to

net x-pos-fb <= hm2_5i23.0.resolver.01.position
This is what got the X reading on the Axis Screen, No I do not believe it is resolver related. I think it is total operator error, Me!

The Spindle RPM for the Lathe is an Add on Widget. But I still can't figure out how to connect to the velocity readout of Axis either.


I thank all of you again.

I think the magic is

net x-pos-fb => axis.1.motor-pos-fb

the line:

net x-pos-fb <= hm2_5i23.0.resolver.01.position

just creates a wire called x-pos-fb

Hi guys, thank you all for your help today. Peter, thank you for the new .BIT file. It did the trick.

Now in trying to get my servo motors to turn I have discovered that my pwmgens are enabled as per the watch list, but my values are locked at zero. I have confirmed this also by my volt meter never moving from 0v as I try to move the X&Y axis of my machine.

So a bit of exploration and some help from you and I see that I need gpio.01 (/ENA0) and gpio.47 (/ENA1) to be be ON (yellow?) in my watch list, but 47 is not yellow. Only 01 is. So I think this is my problem.

It appears these settings or toggles come from the 7i43 card but I'm not sure.

My question to anyone who can answer is this: How do I turn my .047 on? -How is this one enabled?

your mixing up your connections PCW is talking about the 7I49 connections which is pwmgen 00 & 01 enable signals , which are ok i.e yellow as shown . and not the GPIO pins as you were thinking , you also have to remember which port your looking for to
i.e P3 or P4 , confusing is it not ......

thnk we need a new thread rather than Hijack the origional post

A new thread sounds like its in order.