On 08/07/2018 07:34 PM, Peter C. Wallace wrote:
The following error really suggests a thread /configuration issue
(latency gone bad, missing thread etc etc) Almost nothing interface
hardware wise should be able to cause a following error.
I would try out stepconfs test proceedure to verify that the external
hardware/parallel ports are OK and also re-run the latency-test
Well, Peter nailed it with a configuration issue. You guys can dope
slap me now. I'd forgotten I'd commented out the HALFILE =
lin_curve.hal in my ini file. To compound the problem, I had to change
a couple of pins in my main hal file to make Andy's lincurve work with
my system. I commented out the old pin assignments and created new
ones. I decided to keep the old pin assignments commented out,
thankfully, so that if I wanted to calibrate the system without lincurve
running I had to uncomment the old and comment out the new. Which is
what I was planning on doing. I'd commented out the HALFILE statement
the day before and forgot I'd done that. Damn CRS.
Anyway, it's doing what it's supposed to now. Lesson learned. Don't do
stuff at the end of the day when you are tired. Stuff happens that way.
Mark
------------------------------------------------------------------------------
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
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users
