Re: [Machinekit] Re: ADC and printing issues on the Beaglebone CRAMPS

[Charles Steinkuehler]

On 5/16/2017 2:56 PM, Jonathan Cohen wrote:
> So I had found that the same bugs that I was getting with ADC lockups were 
> occurring with a Replicape on another BBB.  I increased the output of my 
> power 
> supply (360W Amazon special) to 12.4 volts and the problems have so far 
> seemed 
> to go away (12 successful prints).  I have to test with the CRAMPS/BBB to see 
> if 
> it is the same case.  So throwing it out there,  what is the most popular way 
> that CRAMPS users power their printers ?

I typically use 5VSB from an ATX power supply to power the BBB.  I
have the CRAMPS setup to turn the ATX supply on/off under program
control, and drive the printer with the 12V rail from the ATX.

This requires a supply that works properly with no load, but most of
the newer supplies work fine.  Older ATX supplies that list a minimum
required load on the 5V and/or 12V lines should be avoided (or you
should make sure the minimum load requirement is met).

I also have several systems that use 5V 2A switching regulators (of
various make), and two systems using BeBoPr boards with on-board 5V
power (one from 12V and one from 24V motor power input).

-- 
Charles Steinkuehler
char...@steinkuehler.net

-- 
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] Re: ADC and printing issues on the Beaglebone CRAMPS

[Jonathan Cohen]

So I had found that the same bugs that I was getting with ADC lockups were 
occurring with a Replicape on another BBB.  I increased the output of my 
power supply (360W Amazon special) to 12.4 volts and the problems have so 
far seemed to go away (12 successful prints).  I have to test with the 
CRAMPS/BBB to see if it is the same case.  So throwing it out there,  what 
is the most popular way that CRAMPS users power their printers ?

On Monday, May 15, 2017 at 6:31:17 PM UTC-4, Daren Schwenke wrote:
>
> Tried to reproduce this without success.  Unplugged, plugged in the 
> thermistor a dozen times or so.
>
> Noticed it drops to -26C while unplugged, *which triggers the PID to turn 
> on, even at 'off' setpoint* in Machineface which logically sets the 
> target temperature to 0C.
> So when I plugged it back in I was reading 180C just from my efforts.  
> Easy fix for that is just modifying the thermistor table so 1C is the 
> lowest it can read: so 'off' doesn't ever trigger heating when the 
> thermistor goes away..
>
> When mine locked up before, it was reading about 6C (and it wasn't cold 
> here) so it must have locked up during the rapid transition down, or back 
> to 'normal'.
>
>
> On Tuesday, December 20, 2016 at 9:40:39 AM UTC-5, 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=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+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

[Machinekit] Re: ADC and printing issues on the Beaglebone CRAMPS

[Daren Schwenke]

Tried to reproduce this without success.  Unplugged, plugged in the 
thermistor a dozen times or so.

Noticed it drops to -26C while unplugged, *which triggers the PID to turn 
on, even at 'off' setpoint* in Machineface which logically sets the target 
temperature to 0C.
So when I plugged it back in I was reading 180C just from my efforts.  
Easy fix for that is just modifying the thermistor table so 1C is the 
lowest it can read: so 'off' doesn't ever trigger heating when the 
thermistor goes away..

When mine locked up before, it was reading about 6C (and it wasn't cold 
here) so it must have locked up during the rapid transition down, or back 
to 'normal'.


On Tuesday, December 20, 2016 at 9:40:39 AM UTC-5, 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=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+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

[Machinekit] Re: ADC and printing issues on the Beaglebone CRAMPS

[Brian Schousek]

So I just looked at the CRAMPS schematic and if that is what you are using, 
then it looks like the voltage driving the thermistor is the Vref from the 
Beagleboard which I think is 1.8 volts. As an EE, I have never 
aesthetically cared for the large 10 uF capacitor helping to filter the 
thermistor inputs. I could still see a latchup condition being triggered by 
intermittent thermistor connections, or perhaps some ground bounce by the 
same.

