I wrote the software drivers for the old DigiCHANNEL Nu/Xi 8-port serial card for the Macintosh and the firmware for some of the concentrators from the early 1990s, and, although there doesn’t seem to be a link from the current “support” page, Digi’s legacy product drivers are still online via FTP:
ftp://ftp.digi.com/support/legacy/digi/index.html
Even my drivers for the Mac Nu/Xi serial card are there. People looking for obsolete software should check it out…
Thanks Brian 
Thanks a lot man !
I can’t get into that link with the ftp:// header, but I got in using this address:
http://ftp.digi.com/support/legacy/digi/drivers/
I got what I needed for my MCA DigiChannel MC/8i too.
Thanks again!
Casolai
A (very) late note from Brian Westley (westley@visi.com)
on the DigiCHANNEL Nu/Xi and Mac OS 9.x
Apparently, some changes between OS8 and OS9 broke the
configuration setup; the driver itself still seems to
work fine, though (tested under OS9.1)
The startup icon isn’t drawn correctly, and under OS9.2
the file icons for the extension (the driver itself) and
the control panel Digiconfig are “generic”. These are
just cosmetic bugs.
The most important problem is that the driver can no longer
see the configuration made by the control panel, so the
driver is always using its default values; the control panel
no longer creates a “DigiCHANNEL Config” file in the
Preferences folder, and when run, it reads garbage and
appears to write over its own copy of the default
configuration instead of creating the config file.
So, to configure your driver to be something other than
default, you need to edit the DigiCHANNEL extension with
ResEdit, Apple’s resource editor. The resources are
‘opts’ and ‘STR’ and ‘slt1’. The TMPL resource has
templates for the ‘opts’ and ‘slt1’ resource, so you
can edit it easily with ResEdit and the fields are
fairly self-explanatory. ‘opts’ ID #0 is the default
for all channels, while ID #102 would be just the
configuration for the serial device at slot 1 port 2, etc,
in case you want to configure each port differently.
STR #102 would be the Comm. toolbox name for the port.
The digichannel.h file in the Programming folder
explains the ‘opts’ fields in more detail:
'STR ’ #9999 - Sys 7 configuration file name
'STR ’ #9998 - Sys 6.0.x configuration file name
'STR ’ #9997 - “In” suffix, to make .AIn/.AOut pairs
'STR ’ #9996 - “Out” suffix for above
‘STR ’ #9995 - Default Communications’ Toolbox name
'STR ’ #9994 - Default DRVR name. Special characters are:
0xFF = “In” or “Out” suffix
0xFE = Slot number
0xFD = Port number
0x00 = Next letter in A
Z
0x01
0x1A = Letter A
Z (^A
^Z)
'STR ’ #9993 - Max Comm Toolbox name template
'STR ’ #(slot100+port) - Specific CTB name for a serial line
e.g. ('STR ’ #201 is slot 2, port 1)
'STR ’ #-(slot100+port) - Specific DRVR name for a serial line
‘slt1’ #-1 - NuBus slot to call “Slot 1”.
If = 1, NuBus slot numbering.
‘opts’ #0 - Default option settings
‘opts’ #(slot*100+port) - Specific option settings for a serial line
‘opts’ fields in use are:
Default buffer size - Max 4096
Minimum buffer size - buffers smaller than this size, use this size. Max 4096
Maximum buffer size - buffers larger than this size, use this size.
Fix baud at: if not -1, baud rate is fixed at this value, no matter what.
External CLK: baud rate that is mapped to External Clock mode (ports 1 & 2 only)
76.8 Kbaud: baud rate that is mapped to 76800 baud
115.2 Kbaud: baud rate that is mapped to 115200 baud
Low water %: low watermark to turn input back on
High water %: high watermark to turn input off
XON: if nonzero, XON character (overrides all others)
XOFF: if nonzero, XOFF character
“DTR” and “CTS” mapping (Open and RI not used)
Flow control mapping (On and RI not used)
H/W flow forced on
(rest unused)
External Clock has not been tested as yet; I can’t guarantee that it works.
Hey, I googled and found that Gene Olsen was made Chief Technical Officer in a 1999 reorganization; is he still at Digi? I knew him at Digi, he’s a great programmer.
I also ran into Jeff Rabe (who did a lot of the concentrator hardware) last year when we were both helping our respective kids move into Centennial Hall at the U of M.
Just fired up two Nu/Xi boards in my oldest working mac and they seem to work, though I don’t yet have anything on that computer that talks across the serial ports.