Steve, Thanks....
My next step is to create a .hal file (I believe) that makes the connections to hal and halui. I have a couple questions about this. Looking at Anders work, it looks like he has a single file w/ both regular hal and halui connections, that get called from the .ini file using Halfile = XXXXXXX.hal. I would like to do the same. I have a decision to make on what features I want to include on my pendant because I only have 13 inputs to work w/. Well I actually have one more unused port that I could use to give me 26 inputs. I will have to come up w/ a clean way of breaking out to 2 individual parallel ports from one pendant to do this. Anyway, I think I have a handle on the normal bit type i/o. For jogging an axis I think I see a couple ways to do it: With out a jog wheel: I could have buttons that would jog in the plus or minus direction. I would have a multi-position switch to select X,Y,Z,A axis. I see in halui that i could use halui.jog.<channel> aka axis.minus and halui.jog.<channel> aka axis.plus . Because I am limited on inputs I don't want to dedicate a input for each axis + and each axis -. I would like to have a way to use the already selected axis/channel (0-3). It looks like match8 might do this but I am not completely following how it works in Anders .hal file. Also how does halui.jog.<channel>.plus and minus work. Does it jog continuous when halui.jog.<channel>.plus is true? I am used to if then else type programming. It looks like some of the available blocks can be used to reproduce this type of structure? Thanks, Mike On Tue, 2007-01-09 at 13:25 -0500, Stephen Wille Padnos wrote: > Mike Cinquino wrote: > > >Anders, > > > >Thanks, that's good info. > > > >After looking at the HAL_Documentation again... The answer to my > >question on adding a second port jumped out at me. I don't know how I > >missed it many times before. > > > >It looks like I want to do this: (add this to my standard_pinout.hal > >file) > > > >loadrt hal_parport cfg="myport#_0 myport#_1 in" > > > > > I'm glad you found it, that should work. You may want to use > underscores instead of spaces though. Apparently insmod on some systems > cuts off string parameters at the first space. The modified line looks > like this: > loadrt hal_parport cfg="port0addr_port1addr_in" > > >My first port will be defaulted to an output type because I did not > >specify in. My second port will be an in type because I used in after > >the port number. Does this look right? > > > > > It's safer in general to specify things instead of using defaults - that > way it keep working even if the default changes: > loadrt hal_parport cfg="port0addr_out_port1addr_in" > > >Can I start using this port after I have done this? > > > > > Yes. It will be parport.1.xxx, as you originally thought. > > - Steve > > >Thanks, > >Mike > > > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Emc-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/emc-users > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
