I am using the same call, hal_temp_bbb script that is in the most recent build. I just started a print and 30 min in, crashed. I had tried putting a passive filter on the thermistor wire but that did not help it either. Is it possible that there is some amount of oxidation occurring on the analog pins after some use that may be causing this sort of problem ? I was thinking to try a different set of pins (e.g. Therm 2) and see if it continues.
On Saturday, December 24, 2016 at 4:58:44 PM UTC-5, Charles Steinkuehler wrote: > > What script are you using to read the ADC? It needs to be able to > continue through the occasional errors encountered when reading the > ADC value via sysfs. If these errors are not handled, you will get > behavior like what you're seeing (the user-mode python code crashes > when the kernel throws an I/O Error, at which point the temperatures > stop updating). > > I use the hal_temp_bbb script that comes with Machinekit in my > personal configs and haven't had problems: > > > https://github.com/cdsteinkuehler/machine-configs/blob/master/configs/MendelMax/MendelMax.hal#L32-L34 > > > On 12/20/2016 8:40 AM, Jonathan Cohen wrote: > > I took my printer down since the hot end was locking up during a long > print. I > > have posted about this over the past year. I recently purchased a new > microsd > > card, put on a new image of Jessie 8.6. I also replaced the hotend > thermistor, > > redid all of the wiring to decrease the effect of EMI near the cartridge > heater > > leads. I got off one reasonable 4hr test print. However, on an > overnight, the > > ADC locked up at maybe the 5 hr mark on a 6.5 hr print (not heating). > So, I > > recall Charles writing about the ADC driver being a bit temperamental, > sensitive > > to over-voltage and such. I am powering the beaglebone through the AUX > in on > > the CRAMPS board through a 5V LM2596 buck regulator > > ( > https://www.amazon.com/gp/product/B00WEBJRE8/ref=oh_aui_search_detailpage?ie=UTF8&psc=1). > > > > I recently went a made sure that it was set to 5V to be sure. Prior > to that I > > was using a 5V DC adapter where I still had this issue. My cable > management is > > reasonable so I do not think wires are moving about. > > > > 1. So what I want to know is whether this is a particular problem that > is always > > going to be sporadic during a print ? > > 2. Is there no straightforward solution ? I tried several microSD > cards, > > thinking it was a quality issue or corruption of the card but that did > not fix > > it. I also though my thermistor may have been bad, or the wiring out > both so I > > swapped that out, to no avail. > > 3. There was mention of a buggy ADC driver in an older kernel. Has > this same > > driver been brought along to the new Debian release / > > 4. I did see in the forums about using an external ADC, is this possible > to > > implement on the CRAMPS (I am not sure if the SPI is broken out). > > 5. Is this an issue that everyone who uses the Beaglebone/CRAMPS combo, > sees ? > > 6. I slice in Cura, is this a G-code problem ? ( I am not using the > remapped > > G-codes0 > > 7. 5. Does this occur with the Replicape board ? > > 8. Is it time to throw in the towel ? > > > > I really like the using an embedded platform for running a printer. > This is a > > bit frustrating as I can not figure it out. Everyone on this board has > been > > really helpful. I have scoured the board looking for solutions, but am > still at > > a loss (probably since I am not a programmer or engineer !) > > > > Thanks, > > > > Jonathan > > > > -- > > 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+...@googlegroups.com <javascript:> > > <mailto:machinekit+unsubscr...@googlegroups.com <javascript:>>. > > Visit this group at https://groups.google.com/group/machinekit. > > For more options, visit https://groups.google.com/d/optout. > > > > > -- > 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.
