Home Page Forums MAME MAME NCR Decision Mate V (DMV)

The last changes allow another OS to run on the DMV - USCD p-System. That's four down, one to go (CP/M-68K)





Robert

I've worked on the DMV layout a bit ... there are now four options apart from "screen only":

• Default without backdrop
• Diagnostic module without backdrop
• Default with backdrop
• Diagnostic module with backdrop

Each view comes with drive LEDs (although I couldn't figure out how to "connect" them in the driver ... disk copying inside the driver works, so having the LEDs work would be nice), and the mainboard diagnostics LEDs.

The views that include the backdrop have a "lighted" power LED. In these views it would be great to be able to call up the file manager dialogue for the respective floppy disk drive by adding a hotspot to the drive knobs. I don't know if MESS supports switching between the host mouse and a guest mouse that might be emulated in the future.

The views for the diagnostic module include the 7 segment LED displays and the diagnostics LEDs on the module. Of these, the six LEDs monitoring the computer's voltage are fixed, the PCLK/, MEMR/ and HLDA LEDs could be hooked up.

https://dl.dropboxusercontent.com/u/55419307/NCR%20DMV/DMV%20Layout%20Artwork.rar

Holy blinkenlights! This is awesome!

Everything that works was put there by Micko in 2012 ... I just shuffled it around a bit

Way cool!

Want that for the Rainbow, too.

Do you have good images of monochrome or color monitors?

To light simple LEDs, you'll have to write something like that:

A bezel named "led1" must exist. See
<view name="Default Layout">
in RAINBOW.LAY

The state values can be taken from the top of the layout file:
I don't know yet how to drive 7 segment LEDs (hell, the documentation is really bad...)

Well, I've been looking through the DMV driver to find the appropriate signal to trigger the output to the drive LED, but couldn't make heads nor tails of it ... this'll have to wait for a dev.

As for pictures of the monitors, I can try to photograph them and then enhance the existing layout.

The drive led is usually configured by jumpers on the drive itself.
On the TEAC FD55GFR drive (which is just an example drive here) it can be one of 5 things (from FD55GFR-7xxx jumper listing):
1. Drive Select
2. Drive Select + In Use
3. In Use
4. Drive Select * Ready (ready is supplied by the drive itself)
5. In Use + (Drive Select * Ready)
(In Use is an optional use of the otherwise reserved mini-shugart pin 4; other drives may use it for other things)
(+ means OR, * means AND)
(The actual cable signals are all open collector active low, so consider them pre-inverted on the drive board to active high for simplicity here)

LN

Yeah, I'd know how to jumper a physical drive, but integrating the LED code into the driver is beyond my abilities.

Make that "strap" instead of "jumper" as this is a NCR related thread. That's the terminology they were using then

Actually it's pretty simple if you know where to get the value, src/mess/drivers/mk2.c has one I hooked up a while back:


So the first parameter to output_set_digit_value is which digit to change, and the second parameter is the value to set it to (m_led is set by a write handler elsewhere in this case). I think the value is a bit field of the segment values so if the system has some weird arrangement of bits you may need to use a BITSWAP macro but for mk2 it just worked.

Thanks ... the 7 segments are actually hooked up ... I have yet to cross check the the validity of the values they display.