On 22-12-2013 20:04, Bas de Bruijn wrote:
>>>> I don't have a LinuxCNC system available to test at the moment, so
>>>> maybe
>>>> Charles
>>>> or someone else can comment.
>>>>
>>>> Maybe you're bitten by the ever changing device numbering scheme:
>>>> Have a
>>>> look in
>>>> /sys/devices for the name of the ocp.? node. The script assumes
>>>> it's
>>>> ocp.2, but maybe
>>>> it ocp.3 or something else in your situation.
>>> ocp.2 seems there
>>>
>>>> Or do a "find /sys/devices/ -name in_voltage4_raw" on the command
>>>> line
>>>> and see if
>>>> there is a difference with the path used in the script.
>>> linuxcnc@arm:~$ find /sys/devices/ -name in_voltage4_raw
>>> /sys/devices/ocp.2/44e0d000.tscadc/tiadc/iio:device0/in_voltage4_raw
>>>
>>> It’s there, but the script doesn’t work. :(
>> Weird, I cut and pasted that line from the file that I've used to
>> test
>> your board before shipment.
>>
>> And if you enter the following command (on the command line):
>>     cat `find /sys/devices/ -name in_voltage[346]_raw`
> now I get some values
>
> with a potmeter on J6 (3 positions)
> linuxcnc@arm:~$ cat `find /sys/devices/ -name in_voltage[346]_raw`
> 1817
> 1216
> 1043
> linuxcnc@arm:~$ cat `find /sys/devices/ -name in_voltage[346]_raw`
> 1819
> 1226
> 2965
> linuxcnc@arm:~$ cat `find /sys/devices/ -name in_voltage[346]_raw`
> 1796
> 1195
> 921
>
> with a potmeter on J7 (3 mositions)
> linuxcnc@arm:~$ cat `find /sys/devices/ -name in_voltage[346]_raw`
> 1844
> 1243
> 3410
> linuxcnc@arm:~$ cat `find /sys/devices/ -name in_voltage[346]_raw`
> 1843
> 1243
> 3611
> linuxcnc@arm:~$ cat `find /sys/devices/ -name in_voltage[346]_raw`
> 1848
> 1249
> 3608
>
> with a potmeter on J8 (3 positions)
> linuxcnc@arm:~$ cat `find /sys/devices/ -name in_voltage[346]_raw`
> 1851
> 1250
> 3571
> linuxcnc@arm:~$ cat `find /sys/devices/ -name in_voltage[346]_raw`
> 1845
> 1245
> 3374
> linuxcnc@arm:~$ cat `find /sys/devices/ -name in_voltage[346]_raw`
> 1843
> 1244
> 3385

Oops, where did 346 come from? The script had the right values! Use 456 to
read the proper inputs.

One of the problems with the TI ADC implementation is that it's slow to 
update.
First you always seem to get an old (queued?) value. So throw away the first
couple of readings after changing the input!

Furthermore I suggest that you use J8 (the one close to the reset 
button) for the
extruder reading as this channel seems to have the least 
crosstalk/disturbance
caused by the  touch-screen interface.

-- Bas

>
>
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
> _______________________________________________
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users


------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to