So after a hour, the ADC froze. I opened up a terminal window and type realtime stop, followed by realtime start which killed the instance of machinekit that was running (became completely unresponsive. So I shut it down and started an instance of Machinekit from a terminal prompt. After homing the printer, and setting a bed and extruder temperature, the ADC did not report any values (stayed at 0). There was a couple of errors about DOS style characters in the config files (I dont know if that is an issue). What I did notice was an error that "libgcc_s.so.1 is required and something else about pthread.cancel. This was in trying to set M104 and M140. I still had to reboot the machine in order to get it to respond again.
On Monday, December 26, 2016 at 1:03:11 PM UTC-5, Charles Steinkuehler wrote: > > On 12/26/2016 2:54 AM, David Kalwar wrote: > > I have the exact same issue as described. Also using Blackbone > > beagle with cramps, two thermistors for Extruder and heated bed and > > both stop at the same time. > > > > As the machine is quite newly built I have not been able to > > investigate further. > > Since it looks like this issue takes a while to reproduce, if anyone > has this happen could you please run through the following diagnostic > process and report your results? You can stop at the first step that > results in working temperature readings (ie: no need to power down if > relaunching the application fixed things). > > 1) Launch machinekit from a console window, so you can see anything > printed by the hal_temp_bbb python script. > > ...once the thermistor readings get stuck: > > 2) Check to see if the hal_temp_bbb python script is running (via ps, > top or your favorite utility), and report any text that may have been > recently printed on the console window used to launch machinekit. > > 3) Shutdown and re-launch the machinekit application > > 4) Shutdown the machinekit application, the run "realtime stop" > followed by "realtime start" and re-launch machinekit > > 5) Perform a "warm" boot: "sudo reboot" and re-launch machinekit > > 6) Perform a "cold" boot: "sudo halt", remove power, reconnect power > and re-launch machinekit > > Please share your findings, and at least we'll have an idea of where > to look for problems. Perhaps the universe is telling me I should > design an ADC daughtercard for the CRAMPS board?!? ;-) > > -- > Charles Steinkuehler > cha...@steinkuehler.net <javascript:> > -- 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.
