gmane.linux.hardware.gpib.general archive

404 archived articles, newest first (page 3 of 5). Latest articles →

Re: Reinitializing controller with ibonl()
Sat, 2 Mar 2024 11:12:21 +0100
dave penkler <[email protected]> • #2009
Reinitializing controller with ibonl()
Mon, 26 Feb 2024 04:38:53 +0000 (UTC)
Michael K via Linux-gpib-general <[email protected]> • #2008
WaitSRQ spurios triggers
Thu, 7 Dec 2023 17:22:48 +0000 (UTC)
Michael K via Linux-gpib-general <[email protected]> • #2007
Re: ibcnt reset after ibtmo() call
Mon, 6 Nov 2023 20:40:30 +0100
dave penkler <[email protected]> • #2006
ibcnt reset after ibtmo() call
Mon, 6 Nov 2023 17:14:31 +0000 (UTC)
Michael K via Linux-gpib-general <[email protected]> • #2005
Seeking testers with ines board
Mon, 9 Oct 2023 18:27:20 +0200
dave penkler <[email protected]> • #2004
Re: INES GPIB-PCI board: bugs in ver. 4.3.4 and above
Thu, 5 Oct 2023 21:02:19 +0200
dave penkler <[email protected]> • #2003
Re: Agilent 82357B repeatable hard failure
Tue, 3 Oct 2023 16:53:10 +0200
dave penkler <[email protected]> • #2002
Re: Agilent 82357B repeatable hard failure
Tue, 3 Oct 2023 10:00:50 -0400
Jim Houston <[email protected]> • #2001
Re: Agilent 82357B repeatable hard failure
Mon, 2 Oct 2023 14:31:48 +0200
dave penkler <[email protected]> • #2000
Re: R&S CMU200 requires both primary and secondary addresses
Mon, 2 Oct 2023 14:08:19 +0200
dave penkler <[email protected]> • #1999
R&S CMU200 requires both primary and secondary addresses
Sun, 1 Oct 2023 21:43:47 +0000 (UTC)
Michael K via Linux-gpib-general <[email protected]> • #1998
Re: Agilent 82357B repeatable hard failure
Sun, 1 Oct 2023 08:48:12 -0400
Jim Houston <[email protected]> • #1997
Re: Agilent 82357B repeatable hard failure
Sat, 30 Sep 2023 10:03:09 +0200
dave penkler <[email protected]> • #1996
Re: Agilent 82357B repeatable hard failure
Sat, 30 Sep 2023 09:48:59 +0200
dave penkler <[email protected]> • #1995
Re: Agilent 82357B repeatable hard failure
Fri, 29 Sep 2023 08:46:15 -0400
Jim Houston <[email protected]> • #1994
Re: Agilent 82357B repeatable hard failure
Fri, 29 Sep 2023 10:58:57 +0200
dave penkler <[email protected]> • #1993
Re: Agilent 82357B repeatable hard failure
Thu, 28 Sep 2023 20:58:24 -0400
Jim Houston <[email protected]> • #1992
Re: Agilent 82357B repeatable hard failure
Thu, 28 Sep 2023 20:47:47 -0400
Jim Houston <[email protected]> • #1991
Re: Agilent 82357B repeatable hard failure
Thu, 28 Sep 2023 23:25:47 +0000 (UTC)
Michael K via Linux-gpib-general <[email protected]> • #1990
Re: Agilent 82357B repeatable hard failure
Thu, 28 Sep 2023 19:13:12 +0200
dave penkler <[email protected]> • #1989
Re: Agilent 82357B repeatable hard failure
Thu, 28 Sep 2023 17:59:03 +0200
dave penkler <[email protected]> • #1988
Re: Agilent 82357B repeatable hard failure
Wed, 27 Sep 2023 14:37:04 +0000 (UTC)
Michael K via Linux-gpib-general <[email protected]> • #1987
Re: Agilent 82357B repeatable hard failure
Wed, 27 Sep 2023 13:01:16 +0200
dave penkler <[email protected]> • #1986
Re: Agilent 82357B repeatable hard failure
Tue, 26 Sep 2023 22:05:37 +0000 (UTC)
Michael K via Linux-gpib-general <[email protected]> • #1985
Re: Agilent 82357B repeatable hard failure
Tue, 26 Sep 2023 19:36:29 +0200
dave penkler <[email protected]> • #1984
Re: Speed difference between Agilent 82357B and NI GPIB-USB-HS
Tue, 26 Sep 2023 09:38:04 +0200
dave penkler <[email protected]> • #1983
Re: Agilent 82357B repeatable hard failure
Tue, 26 Sep 2023 09:23:47 +0200
dave penkler <[email protected]> • #1982
Speed difference between Agilent 82357B and NI GPIB-USB-HS
Mon, 25 Sep 2023 23:26:14 +0000 (UTC)
Michael K via Linux-gpib-general <[email protected]> • #1981
Re: Agilent 82357B repeatable hard failure
Mon, 25 Sep 2023 18:20:51 +0200
dave penkler <[email protected]> • #1980
Re: Agilent 82357B repeatable hard failure
Mon, 25 Sep 2023 12:13:20 +0200
"Michael Dittrich" <[email protected]> • #1979
Re: Agilent 82357B repeatable hard failure
Mon, 25 Sep 2023 10:22:50 +0200
dave penkler <[email protected]> • #1978
Re: Agilent 82357B repeatable hard failure
Sun, 24 Sep 2023 20:50:39 -0400
Jim Houston <[email protected]> • #1977
Re: Agilent 82357B repeatable hard failure
Mon, 25 Sep 2023 01:48:48 +0200
"Michael Dittrich" <[email protected]> • #1976
Re: Agilent 82357B repeatable hard failure
Fri, 22 Sep 2023 17:05:53 +0000 (UTC)
Michael K via Linux-gpib-general <[email protected]> • #1975
Re: Agilent 82357B repeatable hard failure
Fri, 22 Sep 2023 12:30:17 -0400
Jim Houston <[email protected]> • #1974
Re: Agilent 82357B repeatable hard failure
Fri, 22 Sep 2023 16:07:41 +0000 (UTC)
Michael K via Linux-gpib-general <[email protected]> • #1973
Re: Agilent 82357B repeatable hard failure
Fri, 22 Sep 2023 09:35:45 -0400
Jim Houston <[email protected]> • #1972
Re: missing "System.map" and depmod skipped
Wed, 13 Sep 2023 09:47:17 +0200
dave penkler <[email protected]> • #1971
Re: missing "System.map" and depmod skipped
Wed, 13 Sep 2023 05:51:19 +0000
Saif Mostafa <[email protected]> • #1970
Re: missing "System.map" and depmod skipped
Fri, 1 Sep 2023 14:47:17 +0200
dave penkler <[email protected]> • #1969
Re: INES GPIB-PCI board: bugs in ver. 4.3.4 and above
Tue, 29 Aug 2023 15:04:05 +0200
dave penkler <[email protected]> • #1968
INES GPIB-PCI board: bugs in ver. 4.3.4 and above
Tue, 29 Aug 2023 09:18:50 +0200
[email protected] • #1967
missing "System.map" and depmod skipped
Wed, 23 Aug 2023 23:25:00 -0500
Saif Mostafa <[email protected]> • #1966
Re: Agilent 82357B repeatable hard failure
Wed, 23 Aug 2023 17:12:39 -0400
Jim Houston <[email protected]> • #1965
Re: Agilent 82357B repeatable hard failure
Sun, 30 Jul 2023 17:18:42 -0400
Jim Houston <[email protected]> • #1964
Fwd: Agilent 82357B repeatable hard failure
Sun, 30 Jul 2023 13:02:21 -0400
Jim Houston <[email protected]> • #1963
Re: Agilent 82357B repeatable hard failure
Sat, 29 Jul 2023 17:55:29 -0400
Jim Houston <[email protected]> • #1962
Re: Agilent 82357B repeatable hard failure
Thu, 27 Jul 2023 18:13:04 +0200
dave penkler <[email protected]> • #1961
Re: Agilent 82357B repeatable hard failure
Wed, 26 Jul 2023 16:58:05 -0400
Jim Houston <[email protected]> • #1960
Strange errors with NI GPIB-USB-HS
Mon, 1 Aug 2022 15:01:32 +0200
Ladman Jakub <[email protected]> • #1959
Agilent 82357B repeatable hard failure
Thu, 20 Jul 2023 15:53:30 -0400
Jim Houston <[email protected]> • #1958
Re: Unsure why Agilent 82357B isn't working
Wed, 14 Jun 2023 00:19:23 +0000 (UTC)
Michael K via Linux-gpib-general <[email protected]> • #1957
Unsure why Agilent 82357B isn't working
Thu, 8 Jun 2023 15:36:38 -0700
Brandon Gunn <[email protected]> • #1956
Re: Problem working with Python 3.10
Sat, 3 Jun 2023 10:33:36 +0200
Wilhelm Kusian <[email protected]> • #1955
Re: Problem working with Python 3.10
Thu, 1 Jun 2023 10:26:50 +0930
"quips_roofing.0t--- via Linux-gpib-general" <[email protected]> • #1954
Re: Problem working with Python 3.10
Wed, 31 May 2023 00:01:31 +0000 (UTC)
Michael K via Linux-gpib-general <[email protected]> • #1953
Problem working with Python 3.10
Sun, 28 May 2023 14:30:41 +0930
"quips_roofing.0t--- via Linux-gpib-general" <[email protected]> • #1952
Re: [EXTERNAL] Re: GPIB as a pure slave
Mon, 8 May 2023 18:02:38 +0200
Vladimir Vassilev <[email protected]> • #1951
Re: [EXTERNAL] Re: GPIB as a pure slave
Mon, 8 May 2023 16:06:21 +0200
"marcello.carla" <[email protected]> • #1950
Re: [EXTERNAL] Re: GPIB as a pure slave
Mon, 8 May 2023 12:28:37 +0200
Vladimir Vassilev <[email protected]> • #1949
Re: Problems with Electronomikon gpib_bitbang
Tue, 21 Feb 2023 15:26:50 +0100
"marcello.carla" <[email protected]> • #1948
Problems with Electronomikon gpib_bitbang
Tue, 21 Feb 2023 22:12:23 +1030
"quips_roofing.0t--- via Linux-gpib-general" <[email protected]> • #1947
Re: Making the linux-gpib pc a server
Sun, 12 Feb 2023 19:55:48 +0100
Jakub Ladman <[email protected]> • #1946
Re: Making the linux-gpib pc a server
Sun, 12 Feb 2023 06:51:45 -0500
Dale Smith <[email protected]> • #1945
Making the linux-gpib pc a server
Sun, 12 Feb 2023 10:40:40 +0100
Jakub Ladman <[email protected]> • #1944
Re: [EXTERNAL] Re: GPIB as a pure slave
Mon, 30 Jan 2023 17:45:37 +0100
Stefan Olejnik <[email protected]> • #1943
Re: [EXTERNAL] Re: GPIB as a pure slave
Wed, 18 Jan 2023 22:06:27 +0100
Stefan Olejnik <[email protected]> • #1942
Re: [EXTERNAL] Re: GPIB as a pure slave
Tue, 17 Jan 2023 13:20:07 -0500
Frank Mori Hess <[email protected]> • #1941
Re: [EXTERNAL] Re: GPIB as a pure slave
Mon, 16 Jan 2023 18:18:17 +0100
Stefan Olejnik <[email protected]> • #1940
Re: [EXTERNAL] Re: GPIB as a pure slave
Mon, 16 Jan 2023 14:01:54 +0100
dave penkler <[email protected]> • #1939
Re: [EXTERNAL] Re: GPIB as a pure slave
Sun, 15 Jan 2023 09:42:38 +0100
Stefan Olejnik <[email protected]> • #1938
Re: GPIB as a pure slave
Fri, 13 Jan 2023 13:50:54 +0100
dave penkler <[email protected]> • #1937
Re: Problem compiling driver after Ubuntu update
Fri, 13 Jan 2023 11:12:10 +0100
dave penkler <[email protected]> • #1936
Problem compiling driver after Ubuntu update
Fri, 13 Jan 2023 05:53:37 +0000
Søren Koch via Linux-gpib-general <[email protected]> • #1935
GPIB as a pure slave
Tue, 10 Jan 2023 15:34:11 +0000
"Olejnik, Stefan" <[email protected]> • #1934
Re: Clone NI GPIB-USB-HS
Sun, 11 Dec 2022 18:34:52 +0100
dave penkler <[email protected]> • #1933
Clone NI GPIB-USB-HS
Sun, 11 Dec 2022 15:34:58 +0000 (UTC)
Michael K via Linux-gpib-general <[email protected]> • #1932
Re: gpib_bitbang kernel exceptions and deadlocks in 4.3.5 releases now fixed in r2046
Thu, 1 Dec 2022 16:10:25 +0100
"marcello.carla" <[email protected]> • #1931
gpib_bitbang kernel exceptions and deadlocks in 4.3.5 releases now fixed in r2046
Thu, 1 Dec 2022 12:38:55 +0100
Vladimir Vassilev <[email protected]> • #1930
Re: ibwt() / ibrd() immediatly following ibclr()
Thu, 17 Nov 2022 13:45:16 +0100
dave penkler <[email protected]> • #1929
ibwt() / ibrd() immediatly following ibclr()
Wed, 16 Nov 2022 19:20:12 +0000 (UTC)
Michael K via Linux-gpib-general <[email protected]> • #1928
Re: HP 59306A problem with the gpib_bitbang driver in the 4.3.4 and 4.3.5 releases
Tue, 8 Nov 2022 00:35:44 +0100
Vladimir Vassilev <[email protected]> • #1927
HP 59306A problem with the gpib_bitbang driver in the 4.3.4 and 4.3.5 releases
Fri, 4 Nov 2022 20:17:26 +0100
Vladimir Vassilev <[email protected]> • #1926
Re: Problem with device communication
Mon, 17 Oct 2022 13:39:26 +0200
Vladimir Vassilev <[email protected]> • #1925
Re: async reads and timeouts
Sun, 7 Aug 2022 21:16:30 +0000 (UTC)
Michael K via Linux-gpib-general <[email protected]> • #1924
Re: async reads and timeouts
Sun, 7 Aug 2022 20:58:17 +0000 (UTC)
Michael K via Linux-gpib-general <[email protected]> • #1923
Re: Strange errors with NI GPIB-USB-HS
Sat, 6 Aug 2022 17:47:27 +0200
Jakub Ladman <[email protected]> • #1922
Re: async reads and timeouts
Thu, 4 Aug 2022 17:33:05 -0400
Frank Mori Hess <[email protected]> • #1921
Re: Strange errors with NI GPIB-USB-HS
Thu, 4 Aug 2022 01:15:50 +0200
Jakub Ladman <[email protected]> • #1920
Re: Strange errors with NI GPIB-USB-HS
Wed, 3 Aug 2022 22:06:20 +0200
Jakub Ladman <[email protected]> • #1919
Re: Strange errors with NI GPIB-USB-HS
Wed, 3 Aug 2022 21:34:02 +0200
dave penkler <[email protected]> • #1918
Re: Strange errors with NI GPIB-USB-HS
Wed, 3 Aug 2022 09:12:12 +0200
Jakub Ladman <[email protected]> • #1917
Re: Strange errors with NI GPIB-USB-HS
Mon, 1 Aug 2022 21:18:33 +0200
dave penkler <[email protected]> • #1916
Re: python3.10 breaking changes
Sun, 26 Jun 2022 22:53:21 -0700
Lee Nelson <[email protected]> • #1915
Re: python3.10 breaking changes
Mon, 27 Jun 2022 07:29:03 +0200
dave penkler <[email protected]> • #1914
python3.10 breaking changes
Sun, 26 Jun 2022 19:45:05 -0700
Lee Nelson <[email protected]> • #1913
FYI: New Fedora RPMs available
Wed, 15 Jun 2022 18:45:05 +0000 (UTC)
Michael K via Linux-gpib-general <[email protected]> • #1912
Package for debian?
Sun, 29 May 2022 09:36:59 +0200
"Michael Dittrich" <[email protected]> • #1911
Package for debian?
Sun, 29 May 2022 09:45:19 +0200
"Michael Dittrich" <[email protected]> • #1910
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.