Mesa 7i43 / 7i49 / 7i37 FIrmware Needed

You were originally right. I was using a 400k gate FPGA, it is my mill that uses a 200k gate, but thanks for the 200k one I have a spare 200k card I can use on the lathe as well. I went back and re-checked my jumper settings and I had misread the manual originally, it was set for USB mode on the FPGA. Switched it to EPP and I'm good to go! Now it's time to start trying to read resolvers. Thanks!

-Scott

Managed to read the I/O inputs on the 7i37 board last night! Still working on resolver issues. The resolvers are being powered by the 7i49 and are returning values but nothing is showing up in Axis. I probably have something wrong in my hal file. Will do more digging tonight looking through other people's HAL files for 7i49 setups. Thanks again everyone for the support.

-Scott

easy way is to post your hal and ini files . and let us know what your struggling with etc .


here's an example of the resolver part needed in your hal file

# ---Resolver feedback signals/setup---

setp hm2_7i43.0.resolver.00.velocity-scale 1 # mptor speed in RPS
setp hm2_7i43.0.resolver.00.scale [AXIS_0]ENCODER_SCALE
net x-pos-rawcounts <= hm2_7i43.0.resolver.00.rawcounts
# add pid.x.feedback
net x-pos-fb <= hm2_7i43.0.resolver.00.position => pid.0.feedback
net x-vel-fb <= hm2_7i43.0.resolver.00.velocity
net x-pos-fb => axis.0.motor-pos-fb
net x-index-enable axis.0.index-enable <=> hm2_7i43.0.resolver.00.index-enable

also make sure you have resolvers added here
loadrt hm2_7i43 config="firmware=hm2/7i43-4/SVRM6.BIT num_encoders=0 num_pwmgens=6 num_3pwmgens=0 num_stepgens=0 num_resolvers=3"

and dont forget your encoder scale in the ini file ... for example ENCODER_SCALE = 20000.0

hopfully that should do it

Dave

Dave,

Thanks for the feedback, I've been running my HAL file as generated from PNCCONFIG. The resolver section is as shown below (full hal/ini attached) . Everything was similar to your post with the exception of the => pid.0.feedback so I added that as pid.x.feedback to match my naming convention and it didn't fix anything. Because I'm trying everything I also swapped all my pid.x to pid.0 etc and tried it that way, no luck. Let me know if you have any other things to try. I did re-verify the resolver signals at the 7i49 and they look good. Thanks,

-Scott


loadrt hm2_7i43 config="firmware=hm2/7i43-4/SVRM6.BIT num_encoders=0 num_pwmgens=3 num_3pwmgens=0 num_stepgens=0 num_resolvers=3"

setp hm2_7i43.0.pwmgen.pwm_frequency 24000
setp hm2_7i43.0.pwmgen.pdm_frequency 6000000
setp hm2_7i43.0.watchdog.timeout_ns 10000000
loadrt pid names=pid.x,pid.z,pid.s


# ---Resolver feedback signals/setup---

setp hm2_7i43.0.resolver.00.velocity-scale 1 # mptor speed in RPS
setp hm2_7i43.0.resolver.00.scale [AXIS_0]RESOLVER_SCALE

net x-pos-rawcounts <= hm2_7i43.0.resolver.00.rawcounts
net x-pos-fb <= hm2_7i43.0.resolver.00.position => pid.x.feedback
net x-vel-fb <= hm2_7i43.0.resolver.00.velocity
net x-pos-fb => axis.0.motor-pos-fb
net x-index-enable axis.0.index-enable <=> hm2_7i43.0.resolver.00.index-enable

Can you do a HAL watch/halmeter on the resolver error and position pins?
if these are not right you are not going to get any further

From axis I opened the HALmeter results as follows:

hm2_7i43.0.resolver.error = FALSE
.position = -9.313226e-07 doesn't change when I move the axis
.velocity is all over the place +/-
.count = -1

-Scott