Re: emcprobe status

[Paul <paul.corner-at-tesco.net>]

Hi Dean

In response to your "Open Issues" - Not being able to use freqmod will be a 
major problem with rtai based systems. Long term, this shouldn't be a major 
issue though.

Documentation - I would ecourage you to get to grips with LyX (NOT KLyX). 
Merging your docs in to a new pdf or html based handbook will be much easier 
if it is in a LyX compatable format to start with.

Setting up default parameters within the probing routines should be a trivial 
task - Many of the current ini settings have defaults hard coded into EMC 
already.

I look forward to seeing your routines - The cloud of points would be a 
usefull source of data for rendering with VTK. Using VTK, it would be a small 
step to exporting the data as an STL file for use with other programs.

Regards, Paul.


On Monday 13 May 2002 04:03, Dean L. Hedin wrote:
> Open issues:
>
> 1) Emcprobe won't work with the freqmod.o module, it works fine with
> steppermod.o,  have not tried it with others.   Maybe someone can find the
> problem with this.  My workaround is to use steppermod.o while probing,
> and then switch to freqmod.o for machining.  I'll include the two emc.ini
> files that I use in the documentation.
>
> 2) Documentation.  I am working on this presently.  The intent is html
> documentation with graphics suitable for inclusion with the emc handbook.
>
> 3) Better error handling in the .ini file read routines.  (Presently the
> program aborts if it does not  find an ini entry,  which is'nt too bad but
> it would be nice if it continued on with a reasonable default value.)