Empathy List Archives

MS

Mark Sims

Mon, Jul 6, 2009 4:54 PM

The Prologix adapter has a ++addr command for changing the GPIB address. You can select different instruments that way.

Unfortunately, the version I looked seems to have a potentially fatal flaw. When you change the ++addr, the device writes the internal microprocessor EEPROM. The EEPROM is speced a 1 million write cycles. If you changed instruments at once a second, in under two weeks the chip could be toast. My app could have worn out the chip in under a day...

All this assumes that Prologix did not implement some sort of elaborate wear leveling scheme in their software, but I suspect not. They seem to have intended one to set up the device to talk to one instrument then save that configuration in the chip. Dynamically hammering the thing to death with address changes was not the intention of the ++addr command.

I wound up implementing a GPIB controller (with Prologix emulator) with my MegaDonkey touch screen LCD controller. It even included a HPGL/PCL plotter routine to draw instrument plots on the 160x80 LCD.

Windows Live™ SkyDrive™: Get 25 GB of free online storage.
http://windowslive.com/online/skydrive?ocid=TXT_TAGLM_WL_SD_25GB_062009

The Prologix adapter has a ++addr command for changing the GPIB address. You can select different instruments that way. Unfortunately, the version I looked seems to have a potentially fatal flaw. When you change the ++addr, the device writes the internal microprocessor EEPROM. The EEPROM is speced a 1 million write cycles. If you changed instruments at once a second, in under two weeks the chip could be toast. My app could have worn out the chip in under a day... All this assumes that Prologix did not implement some sort of elaborate wear leveling scheme in their software, but I suspect not. They seem to have intended one to set up the device to talk to one instrument then save that configuration in the chip. Dynamically hammering the thing to death with address changes was not the intention of the ++addr command. I wound up implementing a GPIB controller (with Prologix emulator) with my MegaDonkey touch screen LCD controller. It even included a HPGL/PCL plotter routine to draw instrument plots on the 160x80 LCD. ---------------------------------------- _________________________________________________________________ Windows Live™ SkyDrive™: Get 25 GB of free online storage. http://windowslive.com/online/skydrive?ocid=TXT_TAGLM_WL_SD_25GB_062009

SD

Samuel D. [x86/CPC]

Mon, Jul 6, 2009 5:07 PM

Damn, that's a big flaw.

The software I'm working on send three "++addr" commands per second.

Only 4 days @24h/day to reach the limit :-/

-----Message d'origine-----
De : time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] De la
part de Mark Sims
Envoyé : lundi 6 juillet 2009 18:54
À : time-nuts@febo.com
Objet : [time-nuts] Prologix GPIB-USB vs. GPIB-LAN vs. NI was: AW: Prologix
GPIB-USB vs. GPIB-LAN

The Prologix adapter has a ++addr command for changing the GPIB address.
You can select different instruments that way.

Unfortunately, the version I looked seems to have a potentially fatal flaw.
When you change the ++addr, the device writes the internal microprocessor
EEPROM. The EEPROM is speced a 1 million write cycles. If you changed
instruments at once a second, in under two weeks the chip could be toast.
My app could have worn out the chip in under a day...

All this assumes that Prologix did not implement some sort of elaborate wear
leveling scheme in their software, but I suspect not. They seem to have
intended one to set up the device to talk to one instrument then save that
configuration in the chip. Dynamically hammering the thing to death with
address changes was not the intention of the ++addr command.

I wound up implementing a GPIB controller (with Prologix emulator) with my
MegaDonkey touch screen LCD controller. It even included a HPGL/PCL plotter
routine to draw instrument plots on the 160x80 LCD.

Windows Live SkyDrive: Get 25 GB of free online storage.
http://windowslive.com/online/skydrive?ocid=TXT_TAGLM_WL_SD_25GB_062009

time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.

