I am in the process of designing a GPIB-Ethernet controller. You think
that will be of any interest?
I'm not sure who your market is. Hobbyists/hackers probably have different
requirements from real businesses and there are probably vast differences
from business to business.
My general
John Miles wrote:
I'll admit I'm kind of surprised at all of the users sticking up for RS-232.
I would've thought Abdul would be safe in abandoning his internal RS-232
data pathway between the Atmel and FTDI chip. What are some examples of
RS-232 hosts that need to talk to GPIB test
In message [EMAIL PROTECTED], Tom Van Baak writes:
Another example is GPS receivers. How would it be if they
only came with USB interfaces? Consumers wouldn't care,
they might even prefer it, but consider why it would drive us
engineers crazy.
The biggest mistake in USB, was that they didn't
If a device is USB-only you pretty much have to just plug it into a
wintel PC, install their OS-dependent software, and take what you're
given.
That's more accurate than I like, but some of the devices do work on Linux
and/or FreeBSD.
Devices that are simple enough to work over RS-232 are
In a message dated 4/17/2007 10:28:31 Pacific Daylight Time,
[EMAIL PROTECTED] writes:
What are some examples of
RS-232 hosts that need to talk to GPIB test equipment? Old/retired laptops
being used as dumb terminals? Legacy DOS apps that don't have any form of
USB support? Both?
I'll give you a recent example. I have a bunch of AC power
meters in my lab (model: Watts Up PRO) that have RS232
output and I wrote software that logs and plots the data. A
while back I picked up cheap serial-ethernet converters and
now I get all the same data over my house LAN. If these
Tom Van Baak [EMAIL PROTECTED] wrote:
If a device is USB-only you pretty much have to just plug it
into a wintel PC, install their OS-dependent software, and
take what you're given.
There's not much in the way of OS-dependent software, at least not in the
conventional sense of must install
I struck gold, I got two brand new units in original packaging with
manuals and cables for $90 on eBay a year ago or so... The seller had 2
in a Dutch auction for $90 each, and I was going to buy one but I missed
the deadline and the units did not sell... As I was writing him an email
to ask
The good news in that regard is that it appears FTDI pretty much owns
the USB-Serial adapter market, at least in the US, so we almost have a
standard there...
Didier KO4BB
Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Tom Van Baak writes:
Another example is GPS receivers. How
In message: [EMAIL PROTECTED]
Didier Juges [EMAIL PROTECTED] writes:
: The good news in that regard is that it appears FTDI pretty much owns
: the USB-Serial adapter market, at least in the US, so we almost have a
: standard there...
Well, there is the umodem standard... But 3/4 of
The public beta of the Windows configuration app for Prologix boards is
here:
http://www.ke5fx.com/gpib/setup.exe
This is actually a complete GPIB Toolkit release, but you can run the
PROLOGIX.EXE app independently of anything else. It's a standalone program
with no dependencies on the rest of
John,
You are too late by about a week or two, we had a rental for about 6
months and just sent it back last week... Forgot which model exactly,
but it was the 40 or 50 GHz model. Very spiffy.
I have a new Prologix controller on the way and I intend to check it on
everything I can lay my
In a message dated 4/15/2007 17:11:52 Pacific Daylight Time,
[EMAIL PROTECTED] writes:
Unfortunately, no. Updated firmware requires the new hardware.
Why are you not using hardware flow control? Which platform and application
are you using?
Hi Abdul,
we modified the board to have
In a message dated 4/16/2007 11:22:11 Pacific Daylight Time,
[EMAIL PROTECTED] writes:
In that case the new firmware will not be compatible at all. The new
hardware uses FTDI FT245R USB FIFO chip which has a parallel interface to
the micro. Host side USB drivers make it appear like a
In that case the new firmware will not be compatible at all. The new
hardware uses FTDI FT245R USB FIFO chip which has a parallel interface to
the micro. Host side USB drivers make it appear like a virtual serial port,
which is why all the serial port parameters can be ignored.
Abdul
Tom Van Baak said the following on 04/16/2007 05:41 PM:
In that case the new firmware will not be compatible at all. The new
hardware uses FTDI FT245R USB FIFO chip which has a parallel interface to
the micro. Host side USB drivers make it appear like a virtual serial port,
which is why
that
will be of any interest?
Abdul
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of John Ackermann N8UR
Sent: Monday, April 16, 2007 3:20 PM
To: Tom Van Baak; Discussion of precise time and frequency measurement
Subject: Re: [time-nuts] Prologix GPIB/USB converter help
Prologix said the following on 04/16/2007 07:17 PM:
I am in the process of designing a GPIB-Ethernet controller. You think that
will be of any interest?
Yes!!!
John
___
time-nuts mailing list
time-nuts@febo.com
In a message dated 4/16/2007 16:17:05 Pacific Daylight Time,
[EMAIL PROTECTED] writes:
Interesting. I used to sell a GPIB-RS232 version some years ago. Sales were
low since customers were clamoring for an USB version! But then I hadn't
discovered this crowd :-) Happy to take another look at
Prologix [EMAIL PROTECTED] wrote:
I am in the process of designing a GPIB-Ethernet controller. You think
that
will be of any interest?
Abdul
Yes, very much so. Of course price is key.
-ch
___
time-nuts mailing list
time-nuts@febo.com
Interesting. I used to sell a GPIB-RS232 version some years ago. Sales were
low since customers were clamoring for an USB version! But then I hadn't
discovered this crowd :-) Happy to take another look at it.
You'll find two sets of users. End-users want the latest
one-click, plug-n-play, PC
GPIB-ENET controllers by NI are on and off available on eBay for about
$200. I would think there is a market for an ethernet/GPIB controller in
that price range.
I also second the RS-232 option. While the USB-parallel interface chip
has the potential of being much faster (which is great when
As someone pointed out, a Serial-USB adapter cost only about $10
(www.geeks.com), and I would not mind having a GPIB-Serial device, and
attach a Serial-USB if I want to. Once you provide USB only, that's it,
it will be USB or nothing. The one drawback of a Serial only controller
is that
I'll admit I'm kind of surprised at all of the users sticking up for RS-232.
I would've thought Abdul would be safe in abandoning his internal RS-232
data pathway between the Atmel and FTDI chip. What are some examples of
RS-232 hosts that need to talk to GPIB test equipment? Old/retired laptops
Bill Janssen said the following on 04/14/2007 09:40 PM:
Don't know about the prologix bit but have had similar problems with
other equipment
and had to get my terminal program to ignore the 8th bit in the ASCII byte.
One of my terminal programs can be set to recognize 7 bits and ignore
the
I just got one and am trying to get it running under Linux. I have the
low-level configuration right (I think) and the device is recognized and
I can talk to it, after a fashion, on the /dev/ttyUSB0 port.
Hmmm ... it just works for me under Linux (Debian/Ubuntu), at least when it
is in the
Christopher Hoover said the following on 04/15/2007 12:17 PM:
I just got one and am trying to get it running under Linux. I have the
low-level configuration right (I think) and the device is recognized and
I can talk to it, after a fashion, on the /dev/ttyUSB0 port.
Hmmm ... it just works
I think the problem is most likely with the requirement for putting a
linefeed at the end of each transmission. I *think* I'm doing that, but
there's something there that's not working properly.
Yes, it is quite picky about line endings -- too much so IMNSHO.
My perl code that talks to my
Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of John Ackermann N8UR
Sent: Sunday, April 15, 2007 10:45 AM
To: Christopher Hoover
Cc: [EMAIL PROTECTED]
Subject: Re: [time-nuts] Prologix GPIB/USB converter help...
Well, I got my perl code, using Device::SerialPort
PROTECTED]
Behalf Of John Ackermann N8UR
Sent: Sunday, April 15, 2007 10:45 AM
To: Christopher Hoover
Cc: [EMAIL PROTECTED]
Subject: Re: [time-nuts] Prologix GPIB/USB converter help...
Well, I got my perl code, using Device::SerialPort, to work by *not*
selecting raw mode, but explicitly
-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of John Ackermann N8UR
Sent: Sunday, April 15, 2007 11:12 AM
To: Discussion of precise time and frequency measurement
Subject: Re: [time-nuts] Prologix GPIB/USB converter help...
I think I have it licked now. Getting the right
Well, I got my perl code, using Device::SerialPort, to work by *not*
selecting raw mode, but explicitly adding CRLF to the command string by
using chr() to append those characters. I have no idea why...
I'm using Device::SerialPort as well. In fact, I think I cribbed the
original code from
Just an update -- I have things working more-or-less OK now, after
messing around with line terminations and timing.
However, there *is* a problem, at least on one of my systems. If you
plug the adapter into the USB port with an active device on the GPIB
side, things go nuts and that yields (at
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of John Ackermann N8UR
Sent: Sunday, April 15, 2007 1:19 PM
To: Discussion of precise time and frequency measurement
Subject: Re: [time-nuts] Prologix GPIB/USB converter help...
Just an update -- I have things
John Miles said the following on 04/15/2007 04:37 PM:
You can try sending the command ++rst to force the Atmel chip to cold-boot
itself. That takes about 5 seconds.
Hmmm... that command isn't documented in the on-line manual. I'm
getting the feeling that one of the problems with this device
I wouldn't say they're horribly incomplete -- there's really not that much
to the firmware -- but there are a few things missing from his online
manual. The ++help text is always more up to date than the web page. ++rst
is really just meant for use with a firmware-flashing app, from what I
Hello,
Few points to consider while setting up the Prologix GPIB-USB controller:
1. All commands to the Prologix controller MUST be terminated by LF
(character 0x0A).
2. 4.x versions do NOT care about serial port parameters. Other than
the port number, of course.
3. 3.x
Hi John and Abdul --
Abdul, welcome to the list if you just joined -- I think a fair number
of your customers hang out here, so this is a great opportunity for us
to learn from each other.
And John, knowing that you're involved in the debugging is another
confidence booster.
Thanks to both of
In a message dated 4/15/2007 14:53:37 Pacific Daylight Time,
[EMAIL PROTECTED] writes:
3. 3.x versions require the serial port to be configured as
115200-8-N-1 with RTS/CTS (aka hardware) flow control. The flow control is
essential to avoid data corruption. A less elegant (and less
Hello Said,
Unfortunately, no. Updated firmware requires the new hardware.
Why are you not using hardware flow control? Which platform and application
are you using?
Regards,
Abdul
Hello Abdul,
is there a way to upgrade older boards with a new microcontroller?
I have a version 3.11
John Ackermann N8UR wrote:
Hi --
Sorry if this is a bit off-topic, but I know there are some folks here
who have used the nifty little Prologix GBIB dongles.
I just got one and am trying to get it running under Linux. I have the
low-level configuration right (I think) and the device is
41 matches
Mail list logo
