On Saturday 26 September 2015 22:33:21 Gene Heskett wrote: Its being difficult, and won't let me loadrt a comp module, so I'll excise that loadrt from simulated_home and name them all in core-sim.hal
Using this path motion.motion-type => s32-float =>compname.in0, compname.equal => timedelay.in, setp timedelay.on-delay 3.0 setp timedelay.off-delay 1.0 timedelay.out => motion.probe-input Works! My code runs. Thanks for the elbow in the ribs. ;-) <VBSEG> Now when I wake again, maybe I can fix my code. > On Saturday 26 September 2015 14:18:12 John Kasunich wrote: > > You should be able to simulate a probe in your sim HAL file. > > A comparator looking at axis position and driving the probe > > input true when the position is above (or below) a specific > > value.... > > Both this idea and Kenneths are possible solutions. But its not > particularly important that it be dead accurate, so I am thinking > along the lines of a timedelay, triggered when motion.probing goes > true, and firing 1 or 2 seconds later. All I need is something to > give it a probe signal before it bails out. Everything it does would > move slightly with the timedelay, but its all in unison in pixels on > the screen & not even any cut pixal swarf on the desk to clean up. :) > > Triggered on motion.motion-type=5 is s32 format, a comp module would > needa data conversion in front of it. I don't see a thing there that > can directly take the s32 signal from motion, without first making it > a float. > > I'll have to cogitate on that when I've had some sleep I guess. Its > been in short supply while I try to add this pointed roundover bit to > code that just works when a .250" end mill is in the spindle. > > The problem is that while it needs to follow the same path the .250" > mill is using, including the rounded corners but with only a 20 thou > or less offset from the center of the 1/4" mill. But the 90 degree > arcs for the corners are as usual, being spoilt, screaming brats. > > One other squawk. > > Clicking on a line in the backplot highlights that line of code, but > where the running highlight is very obvious, a near red with the dark > text, the highlight color used when clicking on a backplot line is > medium grey, and the text is quite difficult to read because there is > very little contrast. The backplot turns the path line bright green, > and it would be a visual treat to have that color used to highlight > that line of code in the text window too, many times easier to read. > > /squawk. > > Thanks Kenneth & John > > Cheers, Gene Heskett Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> ------------------------------------------------------------------------------ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
