> In addition, while I could easily afford a modern printer to transplant
> into the 4631 case, why should I when I have a perfectly good printer
> already, plugged into my PC?
> I'd prefer to take the raster image and save it in a suitable file
> format (TIFF?) for putting on a PC and printing on any old printer.
> This would make it much more flexible, and I think it would be of
> benefit to do so.
If a graphics file is the end format, it seems to me the easy way out
Is to use a modern PC running Tek 4010/4014 emulation software (anything
>From MS-Kermit to xterm) sniffing the serial traffic and just do
screen dumps from there.
For the vector purists (e.g. me) making SVG or Postscript or PDF or some
True vector format, would be a desirable goal. But with endpoint resolution
Only 1024x768 probably overkill. I still hate seeing what I know are
True vector lines, get rasterized.
Tim.
> It could be the chip, certainly, I doubt it's the windings. IIRC the
> widings are connected in a 'star' ('Wye') configuration to the 3 outputs,
> see the HP drive schemcatics I pointed you to for details. If I cam
> right, you could check the resistance between the 3 motor driver ouptus
> (6,7,9) with the drive power remoced, they should all appaer to be
> shorted to each other.
Tony I've looked through past emails and can't seem to find those schematics. Can you point me to them again?
The motor driver output pins are not QUITE shorted. There is about 25 ohms resistance showing which flickers between 20 and 30 as I turn the wheel? Normal?
> However, it's also ppossibloe that one of the hall sensors has failed.
> Theseare little 4 terminal parts that detelct the position of the motor
> and cause the chip to drive the rigth coils. IIRC, they are connected to
> pins 15,16,1,2,3,4[1] of the chip. With the motor supposed to be stopped,
> connect a voltbeeter between grounf and each of those pins (if I have
> rememebred them right, checkl the data sheet) in turn and slowly turn the
> spidnle. You should see a samll change in voltage for each pin, it shoud
> 'flick' up and down as you turn the spindle. If one or two are not doing
> this, suspect the hall device.
I've found them. On this TA7259P they are pins 1-4 and 13, 14. The voltages do show a variation as the spindle turns. But it's very small. About 0.03 volts and that variation is consistant over all 6 of them. The voltages differ. Pins 1 and 2 are 6.5, pins 3 and 4 are 4.3 and pins 13 and 14 are 8.4v
> [1] Be careful with the pin mubmbering if you are working from one of my
> HP drive scheramtics. I said the chip has 14 pins and 2 tabs. Toshiba say
> th chip has 16 pins, including the tabs. So the pin numbers are
> different.
The chip I have has 14 pins.
> I notce that one of the screews was badly corroded. Is there any damage
> to the PCB tracks in that area? An open connection could account for your
> problems.
>
The screw is rusty but the PCB tracks are actually in very good condition. There are no shorts.
> One question for you. Where does the white wire from thr motor connector
> go? Is it soldered to some point o nthe bototm of the PCB, if so, where?
No not soldered to the board. The white wire joins the other wires from the two motor board connectors and goes into an 8-pin socket which plugs into the top of the bottom circuit board. The pins for this can be seen standing upright on the mid-bottom left on the board:
http://www.classic-computers.org.nz/temp/lisa2-10-bottom-of-drive-circuit-b…
The white wire goes to pin 8 which is the pin nearest the bottom (i.e south) of the picture.
Well, what do you think Tony? I've found a place in HongKong I can get these TA 7259P ICs for $20 (incl shipping). The IC or the hall sensors? Are there any other tests I can do?
I appreciate the detailed help you're giving me here.
Terry
DEC AlphaServer 1000A?pedestal server, in good shape, working state unknown,
but likely does.? Alpha VMS or Tru64 UNIX CD's with apps likely available as well.
Let me know asap if anyone is interested.? Ths is being cleared out of an old DEC
logistics site early this week.
?
Dale
____________________________________________________________________________________
Don't pick lemons.
See all the new 2007 cars at Yahoo! Autos.
http://autos.yahoo.com/new_cars.html
This is aimed at all the folks who bought a DiscFerret with 001B
firmware... and has been cross-posted to classiccmp because I know there
are a few DiscFerret owners who don't follow the official mailing list.
There's a fairly nasty bug in the USB stack on firmware version 001B.
This bug causes the DiscFerret to stop responding under some conditions:
- When the power cable is plugged in before the USB cable.
- When the USB cable is unplugged, then reconnected while the
DiscFerret is powered up. ("hot plugging")
Basically, there's a logic error in the Microchip USB stack which causes
it to enter an infinite loop whenever the PIC boots without the USB
cable connected, or when the USB cable is disconnected mid-way through a
USB packet.
In the latter case, the USB PHY/SIE module in the PIC gets out of sync
with the host, and fails to re-synchronise when the host is reconnected.
The solution is to upgrade to Firmware 001C. This is available from
<http://www.discferret.com/downloads/>.
In simple terms:
- Short the BOOT jumper on the DiscFerret
- Connect the power supply and USB cable (in any order)
- Remove the jumper
- Run mphidflash to reprogram the PIC (the exact command line to use
is on the Downloads page).
The whole procedure can be done in a few minutes. If you've ever
reflashed a PC BIOS, you'll have no trouble upgrading the firmware on a
DiscFerret.
Any problems -- feel free to email me, or post on Discferret-L.
Thanks,
--
Phil.
classiccmp at philpem.me.uk
http://www.philpem.me.uk/
Hi guys,
I've just spent an hour or so fixing more bugs in the DiscFerret
microcode. Turns out the hard-sector track mark detector I was so
pleased with... didn't actually work. What's that old saying about pride
coming right before a fall?
Anyway -- it's fixed now, along with a few other bugs. Basically, I
screwed up the logic which generates the 250us and 500us master clocks,
meaning the step rates were about 2x too fast. I'm surprised my drives
managed to keep up at the rate the DiscFerret was stepping them (1.5ms a
step for the 3.5in drive!)
I've done some tests with a 10-sector NorthStar disc, and managed to get
a valid read. Next up is adding NorthStar support to the disc analyser,
but that's going to have to wait until next weekend...
There's also a new feature in Mcode 001F -- index speed measurement.
This is essentially a frequency counter tied to the INDEX pin. With
this, you can measure the rotational speed of the disc -- which could be
useful for testing disc drives, and adjusting the rotational speed of
the spindle motor (on drives which have such adjustments).
The new registers have been added to the current 'TIP' version of the C
API, and the Python API (which still lives in the firmware repository,
under the 'test' directory).
As always, if you have any questions, ask away -- either on Classiccmp
(cctalk or cctech), discferret-l, or the Vintage Computer Forums (though
you may well have to PM me to get my attention!)
Thanks,
--
Phil.
classiccmp at philpem.me.uk
http://www.philpem.me.uk/
Hi! Professor Wilcox is selling his historical S-100 68000 CPU board and
associated material. Please contact him if interested. This is a unique
set of boards and material. If I had the funds I would purchase these
myself but cannot so hopefully someone in the classic/vintage/homebrew
computer community would like these unique historical artifacts.
Thanks and have a nice day!
Andrew Lynch
-----Original Message-----
From: Alan D. Wilcox [mailto:alan at wilcoxengineering.com]
Sent: Wednesday, February 09, 2011 7:28 PM
To: Andrew Lynch
Subject: Re: Andrew - trying to reach you - ADVTG
Hi Andrew,
You're a lot more familiar than I am as to what might appeal. Perhaps if
you could please place a couple postings that might read something like
the following, I might find a happy home for it all.
"Unique 68000 S-100 CPU board and assorted other boards and engineering
notes for sale. The board is the design feature of my 68000 book
published in 1987. Photos and details at
http://wilcoxengineering.com/68000-microprocessor - I can provide more
specifics for serious inquiries only. Will not split; this special
historical collection stays together. Contact me through the site. Alan
Wilcox, W3DVX."
Send me links of where I can see whatever you put up. Hopefully we'll
have some serious folks calling.
Many thanks!
Alan :)
Alan D. Wilcox, W3DVX
570-321-1516
http://WilcoxEngineering.comhttp://www.eham.net/reviews/detail/6768 ... Elecraft Client Comments
http://www.eham.net/reviews/detail/8841 . Small Wonder Labs Comments
http://eBookEditor.nethttps://www.smashwords.com/books/view/28062?ref=awilcox
Williamsport, PA 17701
All --
I?m working on making a version of TinyBASIC available on the N8VEM
80188 board (like IBM ROM BASIC) and I?m looking for generic code to read
and write Intel Hex records. The plan is to use this for the file format for
storing BASIC programs on cassette. I?ve done some Googling and most of what
I find is complete conversion programs rather than the code fragments that I
need.
If anyone has any useful links on this topic I?d appreciate it. Thanks!
Rich
--
Rich Cini
Collector of Classic Computers
Build Master and lead engineer, Altair32 Emulator
http://www.altair32.comhttp://www.classiccmp.org/cini
Tony Duell wrote:
>>
>> That makes no sense.
>> sniping does not drive up prices like early bidding does.
>>
> Of coursei it does. If I (early bid) $50 for an item with an opening bid
> of $5, say, and somebody snipes me at the last minute with a $20 bid,
> then the price I have to pay has been driven up.
I think that's a bit contrived Tony - after all _any_ later bid would drive
up the price you have to pay, this isn't a function of sniping.
Bob