Damn, that's a big flaw. The software I'm working on send three "++addr" commands per second. Only 4 days @24h/day to reach the limit :-/ -----Message d'origine----- De : time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] De la part de Mark Sims Envoyé : lundi 6 juillet 2009 18:54 À : time-nuts@febo.com Objet : [time-nuts] Prologix GPIB-USB vs. GPIB-LAN vs. NI was: AW: Prologix GPIB-USB vs. GPIB-LAN The Prologix adapter has a ++addr command for changing the GPIB address. You can select different instruments that way. Unfortunately, the version I looked seems to have a potentially fatal flaw. When you change the ++addr, the device writes the internal microprocessor EEPROM. The EEPROM is speced a 1 million write cycles. If you changed instruments at once a second, in under two weeks the chip could be toast. My app could have worn out the chip in under a day... All this assumes that Prologix did not implement some sort of elaborate wear leveling scheme in their software, but I suspect not. They seem to have intended one to set up the device to talk to one instrument then save that configuration in the chip. Dynamically hammering the thing to death with address changes was not the intention of the ++addr command. I wound up implementing a GPIB controller (with Prologix emulator) with my MegaDonkey touch screen LCD controller. It even included a HPGL/PCL plotter routine to draw instrument plots on the 160x80 LCD. ---------------------------------------- _________________________________________________________________ Windows Live SkyDrive: Get 25 GB of free online storage. http://windowslive.com/online/skydrive?ocid=TXT_TAGLM_WL_SD_25GB_062009 _______________________________________________ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.

RD

Robert Darlington

Mon, Jul 6, 2009 5:16 PM

You can probably replace the EEPROM with an FRAM chip (or even a free
sample of an FRAM chip) to get around the wear issues. I haven't opened my
unit, but this is a serious issue as I'm gearing up to write software to
make a "poor man's" network analyzer using a frequency synthesizer and a
volt meter, switching between them pretty much as fast as possible. Maybe
I'll just use that NI card ;-)

-Bob

On Mon, Jul 6, 2009 at 11:07 AM, Samuel D. [x86/CPC] sam@canardpc.comwrote:

Damn, that's a big flaw.

The software I'm working on send three "++addr" commands per second.

Only 4 days @24h/day to reach the limit :-/

-----Message d'origine-----
De : time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] De la
part de Mark Sims
Envoyé : lundi 6 juillet 2009 18:54
À : time-nuts@febo.com
Objet : [time-nuts] Prologix GPIB-USB vs. GPIB-LAN vs. NI was: AW: Prologix
GPIB-USB vs. GPIB-LAN

The Prologix adapter has a ++addr command for changing the GPIB address.
You can select different instruments that way.

Unfortunately, the version I looked seems to have a potentially fatal flaw.
When you change the ++addr, the device writes the internal microprocessor
EEPROM. The EEPROM is speced a 1 million write cycles. If you changed
instruments at once a second, in under two weeks the chip could be toast.
My app could have worn out the chip in under a day...

All this assumes that Prologix did not implement some sort of elaborate
wear
leveling scheme in their software, but I suspect not. They seem to have
intended one to set up the device to talk to one instrument then save that
configuration in the chip. Dynamically hammering the thing to death with
address changes was not the intention of the ++addr command.

I wound up implementing a GPIB controller (with Prologix emulator) with my
MegaDonkey touch screen LCD controller. It even included a HPGL/PCL
plotter
routine to draw instrument plots on the 160x80 LCD.

Windows Live™ SkyDrive™: Get 25 GB of free online storage.
http://windowslive.com/online/skydrive?ocid=TXT_TAGLM_WL_SD_25GB_062009

time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.

