Chris, thanks for your advice. First of all, nothing far from my intention than to blame stepconf. But the fact is that I have been reading very carefully the timing requirements for my Gecko drives and confirmed that the default timings in stepconf are correct. Nevertheless, I have manually changed these timings (longer, shorter and all in betweem) trying to find a better response without success. I'm by now using EMC2 (2.2.2) and the last version of stepconf (I believe). I have some experience in CNC machining with other less sofisticated programs, but I'm new to Linux (Ubuntu and EMC). I see the tremendous potential of these systems and I'm determined to use EMC2 and I will resolve the problems one way or the other. Some received suggestions trying to help me (like sending ini and hal files) requires a complex procedure that I'm not familiar with so far. May be it's a question of time until I fully understand the internals of these systems. Meanwhile, the short and direct way of using stepconf has not worked for me. Thanks Jesus
----- Original Message ----- From: "Chris Radek" <[EMAIL PROTECTED]> To: "Enhanced Machine Controller (EMC)" <[email protected]> Sent: Sunday, December 09, 2007 3:53 PM Subject: [Emc-users] Don't blame stepconf unless... > On Sun, Dec 09, 2007 at 03:11:51PM +0100, Jes?s Bas wrote: >> Sheldon, >> >> I'm suffering the same issue with my laptop Dell C610 and have also fixed >> the SMI latency problem the same way. >> Have you however tested EMC with your Dell laptop in a real machine? >> Even with the latency issue resolved that way, I have not been able so >> far >> getting my mill machine working properly. Moves are very erratic and >> making >> a lot of rough noise from the stepper motors. >> I was thinking about other unknown problems with this particular laptop >> but >> now, looking to the emails in this list, there apparently are other >> configuration issues with stepconf. > > When I had similar trouble with a stepconf-generated config, the > problem was the timing settings. My drives are L297-based, so I > picked L297 on the menu, but I neglected to consider the schmitt > trigger/RC filters on the inputs to the driver which make a much > longer step pulse necessary. The timing settings MUST be right for > your drivers to see the step pulses reliably. > > Stepconf generates "doublestep" configurations which allow a much > faster step rate. That's nice but the trade-off is that people who > have never had to worry about the timing requirements of their drives > now have to, because things are happing much faster. > > Chris > > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Emc-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/emc-users ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