On Friday, May 12, 2017 at 10:20:54 PM UTC-5, Brian Schousek wrote:
>
> That almost feels like a problem with the input circuit on the Beagle 
> itself. Like perhaps some latch-up condition (see wiki.) 
>  If I had a Beagle Board my 
> debugging steps might include trying to duplicate the behavior by 
> intentionally disconnecting the thermistor while monitoring the ADC. If 
> this is a repeatable cause then that is wonderful news because you can then 
> go about finding the root cause.
>
>
> If the behavior is repeatable, try looking at the schematic or measuring 
> with a voltmeter to see what the voltage on the ADC pin is with the 
> thermistor removed. It might be that this voltage exceeds the ADC input 
> rating. In that case you might need some protection clamps (link 
> 
> )
>
> On Friday, May 12, 2017 at 6:26:45 PM UTC-5, Daren Schwenke wrote:
>>
>> I have a new data point for you all.
>> Broke the wires going to my thermistor today, and silly me starts to swap 
>> it out with the machine on.
>>
>> No ADC lockups for at least the last 9 months.
>>
>> Swapped out the themistor, go to check what it's reading, frozen ADC.
>>
>> So perhaps somehow a value at the open circuit (probably tied to ground 
>> at that point) range contributes to this.
>> Like if you have a heated bed configured, but not hooked up, then you get 
>> freezes?
>>
>> On Tuesday, December 20, 2016 at 9:40:39 AM UTC-5, 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=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+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

[Machinekit] Re: ADC and printing issues on the Beaglebone CRAMPS

[Brian Schousek]

That almost feels like a problem with the input circuit on the Beagle 
itself. Like perhaps some latch-up condition (see wiki.) 
 If I had a Beagle Board my 
debugging steps might include trying to duplicate the behavior by 
intentionally disconnecting the thermistor while monitoring the ADC. If 
this is a repeatable cause then that is wonderful news because you can then 
go about finding the root cause.


If the behavior is repeatable, try looking at the schematic or measuring 
with a voltmeter to see what the voltage on the ADC pin is with the 
thermistor removed. It might be that this voltage exceeds the ADC input 
rating. In that case you might need some protection clamps (link 

)

On Friday, May 12, 2017 at 6:26:45 PM UTC-5, Daren Schwenke wrote:
>
> I have a new data point for you all.
> Broke the wires going to my thermistor today, and silly me starts to swap 
> it out with the machine on.
>
> No ADC lockups for at least the last 9 months.
>
> Swapped out the themistor, go to check what it's reading, frozen ADC.
>
> So perhaps somehow a value at the open circuit (probably tied to ground at 
> that point) range contributes to this.
> Like if you have a heated bed configured, but not hooked up, then you get 
> freezes?
>
> On Tuesday, December 20, 2016 at 9:40:39 AM UTC-5, 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=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+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

Re: [Machinekit] Re: ADC and printing issues on the Beaglebone CRAMPS

[Charles Steinkuehler]

Sorry for being away from this thread for so long, I'm doing
"real-world" work away from the computer over the holiday break
(tiling a floor!) so I only get to check email a couple times a day.

On 12/28/2016 3:51 PM, David Kalwar wrote:
> 
> So the lines "buffer", "mode" and "scan_elements" are missing.

These are missing on my system when the ADC is working normally, I
think they are from a newer version of the ADC driver.  Can you verify
the files are also missing on your system when the ADC is working
correctly?

> So trying to read a oneshot value gives:
> 
> machinekit@beaglebone:~# cat /sys/bus/iio/devices/iio\:device0/in_voltage0_raw
> Resource temporarily unavailable