You can *probably* replace the EEPROM with an FRAM chip (or even a free sample of an FRAM chip) to get around the wear issues. I haven't opened my unit, but this is a serious issue as I'm gearing up to write software to make a "poor man's" network analyzer using a frequency synthesizer and a volt meter, switching between them pretty much as fast as possible. Maybe I'll just use that NI card ;-) -Bob On Mon, Jul 6, 2009 at 11:07 AM, Samuel D. [x86/CPC] <sam@canardpc.com>wrote: > Damn, that's a big flaw. > > The software I'm working on send three "++addr" commands per second. > > Only 4 days @24h/day to reach the limit :-/ > > > -----Message d'origine----- > De : time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] De la > part de Mark Sims > Envoyé : lundi 6 juillet 2009 18:54 > À : time-nuts@febo.com > Objet : [time-nuts] Prologix GPIB-USB vs. GPIB-LAN vs. NI was: AW: Prologix > GPIB-USB vs. GPIB-LAN > > > The Prologix adapter has a ++addr command for changing the GPIB address. > You can select different instruments that way. > > Unfortunately, the version I looked seems to have a potentially fatal flaw. > When you change the ++addr, the device writes the internal microprocessor > EEPROM. The EEPROM is speced a 1 million write cycles. If you changed > instruments at once a second, in under two weeks the chip could be toast. > My app could have worn out the chip in under a day... > > All this assumes that Prologix did not implement some sort of elaborate > wear > leveling scheme in their software, but I suspect not. They seem to have > intended one to set up the device to talk to one instrument then save that > configuration in the chip. Dynamically hammering the thing to death with > address changes was not the intention of the ++addr command. > > I wound up implementing a GPIB controller (with Prologix emulator) with my > MegaDonkey touch screen LCD controller. It even included a HPGL/PCL > plotter > routine to draw instrument plots on the 160x80 LCD. > > ---------------------------------------- > > > > > > _________________________________________________________________ > Windows Live™ SkyDrive™: Get 25 GB of free online storage. > http://windowslive.com/online/skydrive?ocid=TXT_TAGLM_WL_SD_25GB_062009 > _______________________________________________ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. > > > _______________________________________________ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. >

DC

David C. Partridge

Mon, Jul 6, 2009 5:40 PM

I thought FRAM required a refresh cycle like DRAM - or did I get my brain
cells scrambled?

D.

-----Original Message-----
From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] On
Behalf Of Robert Darlington
Sent: 06 July 2009 18:17
To: Discussion of precise time and frequency measurement
Subject: Re: [time-nuts] Prologix GPIB-USB vs. GPIB-LAN vs. NI was:
AW:Prologix GPIB-USB vs. GPIB-LAN

You can probably replace the EEPROM with an FRAM chip ...

I thought FRAM required a refresh cycle like DRAM - or did I get my brain cells scrambled? D. -----Original Message----- From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] On Behalf Of Robert Darlington Sent: 06 July 2009 18:17 To: Discussion of precise time and frequency measurement Subject: Re: [time-nuts] Prologix GPIB-USB vs. GPIB-LAN vs. NI was: AW:Prologix GPIB-USB vs. GPIB-LAN You can *probably* replace the EEPROM with an FRAM chip ...

DL

Don Latham

Mon, Jul 6, 2009 6:28 PM

I have used an interface from Softmark. I don't know if multiple
interfaces can be applied, but they are USB. There's no local storage,
everything is in the host, and I have not timed the use. OTH, they can be
bought for about $40US on ebay or straight from the Aussies at softmark.
Comes with dll's and an app...
Don

Robert Darlington

You can probably replace the EEPROM with an FRAM chip (or even a free
sample of an FRAM chip) to get around the wear issues. I haven't opened
my
unit, but this is a serious issue as I'm gearing up to write software to
make a "poor man's" network analyzer using a frequency synthesizer and a
volt meter, switching between them pretty much as fast as possible. Maybe
I'll just use that NI card ;-)

-Bob

On Mon, Jul 6, 2009 at 11:07 AM, Samuel D. [x86/CPC]
sam@canardpc.comwrote:

Damn, that's a big flaw.

The software I'm working on send three "++addr" commands per second.

Only 4 days @24h/day to reach the limit :-/

-----Message d'origine-----
De : time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] De
la
part de Mark Sims
Envoyé : lundi 6 juillet 2009 18:54
À : time-nuts@febo.com
Objet : [time-nuts] Prologix GPIB-USB vs. GPIB-LAN vs. NI was: AW:
Prologix
GPIB-USB vs. GPIB-LAN

The Prologix adapter has a ++addr command for changing the GPIB address.
You can select different instruments that way.

Unfortunately, the version I looked seems to have a potentially fatal
flaw.
When you change the ++addr, the device writes the internal
microprocessor
EEPROM. The EEPROM is speced a 1 million write cycles. If you changed
instruments at once a second, in under two weeks the chip could be
toast.
My app could have worn out the chip in under a day...

All this assumes that Prologix did not implement some sort of elaborate
wear
leveling scheme in their software, but I suspect not. They seem to
have
intended one to set up the device to talk to one instrument then save
that
configuration in the chip. Dynamically hammering the thing to death
with
address changes was not the intention of the ++addr command.

