7i43 GPIO Configuration Error

More
09 Jul 2011 21:16 #11323 by gtms_scott
New EMC user here, I'm in the middle of converting an old Milltronics Partner II that had a dead controller. I'm using the Mesa 7i43(200k) w/ the 7i33 PWM servo card and the 7i37 I/O card. I've installed the live cd w/ the latest emc version and all of that is working just fine.

I can read the encoders in emc and then jog the servos around but I can't seem to get the GPIO working. If I set a pin as output emc won't load and I get the following error:

Debug file information:
mill.hal:75: parameter or pin 'hm2_7i43.0.gpio.017.is_output' not found
5242
PID TTY STAT TIME COMMAND
Stopping realtime threads
Unloading hal components

(Full file attached to msg)

In addition to that I can't seem to see any change on input pins when I try to view them in the Hal config. I'm lost as to where to proceed. I was amazed how easy it was to get the servos working and the mesa card talking to EMC. Can't wait to get the GPIO working so I can finish up and start making chips soon.

Thanks for the help,

-Scott

File Attachment:

File Name: error-3cf5...8cb6.txt
File Size:6 KB
Attachments:

Please Log in or Create an account to join the conversation.

More
09 Jul 2011 21:17 #11324 by gtms_scott
Forgot to post my hal and ini file.

File Attachment:

File Name: mill.zip
File Size:4 KB
Attachments:

Please Log in or Create an account to join the conversation.

More
09 Jul 2011 21:59 - 09 Jul 2011 22:00 #11328 by BigJohnT
Did you check your dmesg just after starting your config to make sure gpio.017 is not used by some component of hostmot all ready?

My config is setp h...is-output 1 don't know if that makes any difference using 1 or true or not.

John
Last edit: 09 Jul 2011 22:00 by BigJohnT.

Please Log in or Create an account to join the conversation.

More
09 Jul 2011 23:33 #11338 by PCW
GPIO17 is very unlikely to be available in a servo config, as most servo configs put the servo interface (PWM and encoders) on the first connector = I/O 0..23 = P4
probably I/O 24..47 (P3) will be GPIO so for a 7I37, GPIO40 through 47 will be the outputs

Please Log in or Create an account to join the conversation.

More
10 Jul 2011 03:10 #11347 by cmorley
This is most likely a problem with pncconf.
You are using EMC 2.4.6 ?
There is a bug about component numbering for the 7i43.
The fix has not been released yet unfortunately.
I'll try to think of a work around - plus try to remember what exactly the problem was.

Please Log in or Create an account to join the conversation.

More
10 Jul 2011 03:14 #11348 by cmorley
this is the commit for the fix so sounds like your problem:

"fix 7i43 firmware array - connectors not in right order

I failed to see the connector numerical order is not the same
as the components logical order. So setting gpio on connector3
would actually be setting it on connector 4. If there was
enough special components to span both connectors their
numbering would be wrong too."

Please Log in or Create an account to join the conversation.

More
10 Jul 2011 04:09 #11349 by cmorley
things you could do;

- hand edit the files you have. ( not fun but you learn lots )

- download the latest bugfixed version from EMC's buildbot.
buildbot.linuxcnc.org/
This would replace your released version of EMC with the buildbots version.
buildbot makes its versions from the repository that includes the latest bug fixes.
You would get the latest bug fixes almost as soon as they are fixed.
I like this one.

- you could copy a new version of pncconf over the old ( its found at /usr/bin/pncconf )
you need sudo to do this.
this would be overwritten on the next release but then would be fixed anyways.

no idea when the next release will be. ( I've asked :) )

Please Log in or Create an account to join the conversation.

More
12 Jul 2011 02:13 #11444 by gtms_scott
Thanks for the help that worked. I admit I took the easy route and used the buildbot to get the latest version. It was nice to have a working test panel too! Now I can move on to other things, getting closer to making chips!

-Scott

Please Log in or Create an account to join the conversation.

More
13 Jul 2011 01:00 #11484 by cmorley
Oops the test panel is not supposed to be available.
I had the seemingly unfixable problem that it would always work the first time but not after that until PNconf was reloaded.
and tests wouldn't work until the command 'halrun -U' was run in terminal.

Is this true for you too?
I've wanted that test panel to work for a very long time!

Please Log in or Create an account to join the conversation.

More
13 Jul 2011 02:47 #11486 by gtms_scott
It worked w/out running any other commands. I will have to try going back to it twice w/out restarting pnconf.

Please Log in or Create an account to join the conversation.

Time to create page: 0.147 seconds
Powered by Kunena Forum