OK, so that means the kernel driver isn't responding to the sysfs
request.  This is what used to happen with the ADC driver, but it
would only fail for an individual sample, then go back to normal
operation.  It now seems to no longer recover.  :(

> After a "sudo reboot", the "iio:device0" was missing, it came back only after 
> starting machinekit.

That is expected.  The ADC driver isn't loaded until you load the iio
cape overlay, typically done in the setup.sh script of your machine
configuration.

> Now the "in_voltageX_raw" shows the values.
> 
> Really hope this helps!

It's looking like a kernel driver problem.  Anyone want to debug the
kernel driver, try back-porting the latest driver from 4.x, or make a
4.x kernel patched with Xenomai?  All three options should be
possible, but I'm not sure which is easiest or best.

-- 
Charles Steinkuehler
char...@steinkuehler.net

-- 
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.

Re: [Machinekit] Re: ADC and printing issues on the Beaglebone CRAMPS

[David Kalwar]

So our system locked up again. When we follow 
http://processors.wiki.ti.com/index.php/AM335x_ADC_Driver%27s_Guide

We get:

Code hier eingeb

machinekit@beaglebone:~# ls -al /sys/bus/iio/devices/iio:device0/

drwxr-xr-x5 root root0 Jan  1 00:00 .
drwxr-xr-x4 root root0 Jan  1 00:00 ..
-r--r--r--1 root root 4096 Jan  1 00:00 dev
-r--r--r--1 root root 4096 Jan  1 00:00 in_voltage0_raw
-r--r--r--1 root root 4096 Jan  1 00:00 in_voltage1_raw
-r--r--r--1 root root 4096 Jan  1 00:00 in_voltage2_raw
-r--r--r--1 root root 4096 Jan  1 00:00 in_voltage3_raw
-r--r--r--1 root root 4096 Jan  1 00:00 in_voltage4_raw
-r--r--r--1 root root 4096 Jan  1 00:00 in_voltage5_raw
-r--r--r--1 root root 4096 Jan  1 00:00 in_voltage6_raw
-r--r--r--1 root root 4096 Jan  1 00:00 in_voltage7_raw
-r--r--r--1 root root 4096 Jan  1 00:00 name
drwxr-xr-x2 root root0 Jan  1 00:00 power
lrwxrwxrwx1 root root0 Jan  1 00:00 subsystem -> 
../../../../../../bus/iio
-rw-r--r--1 root root 4096 Jan  1 00:00 uevent

en...

So the lines "buffer", "mode" and "scan_elements" are missing.

So trying to read a oneshot value gives:

machinekit@beaglebone:~# cat /sys/bus/iio/devices/iio\:device0/in_voltage0_raw
Resource temporarily unavailable


After a "sudo reboot", the "iio:device0" was missing, it came back only 
after starting machinekit.
Now the "in_voltageX_raw" shows the values.

Really hope this helps!



-- 
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.

Re: [Machinekit] Re: ADC and printing issues on the Beaglebone CRAMPS

[Robert Nelson]

On Wed, Dec 28, 2016 at 12:00 PM, Robert Nelson  wrote:
> On Wed, Dec 28, 2016 at 11:57 AM, Daren Schwenke
>  wrote:
>> I don't suppose either way.  I'm just adding my data points to the
>> conversation in hopes it might add as mine were different.  :)
>> If easy, I would load that version and see if it makes a difference (with
>> the caveats I've mentioned).  Could just be luck, but my luck has run out
>> much more quickly before.
>>
>> I tried to go to 8, but tried it on a BBGW which didn't work at all (the
>> image won't boot) and I haven't had the time to figure it out.
>
> BBGW, BBBW, BB Blue haven't been back-ported to the 3.8.13-bone tree..
> (wl18xx driver is the worst part of that)
>
> SO just use:
>
> BBGW:
>
> dtb=am335x-bonegreen.dtb
>
> BBBW:
>
> dtb=am335x-boneblack.dtb

I've added a patch so users won't have to do this..

https://github.com/RobertCNelson/bb-kernel/commit/6d969f205926d7329c7bfe277854812bd9d8d5bc

(no wl18xx wireless, but at-least the boards will bootup)

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
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.

Re: [Machinekit] Re: ADC and printing issues on the Beaglebone CRAMPS

[Robert Nelson]

On Wed, Dec 28, 2016 at 11:57 AM, Daren Schwenke
 wrote:
> I don't suppose either way.  I'm just adding my data points to the
> conversation in hopes it might add as mine were different.  :)
> If easy, I would load that version and see if it makes a difference (with
> the caveats I've mentioned).  Could just be luck, but my luck has run out
> much more quickly before.
>
> I tried to go to 8, but tried it on a BBGW which didn't work at all (the
> image won't boot) and I haven't had the time to figure it out.

BBGW, BBBW, BB Blue haven't been back-ported to the 3.8.13-bone tree..
(wl18xx driver is the worst part of that)

SO just use:

BBGW:

dtb=am335x-bonegreen.dtb

BBBW:

dtb=am335x-boneblack.dtb

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
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] Re: ADC and printing issues on the Beaglebone CRAMPS