I wound up implementing a GPIB controller (with Prologix emulator) with
my
MegaDonkey touch screen LCD controller. It even included a HPGL/PCL
plotter
routine to draw instrument plots on the 160x80 LCD.

Windows Live SkyDrive: Get 25 GB of free online storage.
http://windowslive.com/online/skydrive?ocid=TXT_TAGLM_WL_SD_25GB_062009

time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.

--
Dr. Don Latham AJ7LL
Six Mile Systems LLP
17850 Six Mile Road
POB 134
Huson, MT, 59846
VOX 406-626-4304
www.lightningforensics.com
www.sixmilesystems.com

I have used an interface from Softmark. I don't know if multiple interfaces can be applied, but they are USB. There's no local storage, everything is in the host, and I have not timed the use. OTH, they can be bought for about $40US on ebay or straight from the Aussies at softmark. Comes with dll's and an app... Don Robert Darlington > You can *probably* replace the EEPROM with an FRAM chip (or even a free > sample of an FRAM chip) to get around the wear issues. I haven't opened > my > unit, but this is a serious issue as I'm gearing up to write software to > make a "poor man's" network analyzer using a frequency synthesizer and a > volt meter, switching between them pretty much as fast as possible. Maybe > I'll just use that NI card ;-) > > -Bob > > On Mon, Jul 6, 2009 at 11:07 AM, Samuel D. [x86/CPC] > <sam@canardpc.com>wrote: > >> Damn, that's a big flaw. >> >> The software I'm working on send three "++addr" commands per second. >> >> Only 4 days @24h/day to reach the limit :-/ >> >> >> -----Message d'origine----- >> De : time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] De >> la >> part de Mark Sims >> Envoyé : lundi 6 juillet 2009 18:54 >> À : time-nuts@febo.com >> Objet : [time-nuts] Prologix GPIB-USB vs. GPIB-LAN vs. NI was: AW: >> Prologix >> GPIB-USB vs. GPIB-LAN >> >> >> The Prologix adapter has a ++addr command for changing the GPIB address. >> You can select different instruments that way. >> >> Unfortunately, the version I looked seems to have a potentially fatal >> flaw. >> When you change the ++addr, the device writes the internal >> microprocessor >> EEPROM. The EEPROM is speced a 1 million write cycles. If you changed >> instruments at once a second, in under two weeks the chip could be >> toast. >> My app could have worn out the chip in under a day... >> >> All this assumes that Prologix did not implement some sort of elaborate >> wear >> leveling scheme in their software, but I suspect not. They seem to >> have >> intended one to set up the device to talk to one instrument then save >> that >> configuration in the chip. Dynamically hammering the thing to death >> with >> address changes was not the intention of the ++addr command. >> >> I wound up implementing a GPIB controller (with Prologix emulator) with >> my >> MegaDonkey touch screen LCD controller. It even included a HPGL/PCL >> plotter >> routine to draw instrument plots on the 160x80 LCD. >> >> ---------------------------------------- >> >> >> >> >> >> _________________________________________________________________ >> Windows Live SkyDrive: Get 25 GB of free online storage. >> http://windowslive.com/online/skydrive?ocid=TXT_TAGLM_WL_SD_25GB_062009 >> _______________________________________________ >> time-nuts mailing list -- time-nuts@febo.com >> To unsubscribe, go to >> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts >> and follow the instructions there. >> >> >> _______________________________________________ >> time-nuts mailing list -- time-nuts@febo.com >> To unsubscribe, go to >> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts >> and follow the instructions there. >> > _______________________________________________ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. > -- Dr. Don Latham AJ7LL Six Mile Systems LLP 17850 Six Mile Road POB 134 Huson, MT, 59846 VOX 406-626-4304 www.lightningforensics.com www.sixmilesystems.com

RD

Robert Darlington

Mon, Jul 6, 2009 6:40 PM

The chips I used in the past didn't need to get refreshed and they were pin
compatible with an eeprom I was using in a PIC circuit with an i2c
interface. They were basically identical with the exception that they don't
wear out before the sun expands and swallows the earth, and they can be
clocked many times faster than the i2c and spi spec.

-Bob

On Mon, Jul 6, 2009 at 11:40 AM, David C. Partridge <
david.partridge@dsl.pipex.com> wrote:

