On Saturday 12 July 2014 21:12:55 a k did opine And Gene did reply: > i did make new cd are my switch -limit home-- does not working with emc > 2.5 ones again my machine work perfect with emc 2.2.4
Ok, while its running but idle, look at the parport pin your home switch is coming in on. Move the machine to where you know the switch is activated, see if hal_meter shows the change in status, then consult a printout of your hal file to see what net name is associated with that parport pin. Trace that "signal_name" to see where all it goes, and use the hal_meter to verify it is getting there. At some point, it should hit the motion module as a home signal, so check it there while moving the machine on and off the switch. What my mind keeps coming back to is that your .hal file was built in 2.2.4 days, and may be using old syntax. The old syntax is supposed to work yet, but perhaps there is now a place where it "falls thru the crack", aka a bug. 2.2.4 is very, very long in the tooth now. It may be that you've found a bug. Serious errors of course and it will not start, but it will tell you in the window you tried to launch it from, what was wrong. The dmesg command in that window might have a clue, so look the last 50 or more lines of that over carefully. > > what file need to check to see problem? > i can turn camera and you can see monitor in real time. > > On Sat, Jul 12, 2014 at 5:52 PM, Gene Heskett <[email protected]> wrote: > > On Saturday 12 July 2014 19:34:53 a k did opine > > > > And Gene did reply: > > > hi > > > Gene > > > what do you see when open > > > machine >hal meter> signal > > > > > > how many items there? > > > what is items number 8? > > > > That will be highly dependent on your hal file, specifically on how > > many modules you have loaded, and how many functions/pins they each > > have. > > > > So I can't begin to predict what you will see in the menu's. > > > > Each module will have a name, and each will have functions and pins > > driven by signals, or driving signals as the logic is hooked up by > > hal, the Hardware Abstraction Layer. A question on a specific > > module and its "named pins" can often be deduced from a "man 9 > > module_name". > > > > A signal is usually named as the next option to the right of a "net" > > statement. Which means it could be named anything you want. The > > third argument in a "net" line of the hal file is the source > > module.#.pin#, UNLESS that signal name has been used before, in > > which case the third and succeeding arguments are all places where > > this signal is to be delivered. That way you can feed a given signal > > to more places than you can nicely type on one line. > > > > There is more of course, but this needs to be digested, so you can > > build on that. > > > > 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> > > US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS > > > > > > --------------------------------------------------------------------- > > --------- _______________________________________________ > > Emc-users mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/emc-users > > ----------------------------------------------------------------------- > ------- _______________________________________________ > Emc-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/emc-users 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> US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS ------------------------------------------------------------------------------ _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
