| Products > Test Equipment |
| Test Equipment Anonymous (TEA) group therapy thread |
| << < (24984/27437) > >> |
| mnementh:
--- Quote from: bd139 on July 02, 2022, 04:06:20 pm ---Cat purring annoys me like ticking clocks and loud fans do :popcorn: --- End quote --- mnem I prepared Explosive Runes today. >:D |
| m k:
--- Quote from: mnementh on July 02, 2022, 04:08:13 pm --- --- Quote from: factory on July 02, 2022, 02:05:50 pm --- --- Quote from: mnementh on July 02, 2022, 03:05:23 am ---Uggghhh... Okies... anybody got any tech ref on the monitors used in these HP scopes? I understand the difference between the two implementations is the 54621D and family use 32-grayscale palette, while the 54600A and family use a 2-grayscale palette. 54645A/54600A use HP 2090-0316/DataRay CDM-7SF191, the 54621D uses HP 2090-0384/DataRay CDM-7SX191. My searches in the available HP SMs and on the internet turned up bupkis. Before I go guessing based on poking around with my scope, does anybody here have actual pinouts and or schematic for these monitors? Tomorrow I figured I'd start looking at the CLIP package from the 54645A and see what I can find there. Maybe lookit the video chip on each and see if I can find some datasheets. :-// mnem :=\ --- End quote --- I'm would be surprized if they aren't interchangeable, they look to be standard bought-in monochrome monitors to me, the different greyscaling would be something done in the video processing, on the mainboard and the output just a video signal. Certainly I saw the video signal on the diagrams for the 54645A, that was posted a few weeks back. I think the other connections are power (+15V?), an external pot for brightness, can't remember what else there is. The chip on the Hitachi CDM-7SF191 board in my 54615B is a uPC1379C, this is a sync signal processor IC intended for small B/W & color TVs and does the vertical & horizontal stuff, that is done by more discrete parts on the earlier scope displays (the only one that a diagram seems available for).David --- End quote --- Yeeah, I'm not sure. IIRC, these are actually a TTL digital input monitor, so not that simple. I need to do some research. :-+ mnem :-/O --- End quote --- Neck board has an added 74S03, so maybe 16 new shades of gray. CNC industry have had small screens for quite some time. Possibly already have an almost ready replacement LCD. |
| bitseeker:
--- Quote from: mnementh on July 02, 2022, 03:14:13 pm ---When I need to, I know how to speak so sweetly that sugar wouldn't melt in my mouth. --- End quote --- Oh, my! :scared: ^-^ In other news, lots of new POI added to post #2 (the extension to the TE list in post #1). Does anyone actually use the POI lists to find stuff in this thread? ??? |
| mnementh:
mnem yes. at least one dwagon uses it. ;) |
| AVGresponding:
Well, as promised, here's a (brief) report on the Agilent DMM logger interface. Progress has been hampered by several factors, including abysmally poor user manuals from Keysight (I might yet start calling them Keyshite publicly, and not just in my head), a Cat phone that only talks to my PC when it feels like it, some trial and error Android emulators for PC (none worked), and a pause for multiple reboots while I removed the pile of steaming crap glacially slow bloatware that is NI Labview. Here's the wee gizmo, the U1177A: Yes, it's a Bluetooth module that attaches to the back of the U12xx series DMMs. And no, it isn't Fluke yellow, it's Agilent orange! Unexpectedly (not as described, should I file a claim..?) it also came with a usb adapter. Now, me being of a suspicious inquisitive turn of mind, I compared it to the usb adapter I'd recently purchased for the U1401B. Now obviously the housing and attachment are different, but the IR LED/phototransistor pair spacing is identical, so I decided to spudge the casings off. Well then... there we have it. No point to try using the usb lead, eh? I may yet pm Daniel about the data logger for the U1401B incompatibility with win 10, but I suspect he will be unable to help, materially. This does however pose another interesting possibility; if the BT module works, maybe it can be used with the U1401B with a 3DP adapter or something? Anyway, back to the primary. The module has a 3-position switch on the back, off-setup-on. Setup is used with Hyper Terminal on the PC, very useful (not) on win10... The manuals get the pairing procedure wrong, again trial and error comes into play. After some buggering about I can even get the Keysight connection expert to talk to the meter, though the only command that works is IDN, and it appears to be completely incompatible with BenchVue. Eventually I found the right software, and I can now connect the U1273A to either my phone or my PC: The apparent difference in readings on the PC is down to comms latency. So, being of an aforementioned mind, I tried the BT module with the U1401B, with some black heatshrink tubing to adapt the IR connectors, and after that, using the U1401B correct usb lead with the PC app. No dice as expected, but both the mobile and PC apps show they are trying to connect, and the "remote" annunciator activates on the meter. Obviously the two meters speak a different language. Does however kind of prove it's the Keysight software that's at fault though. Wow, this post took nearly two hours to write and rewrite! :-DD There's a lot of duff info out there, pretty much any official Agilent link is dead; would have been nice if they could have redirected them to the Keysight equivalents. Quite a few RS and Farnell etc docs have Agilent links in them. Apologies if you try to read this post while I'm editing the pic links in... |
| Navigation |
| Message Index |
| Next page |
| Previous page |