I thought FRAM required a refresh cycle like DRAM - or did I get my brain
cells scrambled?

D.

-----Original Message-----
From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] On
Behalf Of Robert Darlington
Sent: 06 July 2009 18:17
To: Discussion of precise time and frequency measurement
Subject: Re: [time-nuts] Prologix GPIB-USB vs. GPIB-LAN vs. NI was:
AW:Prologix GPIB-USB vs. GPIB-LAN

You can probably replace the EEPROM with an FRAM chip ...

time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.

The chips I used in the past didn't need to get refreshed and they were pin compatible with an eeprom I was using in a PIC circuit with an i2c interface. They were basically identical with the exception that they don't wear out before the sun expands and swallows the earth, and they can be clocked many times faster than the i2c and spi spec. -Bob On Mon, Jul 6, 2009 at 11:40 AM, David C. Partridge < david.partridge@dsl.pipex.com> wrote: > I thought FRAM required a refresh cycle like DRAM - or did I get my brain > cells scrambled? > > D. > > -----Original Message----- > From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] On > Behalf Of Robert Darlington > Sent: 06 July 2009 18:17 > To: Discussion of precise time and frequency measurement > Subject: Re: [time-nuts] Prologix GPIB-USB vs. GPIB-LAN vs. NI was: > AW:Prologix GPIB-USB vs. GPIB-LAN > > You can *probably* replace the EEPROM with an FRAM chip ... > > > _______________________________________________ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. >

P

Prologix

Mon, Jul 6, 2009 6:53 PM

It is pretty straightforward to add a new command to turn on/off automatic
saving of configuration parameters in the next firmware update.
ETA is a week or two. Please email support@prologix.biz if you like to be
notified when the update is available.

Firmware updates may be downloaded from http://prologix.biz

Thanks for all the feedback!

Regards,
Abdul
Prologix

-----Original Message-----
From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] On
Behalf Of Samuel D. [x86/CPC]
Sent: Monday, July 06, 2009 10:08 AM
To: 'Discussion of precise time and frequency measurement'
Subject: Re: [time-nuts] Prologix GPIB-USB vs. GPIB-LAN vs. NI was:
AW:Prologix GPIB-USB vs. GPIB-LAN

Damn, that's a big flaw.

The software I'm working on send three "++addr" commands per second.

Only 4 days @24h/day to reach the limit :-/

-----Message d'origine-----
De : time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] De la
part de Mark Sims Envoyé : lundi 6 juillet 2009 18:54 À : time-nuts@febo.com
Objet : [time-nuts] Prologix GPIB-USB vs. GPIB-LAN vs. NI was: AW: Prologix
GPIB-USB vs. GPIB-LAN

The Prologix adapter has a ++addr command for changing the GPIB address.
You can select different instruments that way.

Unfortunately, the version I looked seems to have a potentially fatal flaw.
When you change the ++addr, the device writes the internal microprocessor
EEPROM. The EEPROM is speced a 1 million write cycles. If you changed
instruments at once a second, in under two weeks the chip could be toast.
My app could have worn out the chip in under a day...

All this assumes that Prologix did not implement some sort of elaborate wear
leveling scheme in their software, but I suspect not. They seem to have
intended one to set up the device to talk to one instrument then save that
configuration in the chip. Dynamically hammering the thing to death with
address changes was not the intention of the ++addr command.

I wound up implementing a GPIB controller (with Prologix emulator) with my
MegaDonkey touch screen LCD controller. It even included a HPGL/PCL plotter
routine to draw instrument plots on the 160x80 LCD.

Windows Live SkyDrive: Get 25 GB of free online storage.
http://windowslive.com/online/skydrive?ocid=TXT_TAGLM_WL_SD_25GB_062009

time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.

