I'm out of practice with C, but shouldn't
viScanf(vi, %t, buf);
be
viScanf(vi, %t, buf);
[I'm not a language wizard.]
It looks OK to me. Arrays are passed by pointer.
buf is the same as buf[0]
The compiler should complain if it is wrong.
A quick google found examples without the .
Hal Murray wrote:
I'm out of practice with C, but shouldn't
viScanf(vi, %t, buf);
be
viScanf(vi, %t, buf);
[I'm not a language wizard.]
It looks OK to me. Arrays are passed by pointer.
buf is the same as buf[0]
The compiler should complain if it is wrong.
A quick google found examples
I think SiSoft Sandra will tell you the device id (assuming its PCI or more
recent), and then you should be able to search for the device ID to find the
drivers.
I assume you've already tried the Panasonic Web Site for drivers?
Dave
-Original Message-
From: time-nuts-boun...@febo.com
If buf is defined as an array (eg. char buf[100];)
its name is a constant that points to the start of the
array. You can write it either as buf, or buf.
-Chuck Harris
Brent Gordon wrote:
I'm out of practice with C, but shouldn't
viScanf(vi, %t, buf);
be
viScanf(vi, %t, buf);
Brent
Date: Sat, 24 Oct 2009 09:35:03 +1300
From: Bruce Griffiths bruce.griffi...@xtra.co.nz
Subject: Re: [time-nuts] LPRO101 Lamp Exciter Frequency
To: Discussion of precise time and frequency measurement
time-nuts@febo.com
Message-ID: 4ae21377.7070...@xtra.co.nz
Content-Type: text/plain;
If buf is defined as an array (eg. char buf[100];) its name is a
constant that points to the start of the array. You can write it
either as buf, or buf.
Not quite. You need buf[0]
buf is a pointer to the array. (first element)
buf is a pointer to that pointer.
buf[0] is a pointer to
I think you are reading the second harmonic.
I would recall that:
- the LPRO loses lock if the lamp gets too hot. This is
indicated by a color more close to red than to pink (which is
normal). This could happen if the temperature control circuit
has some fault. I would suggest cheching the
Not quite. You need buf[0]
buf is a pointer to the array. (first element)
buf is a pointer to that pointer.
buf[0] is a pointer to the first element of the array.
Hal, try the following with your C compiler...
#include stdio.h
void main ()
{
char buf[100] = { 3,1,4,1,5 };
Hal Murray wrote:
If buf is defined as an array (eg. char buf[100];) its name is a
constant that points to the start of the array. You can write it
either as buf, or buf.
Not quite. You need buf[0]
buf is a pointer to the array. (first element)
buf is a pointer to that pointer.
At 04:46 PM 10/24/2009, Tom Van Baak wrote...
Not quite. You need buf[0]
buf is a pointer to the array. (first element)
buf is a pointer to that pointer.
buf[0] is a pointer to the first element of the array.
Hal, try the following with your C compiler...
BASIC is _so_ much easier. :-)
Roberto Barrios wrote:
Date: Sat, 24 Oct 2009 09:35:03 +1300
From: Bruce Griffiths bruce.griffi...@xtra.co.nz
Subject: Re: [time-nuts] LPRO101 Lamp Exciter Frequency
To: Discussion of precise time and frequency measurement
time-nuts@febo.com
Message-ID: 4ae21377.7070...@xtra.co.nz
t...@leapsecond.com said:
Hal, try the following with your C compiler...
...
mag...@rubidium.dyndns.org said:
Not quite.
...
Argh/blush. Sigh.
Thanks for the correction, and apologies for cluttering up the list with
bogus info.
I fished out my old copy of Andrew Koenig's C Traps and
Group,
Completed circumnavigation of the world via Singapore with a hand-held
Garmin 60 CSx GPS receiver.
Set it to record at 6 minute intervals, and marked waypoints. Used about 6%
of track space with 4 GB micro SD card.
Had no trouble with aircraft interference. Talked to the Captain after a
Roberto Barrios wrote:
Date: Sun, 25 Oct 2009 10:24:38 +1300
From: Bruce Griffiths bruce.griffi...@xtra.co.nz
Subject: Re: [time-nuts] LPRO101 Lamp Exciter Frequency
To: Discussion of precise time and frequency measurement
Message-ID: 4ae37096.5030...@xtra.co.nz
Content-Type:
I'm trying to construct a stratum-1 NTP server, using a Garmin 18x LVC
GPS unit (with the PPS line wired to the serial port's carrier pin),
running on an OpenBSD system (current release, 4.6). It's not working
for me (yet), and I could use some advice from anyone who has actually
managed to get
On Sat, Oct 24, 2009 at 8:52 PM, Rich Wales ri...@richw.org wrote:
Despite the claim (see above) that gpsd uses OpenBSD's NMEA line discipline
to export PPS time stamps, I can't find any substantiation for this in
the gpsd source code. I tried enabling the NMEA line discipline manually
on the
Chris Kuethe wrote:
I removed the special-casing that would cause gpsd to activate the nmea(4)
line discipline. The way I'm now doing this is to get ldattach to relay
through a pty, and gpsd can read that pty. you can do something like this
in /etc/rc.local: gpsd -n $(ldattach -t dcd
Hmf. Try this patch to ldattach
Index: ldattach.c
===
RCS file: /cvs/src/sbin/ldattach/ldattach.c,v
retrieving revision 1.12
diff -N -u -p ldattach.c
--- ldattach.c 6 May 2009 18:21:23 - 1.12
+++ ldattach.c 25 Oct 2009
Despite the claim (see above) that gpsd uses OpenBSD's NMEA line
discipline to export PPS time stamps, I can't find any substantiation
for this in the gpsd source code. I tried enabling the NMEA line
discipline manually on the GPS's serial port (via the ldattach
command), but this made gpsd
19 matches
Mail list logo
