Could you send your configuration files?

On Sat, 22 Jul 2017 19:21:40 -0400
Gene Heskett <[email protected]> wrote:

> Greetings everybody;
> 
> Noisy, wet Saturday evening in progress.
> 
> Over on the pi, I am attempting to combine enough code, and using 92 
> offsets, make a brass 8mmx1.0 bolt for the cathead with a single file, 
> and 3 tool changes.
> 
> So I have noted the default net settings in the config I started out 
> with appeared to be connected bass-ackward in terms of signal i/o.
> 
> Without loading hal_manualtoolchange, it sails right on by an M6 
> Tanything command like it was an empty line.
> 
> So, following hints, I added to the end of the loadxx's in the hal file,
> loadusr -w hal_manualtoolchange.
> 
> That hangs it up and LCNC never brings up its screen. Take out the -w, 
> and it then tries to run but exits at the bottom of the hal file,
> because the hal_manualtoolchange pins are not there.
> 
> So the docs say to see such and such a manualtoolchange.hal file in 
> the configs/sim/axis subdir.  Doesn't exist anywhere on the pi.
> 
> Walk over to the mill and locate spits out at least 3 copies.  So I cat 
> the last one, and copy its 'net' commands over to the pi's .hal file.
> 
> Still will not run, doesn't open any gfx except the little box that 
> says its part of the tool changer stuffs, and it eventually, like it 
> says, times out and goes away.
> 
> Call up another terminal_emulator on the pi and run a halmeter.
> 
> halmeter says the documented signal pins are all there, and all false.
> 
> I have not yet tried a direct copy of that stanza from the GO704fast.hal 
> file, which I now note is slightly different:
>  
> loadusr -W hal_manualtoolchange
> net tool-change-request     iocontrol.0.tool-change       =>  
> hal_manualtoolchange.change
> net tool-change-confirmed   iocontrol.0.tool-changed      <=  
> hal_manualtoolchange.changed
> net tool-number             iocontrol.0.tool-prep-number  =>  
> hal_manualtoolchange.number
> net tool-prepare-loopback   iocontrol.0.tool-prepare      =>  
> iocontrol.0.tool-prepared
> 
> I do not have, from following the tuts, a net name hal-toolchange-
> request, but at first glance the logic looks the same:
> 
> unlinkp iocontrol.0.tool-change
> unlinkp iocontrol.0.tool-changed
> # now hook it up like the G0704 version
> net tool-change <= hal_manualtoolchange.change => iocontrol.0.tool-change
> net tool-changed <= hal_manualtoolchange.tool-changed => 
> iocontrol.0.tool-changed
> net tool-prep-number <= hal_manualtoolchange.number => 
> iocontrol.tool-prep-number
> 
> A tool change on the other 3 x86 machines from the M6 Tnumber line works 
> as expected w/o all this hassle.
> 
> Those same lines from the sample manualtoolchange.hal have the i/o order 
> interchanged.
> 
> What do I do next? I'd like to make some 8mm brass bolts tomorrow.
> 
> Is this a pi bug, like my disappearing <> keys in the mdi cmdline box?
> Thanks everybody.  19:21, 'spect I'd better go play short order cook.
> 
> 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>
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Emc-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/emc-users

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to