It is pretty straightforward to add a new command to turn on/off automatic saving of configuration parameters in the next firmware update. ETA is a week or two. Please email support@prologix.biz if you like to be notified when the update is available. Firmware updates may be downloaded from http://prologix.biz Thanks for all the feedback! Regards, Abdul Prologix -----Original Message----- From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] On Behalf Of Samuel D. [x86/CPC] Sent: Monday, July 06, 2009 10:08 AM To: 'Discussion of precise time and frequency measurement' Subject: Re: [time-nuts] Prologix GPIB-USB vs. GPIB-LAN vs. NI was: AW:Prologix GPIB-USB vs. GPIB-LAN Damn, that's a big flaw. The software I'm working on send three "++addr" commands per second. Only 4 days @24h/day to reach the limit :-/ -----Message d'origine----- De : time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] De la part de Mark Sims Envoyé : lundi 6 juillet 2009 18:54 À : time-nuts@febo.com Objet : [time-nuts] Prologix GPIB-USB vs. GPIB-LAN vs. NI was: AW: Prologix GPIB-USB vs. GPIB-LAN The Prologix adapter has a ++addr command for changing the GPIB address. You can select different instruments that way. Unfortunately, the version I looked seems to have a potentially fatal flaw. When you change the ++addr, the device writes the internal microprocessor EEPROM. The EEPROM is speced a 1 million write cycles. If you changed instruments at once a second, in under two weeks the chip could be toast. My app could have worn out the chip in under a day... All this assumes that Prologix did not implement some sort of elaborate wear leveling scheme in their software, but I suspect not. They seem to have intended one to set up the device to talk to one instrument then save that configuration in the chip. Dynamically hammering the thing to death with address changes was not the intention of the ++addr command. I wound up implementing a GPIB controller (with Prologix emulator) with my MegaDonkey touch screen LCD controller. It even included a HPGL/PCL plotter routine to draw instrument plots on the 160x80 LCD. ---------------------------------------- _________________________________________________________________ Windows Live SkyDrive: Get 25 GB of free online storage. http://windowslive.com/online/skydrive?ocid=TXT_TAGLM_WL_SD_25GB_062009 _______________________________________________ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. _______________________________________________ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.

DL

Don Latham

Mon, Jul 6, 2009 7:17 PM

Prologix: Just for ducks, if there is room, there <ought> to be a
GPIB-address-addressed-parameter storage for, say, 5-6 devices?
Don

Prologix

It is pretty straightforward to add a new command to turn on/off automatic
saving of configuration parameters in the next firmware update.
ETA is a week or two. Please email support@prologix.biz if you like to be
notified when the update is available.

Firmware updates may be downloaded from http://prologix.biz

Thanks for all the feedback!

Regards,
Abdul
Prologix

-----Original Message-----
From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] On
Behalf Of Samuel D. [x86/CPC]
Sent: Monday, July 06, 2009 10:08 AM
To: 'Discussion of precise time and frequency measurement'
Subject: Re: [time-nuts] Prologix GPIB-USB vs. GPIB-LAN vs. NI was:
AW:Prologix GPIB-USB vs. GPIB-LAN

Damn, that's a big flaw.

The software I'm working on send three "++addr" commands per second.

Only 4 days @24h/day to reach the limit :-/

-----Message d'origine-----
De : time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] De la
part de Mark Sims Envoyé : lundi 6 juillet 2009 18:54 À :
time-nuts@febo.com
Objet : [time-nuts] Prologix GPIB-USB vs. GPIB-LAN vs. NI was: AW:
Prologix
GPIB-USB vs. GPIB-LAN

The Prologix adapter has a ++addr command for changing the GPIB address.
You can select different instruments that way.

Unfortunately, the version I looked seems to have a potentially fatal
flaw.
When you change the ++addr, the device writes the internal microprocessor
EEPROM. The EEPROM is speced a 1 million write cycles. If you changed
instruments at once a second, in under two weeks the chip could be toast.
My app could have worn out the chip in under a day...

All this assumes that Prologix did not implement some sort of elaborate
wear
leveling scheme in their software, but I suspect not. They seem to have
intended one to set up the device to talk to one instrument then save that
configuration in the chip. Dynamically hammering the thing to death with
address changes was not the intention of the ++addr command.

I wound up implementing a GPIB controller (with Prologix emulator) with
my
MegaDonkey touch screen LCD controller. It even included a HPGL/PCL
plotter
routine to draw instrument plots on the 160x80 LCD.

Windows Live SkyDrive: Get 25 GB of free online storage.
http://windowslive.com/online/skydrive?ocid=TXT_TAGLM_WL_SD_25GB_062009

time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.

time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.

