On Sun, 20 Dec 2015, Stephen Dubovsky wrote: > Date: Sun, 20 Dec 2015 21:59:26 -0500 > From: Stephen Dubovsky <[email protected]> > Reply-To: "Enhanced Machine Controller (EMC)" > <[email protected]> > To: "Enhanced Machine Controller (EMC)" <[email protected]> > Subject: Re: [Emc-users] Grounding Issues > > Peter, this is the root cause in the change of behavior between <=2.6 and > 2.7 w/ the 5i25+7i77 that a couple of us have been having (was discussed > here about a week ago)? I have noticed an occasional warning in the prior > version I was running (just at startup iirc.) I need to put some more > noise filters in, but my error is from the motor contactors pulling in when > I hit enable. The original dc servo drives have big contactors that > disconnect the motor from the drive and put a braking resistor across it > when you disable them (or hit a limit switch, etc.) Hitting the enable > (F2) causes those 3 big guys to pull in and reconnect the drives to the > motors. That causes the sserial glitch and trips the contactors right back > off. I can't get past that step. I haven't had time this week to play w/ > the inc/dec parameters like Andy Pugh suggested. > > Best, > Stephen
Yes I'm pretty sure this is the issue. Error reporting was improved in 2.7 but the error reporting of sticky error bits needs to be conditional on per cycle general (new) error flags and its not. I will try and get this fixed ASAP Also there is a small chance that updating the 5I25 sserial firmware from pre-35 versions to the current version 43 makes the RX UART a bit more sensitive to input noise as the internal processor and UART clock are changed from 33 MHz to 100 MHz. I do have a fix for this ( a 1/2 bit time digital filter on the RX UART input ) and will add this to all bitfiles containing sserial firmware but currently I have new bitfiles for the 5I25/6I25 and 7I76 and 7I77 here: http://freeby.mesanet.com/filtered.zip > > On Sun, Dec 20, 2015 at 1:34 PM, Peter C. Wallace <[email protected]> wrote: > >> >> I looked into the 2.7 source and see that there is a problem with sserial >> error reporting that makes some single errors fatal (because the error >> reporting does not distinguish between per cycle error bits and sticky >> error >> status bits) >> >> That is errors that caused just a random popup on 2.6 will cause 2.7 >> to shut down the sserial port (you still need a pretty bad noise spike to >> cause these errors but they should not be fatal) >> >> > ------------------------------------------------------------------------------ > _______________________________________________ > Emc-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/emc-users > Peter Wallace Mesa Electronics (\__/) (='.'=) This is Bunny. Copy and paste bunny into your (")_(") signature to help him gain world domination. ------------------------------------------------------------------------------ _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
