Hey Paul,
sorry to confuse the issue. I don't think the FAS will enable or disable
options for you. It may however (I've never looked at the TDS540 FAS) declare
the memory location of the byte that holds the flag.
Sadly it appears that Tek is scrubbing their forum of the details, but
here's an EEVBlog thread <
(tds754d)/>
for how this might be done through the serial console. Here's <
>
a similar thread on EEVBlog for how to use GPIB.
It appears the addresses are the same whether you use GPIB or a console
serial port, but the "poke" command is different depending on the mode of
access. If you want to write to the NVRAM directly, presumably you need to
find it's base address in the processor's address space and subtract that
from the address.
As for how to come by these addresses, in e.g. the TDS784D FAS, I see
config files named by the scope types. In a file named TDS784D.CON,
containing lines such as "VAR = hwAOption1M(UNIT "" VALUE 327686)" which
relates the address of the 1M option flag (327686 decimal is 0x50006 hex). It's
possible that the options are always at the same address, scope model and
age be damned, but I don't know that. If your FAS declares this somewhere
for your scope's type, that'd be a good place to nab it.
Caveat: I've never done any of the above.
Siggi
On Mon, 28 Mar 2016 at 17:51 paul huguenin tigrol.lechat@...
[TekScopes] <TekScopes@...> wrote:
Hello,
Thanks Siggi, I must admit that was a little steep for a first experience
on a Tek DSO.
I have found the FAS for the TDS544A on KO4BB, run it on Windows 7 with
DOSbox emulator, from what I see it will only use two models of 8bit ISA NI
GPIB cards.
It seems a shame to find an old 90's card just for that purpose when I have
not yet invested in a recent GPIB interface.
There was nothing obvious in terms of software options in the config files,
it could be stored in main .EXE for this older version.
The most convenient for me would either be directly editing the NVRAM with
a programmer or using RS232 somehow. Shouldn't all that is done with GPIB
be possible with the serial console too?
The other problem is the calibration, DC balance seems to need adjusting,
the mean values measured by the scope change depending on horizontal range
and position (offset) on the screen, any way I can work around that without
the antique FAS and required hardware?
Paul
2016-03-27 1:27 GMT+01:00 Sigur?ur ?sgeirsson siggi@... [TekScopes] <
TekScopes@...>:
Hey Paul,
Congrats on the fix.
Do you have the field adjust software for your scopes? The FAS for my TDS
784D declares the addresses/locations for the software option flags in a
config file of some sort. There are threads on the Tek forum on how to
apply those with a serial console connection and GPIB (I forget the
details).
Siggi
On Sat, Mar 26, 2016 at 19:39 paul huguenin tigrol.lechat@...
[TekScopes] <TekScopes@...> wrote:
I realized there were too many conditions in the GPIB interface
question...
My problem on the TDS544A turned out to be a cut trace under VR1664.
Both TP1608 and TP1658 are now at -6.73V, still not the values on the
schematic, they are similar on both working scopes though.
I had dumped the NVRAM (Desoldered and socketed) on the 544A before
recaping, since I have read here that it is not uncommon that the
NVRAMs
die on desoldering, is it worth the risk dumping the TDS540 NVRAM too?
Now the scopes are working is there a simple way to enable options
software
options? (Still no GPIB)
Thanks,
Paul
2016-03-26 2:39 GMT+01:00 paul huguenin <tigrol.lechat@...>:
Hello,
Quick and late (here) update:
The TDS544A had been put aside a while, the TDS540 passed self tests
but
needed a recap for A11 and A12 boards, A10 had been taken care of by
someone before things turned bad.
Now I have a working scope to confront the failing TDS544A with.
The test point TP1608 is at -6.72V, TP1658 at -6.74V in the working
scope.
Just for future reference.
What would be a good choice/source for a budget USB GPIB interface?
Avoiding fakes.
Paul
2016-03-25 9:00 GMT+01:00 kennedy.simon@... [TekScopes] <
TekScopes@...>:
TL074/TL072 work fine. Glad the schematics have made it to KO4BB.
I'm not too sure what the voltages should be at those test points. I
would strongly suggest tying to find a GPIB adaptor somehow as it
makes
this debugging quite a lot easier. I had problems with the error log
getting too long to find the latest errors.
Even if the traces looks like they are connected make sure to check
them
with a multimeter for continuity.
Simon
[Non-text portions of this message have been removed]
------------------------------------
Posted by: kennedy.simon@...
------------------------------------
------------------------------------
Yahoo Groups Links
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
------------------------------------
Posted by: =?UTF-8?B?U2lndXLDsHVyIMOBc2dlaXJzc29u?= <siggi@...>
------------------------------------
------------------------------------
Yahoo Groups Links
[Non-text portions of this message have been removed]
