Hi Stuart Okay. Okay. I think I understand where you're coming from now. The MDSI control hint helps me a lot because all of the commercial controls I've worked with, and that does NOT include MDSI, work their handwheels as fixed increment. What you turn is exactly what you get.
When I'm retrofitting or servicing a machine tool I like to know that when I turn the wheel a fixed number of detents, I get that length of motion. I like this because I can put an indicator on an axis and test the accuracy of moves based on what I do with the wheel. I can also see deadband and backlash without needing MDI moves. There are also a lot of operators who use handwheel to move an axis into position before they set workpiece offsets. I believe that predictable distance is critical for all of this. As controls have moved toward PC we see folk who are migrating from desktop. These folk tend to want joystick or flight control motion handling. The Turner control had a wheel that moved the axis faster as you turned faster rather than a fixed distance per rotation. I suspect you have a similar sort of thing with MDSI although I know nothing of their work except one of the guys who used to work for them. Allowing these things to be configurable will soon be one of the biggest EMC2 development tasks. It ain't that way now. The usual disclaimer is that if you need it that way now, the source is available. You can make it that way for your machine, or you can find someone to make it that way for your machine. And that's okay I certainly don't want it that way for mine. Rayh On Mon, 2007-03-19 at 08:04 -0500, Stuart Stevenson wrote: > Gentlemen, > I don't see following error as the answer. The tuning should keep > the following error within spec regardless of the commanded position. > If I could specify a maximum delta from the actual position for > the commanded position I think that may work. IOW, the commanded > position could not exceed .1 (or some arbitrary value) from the actual > position. This would give what appears to be an immediate response to > stopping the handwheel. This would be a leading value not a following > value. I think this is what Roger Neal is probably thinking about. > A value of 0 could disable this or a default of not being > specified would disable this. > I understand the impossiblity to please everyone. I am just trying > to make this machine run as close to and better than any other machine > I have. I put MDSI controls on three 5 axis mills in 1998. There are > some differences from the OEM controls. There are differences between > OEM controls. The differences between OEM controls are not perceived > as faults or problems. The differences between the OEM controls and > the MDSI control is perceived as my problem. Everyone wants the MDSI > control to have the exact features of his perceived perfect control. I > originally thought that might be possible with the number of options > for the display in EMC. After very little study I determined I do NOT > want to go there. I would end up with a control display for every > operator. How fun would that be? > Thanks > Stuart ------------------------------------------------------------------------- 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 Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