--
Dr. Don Latham AJ7LL
Six Mile Systems LLP
17850 Six Mile Road
POB 134
Huson, MT, 59846
VOX 406-626-4304
www.lightningforensics.com
www.sixmilesystems.com

Prologix: Just for ducks, if there is room, there <ought> to be a GPIB-address-addressed-parameter storage for, say, 5-6 devices? Don Prologix > > It is pretty straightforward to add a new command to turn on/off automatic > saving of configuration parameters in the next firmware update. > ETA is a week or two. Please email support@prologix.biz if you like to be > notified when the update is available. > > Firmware updates may be downloaded from http://prologix.biz > > Thanks for all the feedback! > > Regards, > Abdul > Prologix > > -----Original Message----- > From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] On > Behalf Of Samuel D. [x86/CPC] > Sent: Monday, July 06, 2009 10:08 AM > To: 'Discussion of precise time and frequency measurement' > Subject: Re: [time-nuts] Prologix GPIB-USB vs. GPIB-LAN vs. NI was: > AW:Prologix GPIB-USB vs. GPIB-LAN > > Damn, that's a big flaw. > > The software I'm working on send three "++addr" commands per second. > > Only 4 days @24h/day to reach the limit :-/ > > > -----Message d'origine----- > De : time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] De la > part de Mark Sims Envoyé : lundi 6 juillet 2009 18:54 À : > time-nuts@febo.com > Objet : [time-nuts] Prologix GPIB-USB vs. GPIB-LAN vs. NI was: AW: > Prologix > GPIB-USB vs. GPIB-LAN > > > The Prologix adapter has a ++addr command for changing the GPIB address. > You can select different instruments that way. > > Unfortunately, the version I looked seems to have a potentially fatal > flaw. > When you change the ++addr, the device writes the internal microprocessor > EEPROM. The EEPROM is speced a 1 million write cycles. If you changed > instruments at once a second, in under two weeks the chip could be toast. > My app could have worn out the chip in under a day... > > All this assumes that Prologix did not implement some sort of elaborate > wear > leveling scheme in their software, but I suspect not. They seem to have > intended one to set up the device to talk to one instrument then save that > configuration in the chip. Dynamically hammering the thing to death with > address changes was not the intention of the ++addr command. > > I wound up implementing a GPIB controller (with Prologix emulator) with > my > MegaDonkey touch screen LCD controller. It even included a HPGL/PCL > plotter > routine to draw instrument plots on the 160x80 LCD. > > ---------------------------------------- > > > > > > _________________________________________________________________ > Windows Live SkyDrive: Get 25 GB of free online storage. > http://windowslive.com/online/skydrive?ocid=TXT_TAGLM_WL_SD_25GB_062009 > _______________________________________________ > time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. > > > _______________________________________________ > time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. > > > _______________________________________________ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. > -- Dr. Don Latham AJ7LL Six Mile Systems LLP 17850 Six Mile Road POB 134 Huson, MT, 59846 VOX 406-626-4304 www.lightningforensics.com www.sixmilesystems.com

CH

Chuck Harris

Mon, Jul 6, 2009 8:35 PM

Hi Mark,

Mark Sims wrote:

The Prologix adapter has a ++addr command for changing the GPIB address. You can select different instruments that
way.

Unfortunately, the version I looked seems to have a potentially fatal flaw. When you change the ++addr, the device
writes the internal microprocessor EEPROM. The EEPROM is speced a 1 million write cycles. If you changed
instruments at once a second, in under two weeks the chip could be toast. My app could have worn out the chip in
under a day...

Hmmm? This is what Microchip says:

The data EEPROM is a high-endurance, byte
addressable array that has been optimized for the
storage of frequently changing information (eg.,
program variables or other data that are updated often).
When variables in one section change frequently, while
variables in another section do not change, it is possible
to exceed the total number of write cycles to the
EEPROM (Specification D124) without exceeding the
total number of write cycles to a single byte
(Specifications D120 and D120A). If this is the case,
then a refresh of the array must be performed. For this
reason, variables that change infrequently (such as
constants, IDs, calibration, etc.) should be stored in
Flash program memory.

It isn't that the EEPROM wears out, but more that it loses
the values in adjacent cells... unless you refresh them
before 1 million cycles occurs.

