Chris Morley wrote: > It seems that the calibration program will only check the first HAL file > described in the INI file. which is ppmc_load.hal. > while the values for substitution are in ppmc_motion.hal > > if you move the setp ppmc.0.encoder.00.scale [AXIS_0]INPUT_SCALE > etc into the ppmc_load.hal -I bet it will work properly. > I can't test that cause I don't have a ppmc product. > > Let me know if that works...sorry the answer took so long. > WOW, this is an amazing discovery! I have had my config broken up into a bunch of hal fines for years. First, there's an xxx_load.hal file that does the loadrt and addf commands, then I have 2 hal files to connect up all the motion, pid and interface stuff (I've been working on merging xxx_servo.hal and xxx_motion.hal, there was no good reason to split these up like that) and then an xxx_io.hal that takes care of aux I/O and E-stop functions. So, I typically have 4 hal files, as you say above. I have run this with a 2.6.0~pre version with no problem, however I haven't tried with a stock 2.5 install from the CD.
The xx_motion.hal file can't come before the xxx_load.hal file, since the pins won't exist. There are anomalies in how the calibration menu works, however, that have been there for a long time. Most notably, the PID_MAX_VEL parameter doesn't show up for axis_0, but does on the higher-numbered axes. Jon ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