[Daren Schwenke]

I don't suppose either way.  I'm just adding my data points to the 
conversation in hopes it might add as mine were different.  :)
If easy, I would load that version and see if it makes a difference (with 
the caveats I've mentioned).  Could just be luck, but my luck has run out 
much more quickly before.

I tried to go to 8, but tried it on a BBGW which didn't work at all (the 
image won't boot) and I haven't had the time to figure it out.

On Wednesday, December 28, 2016 at 9:59:02 AM UTC-5, Jonathan Cohen wrote:
>
> Do you suppose that the older Debian distribution is more stable than 8.6 
> ?  Or the previous kernel ?  Specifically, what kind of shielding do you 
> have on your cabling ?  I switched from the older version since I would get 
> lockups after very long prints but with this setup, it's only an hour to 
> two hours in and it fails.  I was tempted to perfom a mock print, e.g. no 
> filament, setting the extruder to 0 and the HBP to 35 and give it a whirl. 
>  Then try the extruder at 36 and the HBP at 0 to see if a crash occurs. 
>  This would be to see if a specific ADC channel is giving grief.  Is there 
> any possibility of oxidation occurring at the BBB analog in pins ?  I 
> haven't tried using a different channel.  
>
> On Wednesday, December 28, 2016 at 12:14:10 AM UTC-5, Daren Schwenke wrote:
>>
>> Better info:
>> machinekit@beaglebone:/usr/bin$ dpkg -l machinekit* 
>> ii  machinekit 0.1.14581376 armhfPC based motion controller 
>> for re
>> machinekit@beaglebone:/usr/bin$ cat /etc/dogtag 
>> Machinekit Debian Image 2016-02-07
>>
>>
>> On Wednesday, December 28, 2016 at 12:05:04 AM UTC-5, Daren Schwenke 
>> wrote:
>>>
>>> I've been running the following older debian 7 image for many months, 
>>> with many 6+ hour prints, and zero lockups (knock on wood).
>>> Not sure what version of this image this was, but here are some file 
>>> dates:
>>> machinekit@beaglebone:/etc$ uname -a
>>> Linux beaglebone 3.8.13-xenomai-r78 #1 Sat Sep 26 16:54:43 UTC 2015 
>>> armv7l GNU/Linux
>>> machinekit@beaglebone:/etc$ ls -al /usr/bin/linuxcnc
>>> -rwxr-xr-x 1 root root 24129 Mar 16  2016 /usr/bin/linuxcnc
>>> machinekit@beaglebone:/usr/bin$ ls -al /usr/bin/hal_temp_bbb
>>> -rwxr-xr-x 1 root root 9567 Mar 16  2016 /usr/bin/hal_temp_bbb
>>>
>>>
>>> I had experienced lockups in other versions, but my hardware has also 
>>> changed since then with better shielding and smoother power to the BBB.
>>> haltalk (using Machineface) in that build can consume 30% proc at times, 
>>> and this seems to cause random blobbies in the prints.
>>> The effect is worse at high segment speeds (160mm/sec, all arcs). 
>>>  Disconnecting mostly eliminates them and the print continues, so that's 
>>> what I do.  It works so I'm not messing with it.
>>>
>>>
>>> On Tuesday, December 20, 2016 at 9:40:39 AM UTC-5, 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=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 

[Machinekit] Re: ADC and printing issues on the Beaglebone CRAMPS

[Jonathan Cohen]

Do you suppose that the older Debian distribution is more stable than 8.6 ? 
 Or the previous kernel ?  Specifically, what kind of shielding do you have 
on your cabling ?  I switched from the older version since I would get 
lockups after very long prints but with this setup, it's only an hour to 
two hours in and it fails.  I was tempted to perfom a mock print, e.g. no 
filament, setting the extruder to 0 and the HBP to 35 and give it a whirl. 
 Then try the extruder at 36 and the HBP at 0 to see if a crash occurs. 
 This would be to see if a specific ADC channel is giving grief.  Is there 
any possibility of oxidation occurring at the BBB analog in pins ?  I 
haven't tried using a different channel.  

On Wednesday, December 28, 2016 at 12:14:10 AM UTC-5, Daren Schwenke wrote:
>
> Better info:
> machinekit@beaglebone:/usr/bin$ dpkg -l machinekit* 
> ii  machinekit 0.1.14581376 armhfPC based motion controller 
> for re
> machinekit@beaglebone:/usr/bin$ cat /etc/dogtag 
> Machinekit Debian Image 2016-02-07
>
>
> On Wednesday, December 28, 2016 at 12:05:04 AM UTC-5, Daren Schwenke wrote:
>>
>> I've been running the following older debian 7 image for many months, 
>> with many 6+ hour prints, and zero lockups (knock on wood).
>> Not sure what version of this image this was, but here are some file 
>> dates:
>> machinekit@beaglebone:/etc$ uname -a
>> Linux beaglebone 3.8.13-xenomai-r78 #1 Sat Sep 26 16:54:43 UTC 2015 
>> armv7l GNU/Linux
>> machinekit@beaglebone:/etc$ ls -al /usr/bin/linuxcnc
>> -rwxr-xr-x 1 root root 24129 Mar 16  2016 /usr/bin/linuxcnc
>> machinekit@beaglebone:/usr/bin$ ls -al /usr/bin/hal_temp_bbb
>> -rwxr-xr-x 1 root root 9567 Mar 16  2016 /usr/bin/hal_temp_bbb
>>
>>
>> I had experienced lockups in other versions, but my hardware has also 
>> changed since then with better shielding and smoother power to the BBB.
>> haltalk (using Machineface) in that build can consume 30% proc at times, 
>> and this seems to cause random blobbies in the prints.
>> The effect is worse at high segment speeds (160mm/sec, all arcs). 
>>  Disconnecting mostly eliminates them and the print continues, so that's 
>> what I do.  It works so I'm not messing with it.
>>
>>
>> On Tuesday, December 20, 2016 at 9:40:39 AM UTC-5, 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=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 

[Machinekit] Re: ADC and printing issues on the Beaglebone CRAMPS

[Daren Schwenke]

Better info:
machinekit@beaglebone:/usr/bin$ dpkg -l machinekit* 
ii  machinekit 0.1.14581376 armhfPC based motion controller for 
re
machinekit@beaglebone:/usr/bin$ cat /etc/dogtag 
Machinekit Debian Image 2016-02-07


On Wednesday, December 28, 2016 at 12:05:04 AM UTC-5, Daren Schwenke wrote:
>
> I've been running the following older debian 7 image for many months, with 
> many 6+ hour prints, and zero lockups (knock on wood).
> Not sure what version of this image this was, but here are some file dates:
> machinekit@beaglebone:/etc$ uname -a
> Linux beaglebone 3.8.13-xenomai-r78 #1 Sat Sep 26 16:54:43 UTC 2015 armv7l 
> GNU/Linux
> machinekit@beaglebone:/etc$ ls -al /usr/bin/linuxcnc
> -rwxr-xr-x 1 root root 24129 Mar 16  2016 /usr/bin/linuxcnc
> machinekit@beaglebone:/usr/bin$ ls -al /usr/bin/hal_temp_bbb
> -rwxr-xr-x 1 root root 9567 Mar 16  2016 /usr/bin/hal_temp_bbb
>
>
> I had experienced lockups in other versions, but my hardware has also 
> changed since then with better shielding and smoother power to the BBB.
> haltalk (using Machineface) in that build can consume 30% proc at times, 
> and this seems to cause random blobbies in the prints.
> The effect is worse at high segment speeds (160mm/sec, all arcs). 
>  Disconnecting mostly eliminates them and the print continues, so that's 
> what I do.  It works so I'm not messing with it.
>
>
> On Tuesday, December 20, 2016 at 9:40:39 AM UTC-5, 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=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+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.