Home
Help
Search
Login
Register1
Beginners / Re: Calibration - How to Mathematically
« Last post by Picuino on Today at 07:52:45 am »It depends. What function do you want to approximate and with what accuracy?
Recent Posts
2
Projects, Designs, and Technical Stuff / How do hall effect switches not oscillate at the crossover point?
« Last post by e100 on Today at 07:42:01 am »I had run out of Allegro A3144 hall effect switches so I tried to make a similar thing using two 3503 linear hall sensors feeding into the differential AB inputs of a Max485 chip in receive mode.
I waved a magnet in front of one sensor and assumed that the 200mV hysteresis would give a clean signal, but instead I see a series of spurious pulses before it finally flips state.
Do real hall effect switches have the same problem internally, but just capture the first pulse and stretch it out to meet the fully flipped state?
The datasheet for the A3144 doesn't really explain what it does internally, other than showing a Schmitt trigger block.
I waved a magnet in front of one sensor and assumed that the 200mV hysteresis would give a clean signal, but instead I see a series of spurious pulses before it finally flips state.
Do real hall effect switches have the same problem internally, but just capture the first pulse and stretch it out to meet the fully flipped state?
The datasheet for the A3144 doesn't really explain what it does internally, other than showing a Schmitt trigger block.
3
Repair / Re: Tektronix DPO4054 stucked at tektronix splash screen
« Last post by ApertureScience on Today at 07:40:29 am »I now have error messages regarding DramDqPullUpStrength and DramDqPullDownStrength. Im considering putting the old ram chips back and maybe diong a complete reball of U370.
4
Test Equipment / Re: New Zoyi multimeter+oscilloscopes - ZT-70xS, up to 50MHz/250MSps (nov 2022)
« Last post by Razvan_N on Today at 07:39:43 am »Yes, it's safe for the PC and functional on the 703S, I flashed it yesterday.
5
Repair / Re: Tektronix DPO4054 stucked at tektronix splash screen
« Last post by ApertureScience on Today at 07:37:55 am »After a long break I reinvested some time in my broken scope and a new hot air station. I reflowed U370 and something changed.
Code: [Select]
U-Boot 1.1.4 (Jan 8 2007 - 11:12:14) Tektronix, Inc. V1.06
CPU: AMCC PowerPC 440EP Rev. B at 333.333 MHz (PLB=133, OPB=66, EBC=66 MHz)
I2C boot EEPROM enabled
Internal PCI arbiter enabled, PCI async ext clock used
32 kB I-Cache 32 kB D-Cache
Board: Tektronix Route66 IBM 440EP Main Board
VCO: 666 MHz
CPU: 333 MHz
PLB: 133 MHz
OPB: 66 MHz
EPB: 66 MHz
I2C: ready
DRAM: 128 MB
FLASH: 64.5 MB
PCI: Bus Dev VenId DevId Class Int
00 13 10b5 9056 0680 18
00 15 1002 4c59 0300 17
DISP: Type 1
In: serial
Out: serial
Err: serial
Enter password - autobooting in 3 seconds
## Booting image at f0000000 ...
Image Name: Linux-2.4.20_mvl31-440ep_eval
Image Type: PowerPC Linux Multi-File Image (gzip compressed)
Data Size: 1441010 Bytes = 1.4 MB
Load Address: 00000000
Entry Point: 00000000
Contents:
Image 0: 1033953 Bytes = 1009.7 kB
Image 1: 407042 Bytes = 397.5 kB
Verifying Checksum ... OK
Uncompressing Multi-File Image ... OK
cmdline is console=ttyS0,9600 quiet bigphysarea=519 panic=2 root=/dev/mtdblock7 rw mem=131072k
Loading Ramdisk to 07f2b000, end 07f8e602 ... OK
Checking for firmware update...
No USB mass storage devices found to update from.
Linux 2.4.20_mvl31-440ep_eval V 1.15 Tektronix Route66 Tue Jun 22 15:19:50 PDT 2010
stat of /var/log/dmesg failed: No such file or directory
Warning: loading NiDKEng-1.6 will taint the kernel: non-GPL license - Proprietary
See [url]http://www.tux.org/lkml/#export-tainted[/url] for information about tainted modules
Warning: loading NiDUsb-1.6 will taint the kernel: non-GPL license - Proprietary
See [url]http://www.tux.org/lkml/#export-tainted[/url] for information about tainted modules
Warning: loading tek will taint the kernel: non-GPL license - Proprietary
See [url]http://www.tux.org/lkml/#export-tainted[/url] for information about tainted moScope application starting (normal mode)
---------------------- startScopeApp() running Init code ----------------------
versionBuildFWVersionString(): TimestampString: 25-May-11 15:07
VersionFIRMWAREVERSIONversion: v2.58
Major ver num: 2 Minor ver num: 58
Initializing Mia[0]
Adg523 detected, patching reg offsets
Initializing Tek0005[0]
Initializing Ibm440[0]
Initializing HFD204ADC[1]
Initializing HFD204ADC[0]
Model id: 0x02
Initializing Ltc1658Dac[0]
Board id: 0x00
Initializing M859[3]
Initializing M859[2]
Initializing M859[1]
Initializing M859[0]
HFD144[0] ID_REG = 0x00001440
HFD144[1] ID_REG = 0x00001440
HFD144[2] ID_REG = 0x00001440
HFD144[3] ID_REG = 0x00001440
Initializing Hfd144[0]
Initializing Hfd144[1]
Initializing Hfd144[2]
Initializing Hfd144[3]
Open Max5362 successful.
Initializing Max5362[0]
Initializing Ltc1661Dac[1]
Initializing Ltc1661Dac[0]
Init ADT7468 and locking.
CANNOT SET FAN PARAMETERS - CONTROLLER LOCKED
Factory Checksum: Stored: 36701, Calculated: 36701 - OK
Spc CheckSum: stored: 24980 calculated: 24980 - OK
Demux initialization
Dram calibration
dmx 03 ERROR: 06_calDriveStrength: didn't find good value for DramDqPullUpStrength
ERROR: DramDqPullUp can not pull up.
Bit Fields A - H: (All bytes would be 0xff for a good cal.
0xff 0xff 0xf7 0xf7 0xff 0xff 0xff 0xff
dmx 03 ERROR: 06_calDriveStrength: didn't find good value for DramDqPullDownStrength
ERROR: DramDqPullDown can not pull down.
Bit Fields A - H: (All bytes would be 0xff for a good cal.
0x0 0x0 0x0 0x3 0x0 0x0 0x0 0x0
dmx 03: DramCal FAILED *****
Dram calibration complete
Dram Calibration results:
-------------------------
dmx 02: PASSED
dmx 03: FAILED *****
ERROR: 06_calDriveStrength: didn't find good value for DramDqPullUpStrength
Demux initialization complete
Starting POST diags
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002
Failure at address 0x0
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002
Failure at address 0x10
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002
Failure at address 0x20
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002
Failure at address 0x30
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002
Failure at address 0x40
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002
Failure at address 0x50
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002
Failure at address 0x60
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002
Failure at address 0x70
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002
Failure at address 0x80
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002
Failure at address 0x90
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002
Failure at address 0xa0
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000001 0x00000001
Diag Failure: Mode 100 4, U370,U480,U0471,U470,U0462, 0x00000000 0x00000002 0x00000002
Failure at address 0xb0
Failure at address 0xc0
Failure at address 0xd0
Failure at address 0xe0
Failure at address 0xf0
dmx 03 ERROR: 06_calDriveStrength: didn't find good value for DramDqPullUpStrength
ERROR: DramDqPullUp can not pull up.
Bit Fields A - H: (All bytes would be 0xff for a good cal.
0xff 0xff 0xf7 0xf7 0xff 0xff 0xff 0xff
dmx 03 ERROR: 06_calDriveStrength: didn't find good value for DramDqPullDownStrength
ERROR: DramDqPullDown can not pull down.
Bit Fields A - H: (All bytes would be 0xff for a good cal.
0x0 0x0 0x0 0x3 0x0 0x0 0x0 0x0
dmx 03: DramCal FAILED *****
Diag Failure: Mode 100 7, U370,U270, 0x0000ffff 0xffffffff 0xffff0000
Diag Failure: Mode 100 7, U370,U270, 0x00000000 0x0000ffff 0x0000ffff
Diag Failure: Mode 100 7, U370,U270, 0x0000fefe 0xfefeffff 0xfefe0101
Diag Failure: Mode 100 7, U370,U270, 0x00000101 0x0101ffff 0x0101fefe
Diag Failure: Mode 100 7, U370,U270, 0x0000fdfd 0xfdfdffff 0xfdfd0202
Diag Failure: Mode 100 7, U370,U270, 0x00000202 0x0202ffff 0x0202fdfd
Diag Failure: Mode 100 7, U370,U270, 0x0000fbfb 0xfbfbffff 0xfbfb0404
Diag Failure: Mode 100 7, U370,U270, 0x00000404 0x0404ffff 0x0404fbfb
Diag Failure: Mode 100 7, U370,U270, 0x0000f7f7 0xf7f7ffff 0xf7f70808
Diag Failure: Mode 100 7, U370,U270, 0x00000808 0x0808ffff 0x0808f7f7
Diag Failure: Mode 100 7, U370,U270, 0x0000efef 0xefefffff 0xefef1010
Diag Failure: Mode 100 7, U370,U270, 0x00001010 0x1010ffff 0x1010efef
Diag Failure: Mode 100 7, U370,U270, 0x0000dfdf 0xdfdfffff 0xdfdf2020
Diag Failure: Mode 100 7, U370,U270, 0x00002020 0x2020ffff 0x2020dfdf
Diag Failure: Mode 100 7, U370,U270, 0x0000bfbf 0xbfbfffff 0xbfbf4040
Diag Failure: Mode 100 7, U370,U270, 0x00004040 0x4040ffff 0x4040bfbf
Diag Failure: Mode 100 7, U370,U270, 0x00007f7f 0x7f7fffff 0x7f7f8080
Diag Failure: Mode 100 7, U370,U270, 0x00008080 0x8080ffff 0x80807f7f
Diag Failure: Mode 100 7, U370,U270, 0x0000ffff 0xffffffff 0xffff0000
Diag Failure: Mode 100 7, U370,U270, 0x00000000 0x0000ffff 0x0000ffff
Diag Failure: Mode 100 7, U370,U270, 0x0000ffff 0xffffffff 0xffff0000
Diag Failure: Mode 100 7, U370,U270, 0x00000000 0x0000ffff 0x0000ffff
Diag Failure: Mode 100 7, U370,U270, 0x0000ffff 0xffffffff 0xffff0000
Diag Failure: Mode 100 7, U370,U270, 0x00000000 0x0000ffff 0x0000ffff
Diag Failure: Mode 100 7, U370,U270, 0x0000ffff 0xffffffff 0xffff0000
Diag Failure: Mode 100 7, U370,U270, 0x00000000 0x0000ffff 0x0000ffff
Diag Failure: Mode 100 7, U370,U270, 0x0000ffff 0xffffffff 0xffff0000
Diag Failure: Mode 100 7, U370,U270, 0x00000000 0x0000ffff 0x0000ffff
Diag Failure: Mode 100 7, U370,U270, 0x0000ffff 0xffffffff 0xffff0000
Diag Failure: Mode 100 7, U370,U270, 0x00000000 0x0000ffff 0x0000ffff
Diag Failure: Mode 100 7, U370,U270, 0x0000ffff 0xffffffff 0xffff0000
Diag Failure: Mode 100 7, U370,U270, 0x00000000 0x0000ffff 0x0000ffff
Diag Failure: Mode 100 8, U271, calloc failed, 0
Diag Failure: Mode 100 8, U271, calloc failed, 0
Finished POST diags
Class 2 Level 2 acq error from sysTaskCreate in acqInit 0
01:11:45 Fri Apr 26 2024 (thread: tUsrRoot)
Class 2 Acquire Id 99 Instance 0 Severity 2 01:11:45 Fri Apr 26 2024 (thread: tUsrRoot) file errPublic.c line 663 (null)
errAddErrorLogDataEntry: sysAppState != SYS_STATE_ACTIVE
Class 2 Acquire Id 4 Instance 0 Severity 1 01:11:45 Fri Apr 26 2024 (thread: tUsrRoot) file acqPublic.c line 483 (null)
errAddErrorLogDataEntry: sysAppState != SYS_STATE_ACTIVE
All tasks suspended by errLogDataMsg call from tUsrRoot
errSuspendAll called from tUsrRoot
Backtrace: (depth of 6 shown)
/usr/local/bin/scopeApp.ppcep(errSuspendAll+0x6c)[0x10c40f74]
/usr/local/bin/scopeApp.ppcep(errLogDataMsg+0x3d0)[0x10c3f8c4]
/usr/local/bin/scopeApp.ppcep(errLogMsg+0x5c)[0x10c3f944]
/usr/local/bin/scopeApp.ppcep(_Z8acqErroriiiiPci+0xbc)[0x1039c790]
/usr/local/bin/scopeApp.ppcep(_Z7acqInitv+0x3b0)[0x1039ba24]
/usr/local/bin/scopeApp.ppcep[0x10c52628]
Class 22 System Id 0 Instance 22 Severity 2 01:11:45 Fri Apr 26 2024 (thread: tUsrRoot) file sysError.c line 191 (null)
cmdParmGetIntMsgPoll() error processing cmd for parm 151, clientId: 0, retCode: -1
System status:
SheetMemSize=0, TotalNumSheets=0, bus state=-1, xop state=0
MeasAbort=0, MathAbort=0
CurrentTransactionState=-1, CurrentTransactionParm=Invalid parm id
CurrentTransactionType=-1, arg1Type=0, arg2Type=0
Sys tasks and their state:
Name TaskId Pri Pipe Msgs/Max Handler
---- ------ --- ---- -------- -------
ext 0 n/a n/a
errSuspendAllThread(): could not suspend fpIntTask, retCode = -1
errSuspendAllThread(): could not suspend fpUnloadCmdQueueThread, retCode = -1
errSuspendAllThread(): could not suspend fpIrqMonitor, retCode = -1
errSuspendAllThread(): could not suspend usbHotplug, retCode = -1
errSuspendAllThread(): could not suspend UsbOutputMgr, retCode = -1
errSuspendAllThread(): could not suspend piUsb, retCode = -1
errSuspendAllThread(): could not suspend piVGpib, retCode = -1
errSuspendAllThread(): could not suspend probesSharedUnloadCmdQueueThread, retCode = -1
errSuspendAllThread(): could not suspend autoset, retCode = -1
errSuspendAllThread(): could not suspend cal, retCode = -1
errSuspendAllThread(): could not suspend diag, retCode = -1
errSuspendAllThread(): could not suspend fp, retCode = -1
errSuspendAllThread(): could not suspend hc, retCode = -1
errSuspendAllThread(): could not suspend UsbSicInputMsgMgr, retCode = -1
errSuspendAllThread(): could not suspend wfmMgrTest, retCode = -1
errSuspendAllThread(): could not suspend search, retCode = -1
errSuspendAllThread(): could not suspend periodicZoom, retCode = -1
errSuspendAllThread(): could not suspend periodicClockAnimation, retCode = -1
errSuspendAllThread(): could not suspend periodicBusyIndicAnimation, retCode = -1
errSuspendAllThread(): could not suspend math, retCode = -1
errSuspendAllThread(): could not suspend meas, retCode = -1
errSuspendAllThread(): could not suspend measImmed, retCode = -1
errSuspendAllThread(): could not suspend piCmdIntfc, retCode = -1
errSuspendAllThread(): could not suspend ref, retCode = -1
errSuspendAllThread(): could not suspend rtl, retCode = -1
errSuspendAllThread(): could not suspend tHttpd, retCode = -1
errSuspendAllThread(): could not suspend tVxi11SRQd, retCode = -1
errSuspendAllThread(): could not suspend tVxi11Rpcd, retCode = -1
errSuspendAllThread(): could not suspend bus, retCode = -1
errSuspendAllThread(): could not suspend mitlRb, retCode = -1
errSuspendAllThread(): could not suspend VgpibRead, retCode = -1
errSuspendAllThread(): could not suspend VgpibWrite, retCode = -1
errSuspendAllThread(): could not suspend tSocketServerService, retCode = -1
errSuspendAllThread(): could not suspend tSocketResponseThread, retCode = -1
errSuspendAllThread(): could not suspend UsbTmcEventDispatcher, retCode = -1
errSuspendAllThread(): could not suspend inputOverload, retCode = -1
errSuspendAllThread(): all threads in list suspended
errSuspendAll(): TASK tUsrRoot SHOULD NOT BE HERE!!!
6
FPGA / Re: USB BLASTER (FTDI245 vs ch552x) Quartus “No Hardware”
« Last post by noQuitter on Today at 07:35:44 am »@coromonadalix
the device manger does recognize the "vid/pid" pair, here is the hardware id that the device manger shows:
USB\VID_09FB&PID_6001&REV_0400
USB\VID_09FB&PID_6001
the device manger does recognize the "vid/pid" pair, here is the hardware id that the device manger shows:
USB\VID_09FB&PID_6001&REV_0400
USB\VID_09FB&PID_6001
7
Projects, Designs, and Technical Stuff / Re: (Yet Another) DIY Multislope ADC
« Last post by iMo on Today at 07:34:36 am »Yep, I've made an excel sheet to see the stuff in more detail, based on the paper linked in this thread, so I may play with the values (version 0).
The runup phase could have, say, X mV (or less) resolution, the rundown (in this design), say XX uVolts.
Then the auxADC on top of it - I have no math yet how to incorporate it into the end result, so as you indicate it would be matter of a calibration.. Still thinking how to formalize the rundown uncertainty and auxADC such it fits together smoothly..
The runup phase could have, say, X mV (or less) resolution, the rundown (in this design), say XX uVolts.
Then the auxADC on top of it - I have no math yet how to incorporate it into the end result, so as you indicate it would be matter of a calibration.. Still thinking how to formalize the rundown uncertainty and auxADC such it fits together smoothly..
8
Test Equipment / Re: Choosing between entry-level 12-bit DSOs
« Last post by Fungus on Today at 07:30:42 am »1) to be precise, anything more or equal to Sample rate / 2 will not be reconstructed correctly, i havent found literature saying exactly 2.5
Anything equal to sample rate/2 can NOT be reconstructed.
Think: You might sample on the zero crossing points.
Now work from there to something a tiny bit below that ... you'll go between zero crossings and peaks over time, and get an AM effect as seen in that video.
2.5 isn't a mathematically derived number, it's what works in practice.
9
FPGA / Re: USB BLASTER (FTDI245 vs ch552x) Quartus “No Hardware”
« Last post by noQuitter on Today at 07:28:47 am »@radiolistener, @coromonadalix, @Wiljan , @Mark
Thank you all for your comments. I'll try some of these tips and share my findings.
Thank you all for your comments. I'll try some of these tips and share my findings.
10
Beginners / Re: The old "Replace blue LEDs with red LEDs" 7 segment question (74HC595)
« Last post by trondl on Today at 07:21:18 am »Thanks for all the input!
So, there are 7 * 8 = 56 220ohm SMD resistors.
Changing them is doable, but time consuming.
After some more research, the LED package is a 10-DIP, so it narrows the options down to basically the same LTS series because they are positioned very close to each other (no space at all horizontally?), and pinouts are apparently not standardized in any way.
My theory about the dim LEDs is the fact that the only version in the LTS series being obsolete is the blue one and the others are still somewhat active.
Seems to me it was a too early adoption of blue situation.
If the red version is considered "safe" in the current configuration with 220ohm resistors, but the 595 may kneel, the 595 could be replaced with a stronger version that I recently heard about?
But I do then risk having too much current available?
Maybe changing the resistors to 380-470 is worth it after all.
Although it is dimmable, I'd rather be on the slightly dim than too bright side by default.
So, there are 7 * 8 = 56 220ohm SMD resistors.
Changing them is doable, but time consuming.
After some more research, the LED package is a 10-DIP, so it narrows the options down to basically the same LTS series because they are positioned very close to each other (no space at all horizontally?), and pinouts are apparently not standardized in any way.
My theory about the dim LEDs is the fact that the only version in the LTS series being obsolete is the blue one and the others are still somewhat active.
Seems to me it was a too early adoption of blue situation.
If the red version is considered "safe" in the current configuration with 220ohm resistors, but the 595 may kneel, the 595 could be replaced with a stronger version that I recently heard about?
But I do then risk having too much current available?
Maybe changing the resistors to 380-470 is worth it after all.
Although it is dimmable, I'd rather be on the slightly dim than too bright side by default.