Still no luck...some more tests/info: basically there is no
communication between PC and device. The PCI board is recognized and
communication seems to work between PC and board. I can confirm the
device works but not via this board.
Anything else I can check?
Thanks
This is my gpib.conf file:
interface {
minor = 0 /* board index, minor = 0 uses /dev/gpib0, minor = 1
uses /dev/gpib1, etc. */
board_type = "ni_pci" /* type of interface board being used */
name = "teddy" /* optional name, allows you to get a board
descriptor using ibfind() */
pad = 2 /* primary address of interface */
sad = 0 /* secondary address of interface */
timeout = T30s /* timeout for commands */
eos = 0x0a /* EOS Byte, 0xa is newline and 0xd is carriage return */
set-reos = yes /* Terminate read if EOS */
set-bin = no /* Compare EOS 8-bit */
set-xeos = no /* Assert EOI whenever EOS byte is sent */
set-eot = yes /* Assert EOI with last byte on writes */
master = yes /* interface board is system controller *
/* settings for boards that lack plug-n-play capability */
/*base = 0*/ /* Base io ADDRESS */
/*irq = 0*/ /* Interrupt request level */
/*dma = 0*/ /* DMA channel (zero disables) */
/* pci_bus and pci_slot can be used to distinguish two pci boards
supported by the same driver */
/* pci_bus = 0 */
/* pci_slot = 7 */
/*master = yes*/ /* interface board is system controller */
}
Output of command lsmod | grep tnt:
tnt4882 16261 0
nec7210 9372 1 tnt4882
gpib_common 26340 2 nec7210,tnt4882
Output command lspci -n: (last 3 lines with the board ID on the last one)
03:03.0 0c00: 1106:3044 (rev 80)
03:04.0 0104: 105a:3373 (rev 02)
03:0b.0 0780: 1093:c801 (rev 02)
Output ibtest just after sending a few strings to the device: (VN is the
command to get the software version)
enter a string to send to your device: VN
sending string: VN
gpib status is:
ibsta = 0xc100 < ERR TIMO CMPL >
iberr= 6
EABO 6: Operation aborted
ibcntl = 0
Output command uname -r:
4.9.160-antix.2-486-smp
On 07.06.2019 17:59, W wrote:
>
> Ok, thanks for the info
>
> Device is a 0xc801 and vendor is 0x1093.
> tnt4882.h was already set for that device, so didn't change anything.
>
> I built the 2 packages. At the first glance, no compilation error.
> However, at the very top of the compilation messages, there is an error:
>
> "ERROR: Kernel configuration is invalid.
> include/generated/autoconf.h or include/config/auto.conf are missing."
>
> I checked these 2 files and they are not missing.
>
> The GPIB install doc says that the linux kernel should be recompiled.
> That's something I haven't done. Is that necessary?
>
> Thanks
>
> On 07.06.2019 11:53, Ansgar Kueckes wrote:
>> TNT5004 is the full-featured version of NI's GPIB chip which also
>> includes GPIB controller functions (the TNT5002 just implements
>> Talker/Listener).
>>
>> There is no "official" documentation on the TNT5004, since it is not
>> intended for separate sale. But you may get back on the documentation
>> of the TNT5002, which is available here:
>> http://www.ni.com/pdf/manuals/370595b.pdf
>>
>> That manual covers most of the chip functions. GPIB Controller
>> functions are mostly identical to those of a TNT4882, including the
>> register programming.
>>
>> The TNT5004 is supported in the Linux GPIB package by the current
>> TNT4882 driver. It *may* happen that not all boards which are using
>> that chip (especially OEM boards) are properly identified with their
>> PCI device code. That code is board specific, not chip specific. If
>> required, add the device code of your board in tnt4882.h and re-build
>> the package. IIRC the standard PCI device code for the PCI-GPIB
>> boards is 0xc801.
>>
>> -Ansgar
>>
>>> I did not see the TNT5004 driver listed. That's why I assume it's
>>> not supported.
>>>
>>> I do have a PCI board, quite old, dated year 2007. Strange enough,
>>> I can't find any datasheet about this TNT5004 chip.
>>>
>>> "pci device id": you mean adding it in file tnt4882.h?
>>>
>>> On 06.06.2019 23:53, Frank Mori Hess wrote:
>>>> On Thu, Jun 6, 2019 at 12:44 PM Frank Mori Hess <[email protected]> wrote:
>>>>> On Thu, Jun 6, 2019 at 11:12 AM W <[email protected]> wrote:
>>>>>> I just got one of these boards. I had a quick look at the Supported Hardware Matrix and cannot find any kernel driver
>>>>>> that would match the TNT5004 chip. I guess this board is just not supported, right?
>>>>> You should try just adding your pci device id to the tnt4882 driver.
>>>>> It will probably just work. In the worst case, they have dropped some
>>>>> backwards compatibility behavior from the tnt5004, and that will have
>>>>> to be worked around.
>>>> Hmm, actually I'm pretty sure your board is already supported. Why do
>>>> you say it is not in the supported hardware matrix? Is it because it
>>>> only lists "PCI-GPIB" and not "PCIe-GPIB"?
>>>>
>>>
>>>
>>> _______________________________________________
>>> Linux-gpib-general mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>>
>>
>>
>>
>> _______________________________________________
>> Linux-gpib-general mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
_______________________________________________
Linux-gpib-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.