On 12/9/2012 9:16 AM, Gene Heskett wrote:
> It seems to me that
> dead ends & crossed connections would be a lot easier to see in that
> format.

Dead ends are easy to detect in software (it's what my friends in the 
process and piping industry calls "free-ends analysis").  A simple 
script (does every signal connect at least two pins?) can find the 
candidates. I had been thinking before about adding summary pages to my 
visualizations that included this kind of information.

A human still needs to determine if the dead ends are legit---for 
example, some of the LinuxCNC example configurations have them, 
presumably as the equivalent of a labelled test point on a circuit 
board. With more intelligence about the components than I cared to build 
into my visualizer, one could also use software to detect missing 
connections, e.g., pins that must have a connection for the component to 
function but don't.

As for crossed connections, you're right, they'll probably require a 
human eyeball to detect at least in the near-term. That was one of my 
original intentions, to get a visual impression in which a "flier" might 
be easier to detect than an mistyped entry in a .hal file. For our 
machines, the HAL configuration breaks "almost" cleanly into patterns 
repeated for each axis so one can look for unexpected differences 
between the patterns as well as unexpected connections from one pattern 
to another.

As for a progress report (your next message) this flurry of messages is 
the first progress since last year:-)

Regards,
Kent


------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to