2010/6/4 Viesturs Lācis <[email protected]>: >> The rest of your HAL and INI would work better with >> >> setp gantrykins.joint-0 0 >> setp gantrykins.joint-1 1 >> setp gantrykins.joint-2 2 >> setp gantrykins.joint-3 0 >> > > Ok, thank You, I will try this out. > Could You, please, be more specific on what is the difference between > both of these options?
You have 4 joints and 3 axes, the lines above define which joints (motors, in effect) are associated with which axis (X,Y,Z,A,B,C,U,V,W) > My hardware part has already been created and X1 step and dir pins > have to be 2nd and 3rd, X2 step and dir have to be 4th and 5th pins. This is not a problem, the HAL file defines which stepgen outputs go to which parallel port pins. You are free to arrange them any way you like. > So with Your suggestion in stepconf wizard I will have to create > following pin assignement - joint 0 step and dir - 2nd and 3rd pins, > joint 1 step/dir - 6th/7h, joint 2 - 8th/9th, joint 3 - 4th and 5th. > Do I correctly understand that? If you think you can create a working gantry config in stepconf, then no. stepconf is designed to set up simple systems to get the majority of people up and running quickly. I think you are at the point where you need to give up on stepconf and start editing by hand. You can simply copy the config directory and rename the files to create a cloned config if you want to preserve the current (semi-working) stepconf-generated configuration. > How do I assign these > 2 rotary axis to second parallel port? I tried the stepconf, added the > second parallel port, I think, that I entered correct address for the > port and in the drop-down menu chose "out" (I tried to follow > Integrator's manual on this topic, including "lspci -v" command in > terminal to find the second parallel port), but when I came to the > window, where the pins are assigned, I was not presented with pins of > the second port. I don't think that stepconf has that flexibility yet. It will add the definition to the HAL file and add the functions to a thread, but the configuration has to be done by editing the HAL file. > Then I understand, that I will have to do it manually in HAL file. The > way I see it now, is that I will have to indicate not only pin > number, but also port number/address, so that EMC knows - this > particular signal has to go to second port. I did not see anything > about this in the Integrator's manual. You will see that there are lines in the HAL file like: net zstep => parport.0.pin-06-out ? pin 6 of the second paralell port is simply <signal name> => parport.1.pin-06-out. -- atp ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
