The trouble with these error codes is they are printed by a generic
error function, which just gives the function within which the error arose and the return value. To get a proper log you need to wipe /var/log/linuxcnc.log before you start sudo echo "" > /var/log/linuxcnc.log will do it run with DEBUG=5 machinekit Then you will hopefully get a traceback and much better picture of what led to the error. Any segfaults should have more info appearing in /var/log/dmesg If there is a core dump into the PWD, so much the better. The only downside to the extra logging, is that if you are doing long prints with a card that is short of space, that could in itself cause problems. See what you can come up with. regards On 22/03/17 09:26, 'Marco Negrini' via
Machinekit wrote:
-- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to machinekit+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout. |
- [Machinekit] hal_init() failed: -12 'Marco Negrini' via Machinekit
- Re: [Machinekit] hal_init() failed: -1... schoone...@btinternet.com
- [Machinekit] Re: hal_init() failed: -1... 'Marco Negrini' via Machinekit
- Re: [Machinekit] Re: hal_init() fa... schoone...@btinternet.com
- Re: [Machinekit] Re: hal_init(... Bas de Bruijn
- Re: [Machinekit] Re: hal_i... 'Marco Negrini' via Machinekit
- Re: [Machinekit] Re: ... 'Marco Negrini' via Machinekit
- Re: [Machinekit] ... schoone...@btinternet.com
- Re: [Machinekit] ... Alexander Rössler
- Re: [Machinek... 'Marco Negrini' via Machinekit