On 23/07/17 17:06, Seth Pierson wrote:
I resolved this problem. It was completely logging related.

I had checked my ini file, and Debug was set to zero, logs were still coming through at the debug level.

I had also looked at run.py, the file that mklauncher calls to start machinekit. There was no cmd line options that changed the logging level (or so I thought). After a few hours of head banging I saw this line in run.py:
launcher.set_debug_level(5)


After checking, I found that the only instances of this in the machinekit repo are both commented out, so it should not occur.

https://github.com/machinekit/machinekit/blob/master/configs/ARM/BeagleBone/Fabrikator-Mini-CRAMPS/run.py#L10
https://github.com/machinekit/machinekit/blob/master/configs/ARM/BeagleBone/MendelMax-CRAMPS/run.py#L10

I suspect therefore that you are running an old config you got directly from machinekoder's repos or one that someone has altered.


I changed it on a whim to zero: No more debug logging. I had assumed that this was the log level for the launcher...It also changes the logging level of machinekit. Now I know.

Thank you for assisting me. It is much appreciated.
--
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 [email protected].
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

--
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 [email protected].
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

Reply via email to