All that aside, it isn't clear to me that the ++addr even
writes to EEPROM.

In fact, in the section of my prologix manual where it discusses
the use of EEPROM, it specifically says that the EEPROM stores
configuration information, and that addr is not configuration
information, and must be set as needed.

-Chuck Harris

Hi Mark, Mark Sims wrote: > The Prologix adapter has a ++addr command for changing the GPIB address. You can select different instruments that > way. > > Unfortunately, the version I looked seems to have a potentially fatal flaw. When you change the ++addr, the device > writes the internal microprocessor EEPROM. The EEPROM is speced a 1 million write cycles. If you changed > instruments at once a second, in under two weeks the chip could be toast. My app could have worn out the chip in > under a day... Hmmm? This is what Microchip says: The data EEPROM is a high-endurance, byte addressable array that has been optimized for the storage of frequently changing information (eg., program variables or other data that are updated often). When variables in one section change frequently, while variables in another section do not change, it is possible to exceed the total number of write cycles to the EEPROM (Specification D124) without exceeding the total number of write cycles to a single byte (Specifications D120 and D120A). If this is the case, then a refresh of the array must be performed. For this reason, variables that change infrequently (such as constants, IDs, calibration, etc.) should be stored in Flash program memory. It isn't that the EEPROM wears out, but more that it loses the values in adjacent cells... unless you refresh them before 1 million cycles occurs. All that aside, it isn't clear to me that the ++addr even writes to EEPROM. In fact, in the section of my prologix manual where it discusses the use of EEPROM, it specifically says that the EEPROM stores configuration information, and that addr is not configuration information, and must be set as needed. -Chuck Harris

P

Prologix

Wed, Sep 16, 2009 1:35 AM

Closing the loop...

Latest firmware updates available at http://prologix.biz includes the
++savecfg command to temporarily disable automatic saving of configuration
parameters (including address).
Please see manual for details.

Regards,
Abdul

-----Message d'origine-----
De : time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] De la
part de Mark Sims
Envoyé : lundi 6 juillet 2009 18:54
À : time-nuts@febo.com
Objet : [time-nuts] Prologix GPIB-USB vs. GPIB-LAN vs. NI was: AW: Prologix
GPIB-USB vs. GPIB-LAN

The Prologix adapter has a ++addr command for changing the GPIB address.
You can select different instruments that way.

Unfortunately, the version I looked seems to have a potentially fatal flaw.
When you change the ++addr, the device writes the internal microprocessor
EEPROM. The EEPROM is speced a 1 million write cycles. If you changed
instruments at once a second, in under two weeks the chip could be toast.
My app could have worn out the chip in under a day...

All this assumes that Prologix did not implement some sort of elaborate wear
leveling scheme in their software, but I suspect not. They seem to have
intended one to set up the device to talk to one instrument then save that
configuration in the chip. Dynamically hammering the thing to death with
address changes was not the intention of the ++addr command.

Closing the loop... Latest firmware updates available at http://prologix.biz includes the ++savecfg command to temporarily disable automatic saving of configuration parameters (including address). Please see manual for details. Regards, Abdul -----Message d'origine----- De : time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] De la part de Mark Sims Envoyé : lundi 6 juillet 2009 18:54 À : time-nuts@febo.com Objet : [time-nuts] Prologix GPIB-USB vs. GPIB-LAN vs. NI was: AW: Prologix GPIB-USB vs. GPIB-LAN The Prologix adapter has a ++addr command for changing the GPIB address. You can select different instruments that way. Unfortunately, the version I looked seems to have a potentially fatal flaw. When you change the ++addr, the device writes the internal microprocessor EEPROM. The EEPROM is speced a 1 million write cycles. If you changed instruments at once a second, in under two weeks the chip could be toast. My app could have worn out the chip in under a day... All this assumes that Prologix did not implement some sort of elaborate wear leveling scheme in their software, but I suspect not. They seem to have intended one to set up the device to talk to one instrument then save that configuration in the chip. Dynamically hammering the thing to death with address changes was not the intention of the ++addr command.

time-nuts@lists.febo.com

Prologix GPIB-USB vs. GPIB-LAN vs. NI was: AW: Prologix GPIB-USB vs. GPIB-LAN