>> Without seeing what's happening on your computer, we can not help.
>> Do what produces the error, then pastebin the dmesg output and any other
>> relevant logs, then email us the pastebin URL.
>>
>
> HAVE POSTED THE MESSAGES SEVERAL TIMES!!!! ¿SHOULD I POST AGAIN WHAT I
> POSTED ALREADY?
>
> cmon...!!

Richard, I think there might be a misunderstanding.  Every time that emc
crashes, it creates a dmesg file that tells what was going on and what
happened when it crashed.  the guys that are way better than I am can look
at this info and figure out what to do to fix the crashes.  Every time
something is different and it crashes with different errors, the dmesg will
be different telling what's going on.  so every time progress is made, we
(more like the other guys, wish i could personally help) will need a new
dmesg and copies of the current configurations being used in order to see
everything that is being done by the computer and where things go wrong.
Hope I'm able to help you and your situation, I just got an M5i20 card and
7i33, working on drawing and programming a board to go from 50 pin header on
7i33 to screw terminals to the wiring in the machine.

On Sun, Dec 21, 2008 at 7:54 PM, Richard Acosta <eyela...@gmail.com> wrote:

> El 21/12/2008 05:42 p.m., John Kasunich escribió:
> > Stuart Stevenson wrote:
> >
> >> On Sun, Dec 21, 2008 at 1:01 PM, Richard Acosta <eyela...@gmail.com>
> wrote:
> >>
> >>> Is nothing about lazyness... is about being tired of to do something
> >>> that is supossed to work.. and it does not! again and again and again.
> >>>
> >>> When going your lazy path i got the following two messages.
> >>>
> >>> "Acercar linea 10 en /usr/shareaxis/images/axis.ngc: bad character "x"
> used"
> >>>
> >> this message tells you there is something wrong near line 10 of the
> file:
> >> /usr/shareaxis/images/axis.ngc
> >>
> >> it even tells you what is wrong:
> >> bad character "x" used
> >>
> >> your response to this should be:
> >> open the file with an editor and look for an "x" character on or near
> line 10
> >> if you cannot figure out what the error is then post a copy of a few
> >> lines prior and a few lines past
> >>
> >> someone will try to help you
> >> people are trying to help you now - they just don't have enough
> information
> >>
> >
> > Something is fishy here though - isn't axis.ngc the EMC2 splash screen
> > program?  Hundreds of users are loading that g-code file every time they
> > start EMC, and it isn't causing errors.
> >
> > Also, "X" is a perfectly legitimate character in g-code.
> >
> > Stuart is exactly correct in that the proper action is to READ the
> > message, THINK about what it means, and LOOK for the cause of the
> problem.
> >
> > Regards,
> >
> > John Kasunich
> >
> I didn't wrote that file!!!
> it comes with the last install of EMC2 wich was suppossed to be working
> on a lazy path and a couple of clicks as i did this time.
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users
>
------------------------------------------------------------------------------
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to