esr5945@ritcv.UUCP (Eric Rose) (05/04/85)
*** REPLACE THIS LINE WITH YOUR MESSAGE *** Help Does anyone out there have any clues to the following problem we have been having trying to get our version of Caesar working? The senario: We have all the equipment the distribution list specifies: 1) VAX-11/780 2) AED-512 graphics terminal 3) Summugraphics bit-pad 4) all dip-switches set and double-checked! The symtoms: Ceasar works GREAT!.... but the bit pad does not work. We can't seem to get the cursor from the bit pad to come up on the screen of the AED. I have put an oscilliscope on the control lines to the bit pad, and it does seem to be talking to the AED, but it still does not work! The AED was tried on another system whose AED does work, but ours didn't. Possible cause: Our AED is a couple of years old, could it have an old prom set in it? This is the only thing we could think of, since it seems to be narrowed down to the AED it'self? Any thoughts or comments from anyone out there would be most appreciated! Eric Rose Rochester Institute of Technology ritcv!esr5945
ksbszabo@wateng.UUCP (Kevin Szabo) (05/07/85)
We had problems getting our bit-pad talking to the AED 512 too. I remember burning a day and half on it, and I believe the conclusion was that one of the settings in the CAESAR "README" file was incorrect. I believe the AED wants the data in ASCII format with <CR> *AND* <LF>. This is a single dip switch setting. (Berkeley runs with their own PROM set; it probably doesn't need the LF). Note that the AED can also screw up with modem control. We had RTS looped back to CTS which locked up the AED every so often. This was on the VAX <-> AED link. I don't think looping back the RTS-CTS was necessary for the tablet-aed link, but it didn't hurt. Good luck, send mail if you still have problems. Kevin -- Kevin Szabo watmath!wateng!ksbszabo (U of Waterloo VLSI Group, Waterloo Ont.)