On Sunday 17 May 2015 18:22:02 sam sokolik wrote:
> does it still crash without any external device powered up?  (I too
> have been running linuxcnc up to 2.6.7 without issue)
>
> sam
As in LCNC running, but with motor power off?  I don't believe I have 
tried that.  With motor etc power on, it ran all night last night, 
without LCNC running.  FWIW this is 2.6.8, not 2.6.7.

This afternoon I reset the base_thread from 25 u-s to 30 u-s, and turned 
dpms off.  I had it sweeping back and forth across the tool I am shaping 
to cut the polygroove pulleys with, which has only a 40 degree included 
angle, but because its going to be a two speed, 99% of the right face is 
set at 18 degrees. About 2% of the left face will be set at 18 degrees 
so I can cut virtually flush with the side of the larger of the 2 pulley 
steps. It sweeps back and forth with a dremel 1.5" diamond disk, doing 
2500 revs, stacked up on the mandrel for increased rigidity, 10 times, 
then lowers the wheel 2 thou, & sweeps 10 more times.  It made it down 
to -0.022", no where near enough material removed yet, and crashed while 
I was standing there contemplating turning off the monitor & letting it 
run all night.

That was 6 crashes today. More than enough for me to load the big guns, 
but it has already been a long day.

2.6.8 is busted on the mill, exactly as it was busted on the lathes box.  
The crashes are identical.

Tomorrow I pull it down, uncover it & take the air hose to it (it will 
surprise me if I get any great amount of dust out of it) install a 5i25 
in the empty PCI-E slot, then do a clean install the latest 
binary-hybrid.iso.

Get networking working, starting with nuking network-manager so I can 
configure it staticly without that worthless POS overriding everything I 
do, then install amanda-client stuff including xinetd, and get root and 
amrecover the ~/gene/linuxcnc tree.  Pull the mesa stuff from Peters 
site and install firmware for the 5i25.  Steal the lcnc line 
for /etc/apt/sources.list from the lathe and install 2.8.0-pre. On the 
lathe, its bulletproof. I haven't had a crash since.  And the screen 
blanker is working fine.

With good luck, I ought to have it back up amd working on sharpening a 
pulley maker tool before tomorrow is fini.  Configuring the 5i25, and 
finishing the install of a 48 volt motor supply already sitting on a 
shelf above my head is a different project.

Sharpening this tool is a PIMA, but try as I might, I cannot duplicate it 
with a google search for a carbide insert type tool.  Unobtainium is the 
correct word it seems.

On those tool sharpeners that use a diamond dust in oil spread on a 
spinning metal plate maybe 3" in diameter, What is the metal?  I've not 
seen one of those toys since making the camera cases for the Trieste in 
1959, and the machinist we hired had one of them, and a jig bored full 
of holes at all sorts of angles.  He would stop the big lathe, grab the 
tool, mount it in this jig, start that diamond disk spinning with a 
small motor, running slow enough it didn't throw off the oil & diamond 
mix, stick this holder on a 1/4" post so the tool tip rode the wheel, 
swing it back and forth a half a dozen times at various holes the 1/4" 
rod and the swiss cheese holder had, and in about 2 minutes maximum that 
HSS tool would be peeling good sized bronze strings off the 7" diameter 
3" bore tubing that would become the camera case, good for a 20,000 psi 
exterior pressure withstand.

I'd like to make one of those disks.  Purposely soft so the diamond 
particles actually would embed themselves in the face of this disk.
But I don't recall what that one was made of 55 years later.  Do any of 
you folks know?

> On 05/17/2015 04:35 PM, Gene Heskett wrote:
> > On Sunday 17 May 2015 17:25:07 andy pugh wrote:
> >> On 17 May 2015 at 22:19, Gene Heskett <[email protected]> wrote:
> >>> Since I am software stepping, when I next reboot
> >>> it, I will raise the base_thread to 30 u-secs just for S&G's.  I
> >>> believe it was 27 the last time I checked.
> >>
> >> Have a look at Machine->Show Hal Config and at the bottom of the
> >> list is "threads"
> >>

The base_thread show 2 figures, the left hand showing a hair over 11 u-s, 
right hand one being just 2 shy of the thread period if it was 25 u-s, 
but now at 30 u-s has about a 7 u-s cushion.

> >> Make sure that the base-thread time is less than the base-thread
> >> period by some margin.
> >> Also, make sure that only functions that need to be in the base
> >> thread are in the base thread. That is probably only parport.write,
> >> stepconf.make-steps and encoder.count
> >
And the parport.read & spindle pwmgen.make-pulses. I did have a debounce 
in there to settle the G38.2 probing but servo-thread is probably good 
enough for that so I moved it.  Parport.read could probably go in the 
servo-thread too as the main excuse for that is the G38.2 probe 
function.  The actual probe circuit has a small tantalum cap to hold a 
fleeting contact long enough LCNC sees it anyway.

Thanks Sam.

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>

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to