On 24/08/17 21:06, Tim Vruwink wrote:
> Updated with the correct lspci output.
>
> On Thursday, August 24, 2017 at 2:47:31 PM UTC-5, Tim Vruwink wrote:
>
> Hi -
> I've got a server with two National Instrument cards, running RTAI
> and Comedi. It was a semi-automated setup, so I didn't actually see
> how the cards were setup, but apparently one of the cards isn't working.
> I am trying to determine what the problem might be - however I have
> very little experience with comedi.
>
>
> lspci shows:
>
> 05:01.0 Class ff00: National Instruments Unknown device 70aa
> 05:02.0 Class ff00: National Instruments PCI-6713
National Instruments device 70aa is a PCI-6229 (comedi device name
"pci-6229", which ought to be supported by the comedi ni_pcimio driver.
I don't know why comedi isn't creating a device for it. Are there any
more clues from dmesg?
>
>
> dmesg shows:
> ( irq = 17 )comedi0: ni_pcimio: possible problem - never saw adc
> go busy?
> comedi0: ni_pcimio: possible problem - never saw adc go busy?
>
> /proc/comedi shows:
>
> comedi version 0.7.76
> format string: "%2d: %-20s %-20s
> %4d",i,driver_name,board_name,n_subdevices
> 0: ni_pcimio pci-6713 14
> ni_pcimio:
> ni_pcimio
> 8255:
> 8255
>
> Not sure what the error message about adc going busy means. If
> anyone has some insights that would be helpful.
I don't know if it is a real problem or not, but it is related to the
CS5529 calibration ADC on the PCI-6713. It has some code that loops
around 100 times waiting for a "busy" bit to be set, with a 1
microsecond (or so) delay between each check. The "possible problem"
message is produced if the "busy" bit has not been seen after those 100
iterations. The "busy" bit will clear by itself some time after it is
set, so it may the case that the code misses it, or perhaps it is not
waiting long enough.
Does the message appear every time you read the calibration ADC
(subdevice 8), or only during initialization?
--
-=( Ian Abbott @ MEV Ltd. E-mail: <
abb...@mev.co.uk> )=-
-=( Web:
http://www.mev.co.uk/ )=-