If you are at a complete loss as to why your setup is not
working the way you want it to work try following the instructions below.
Beware ! To systematically debug your setup follow all steps from beginning
to end. Do not skip any part of the following list !
1. Identify versions.
There are a number of ways to find out what versions of the
hardware and of the firmware are present in your Digitizer. Find out the
versions of your Digitizer and make sure you're using the correct editor
for it (see below).
1a. Read the Digitizer bottom sticker.
On Digitizers with firmware v4.0 and higher the version
information is printed on the bottom in the form "ab-cd-ef-nnnn", where
a.b = firmware version, c.def = hardware version and nnnn = serial number.
There are a few Digitizers with firmware v4.0 that have
the number on the sticker printed in the form "ab-00-nnnn", where a.b
= firmware version and nnnn = serial number.
Digitizers with firmware upto v3.5 used the form "cd-ghi-nnnn"
or "cdghi-nnn", where c.d = hardware version, g.hi = required editor version
and nnnn = serial number.
1b. Read the EPROM chip sticker.
Regardless of the information printed on the Digitizer bottom
sticker, it is possible that the Digitizer has been updated with a new
EPROM chip. This chip stores the firmware. In that
case it is possible to find the firmware version by opening the Digitizer
(peel off the rubber feet to uncover the screws) and locating the chip
with text on it.
For Digitizers with firmware upto v3.5 the text may contain
a three digit number which is actually the version number of the required
editor.
For Digitizers with firmware upto v3.5 the text may begin
with DCC. In that case the two digits following DCC are the version and
its decimal.
1d. Use sysex communication.
For Digitizers with firmware upto v3.5 it's possible to find
the version number by examining the sysex string that is sent out upon
reset or powerup. If there is a number sent immediately after the value
35 and before 247 then that is the firmware version and its decimal. This
method is used in editor v1.5 by clicking the About menu (make sure MIDI
communication is working though).
Digitizers with firmware v4.0 or v4.1 don't send the version
information upon powerup but enable you to send a request for version
information (see the MIDI implementation docs for firmware v4.0 and v4.1).
With the editor v2.10 it is possible to obtain the version information
in this way by clicking on the About menu (you need to have established
MIDI communication first though).
2. Setup for debugging.
Disconnect the Digitizer from everything - no power, no MIDI
cables, no sensors. If possible use a "clean" computer, with nothing but
the operating system installed and no peripheral devices, except your
MIDI interface attached (and installed). Make sure you have the latest
version of the I-CubeX editor software and MIDI drivers. For firmware
v3.5, use editor v1.51 (MacOS) or v1.52 (Windows). For firmware v4.0 use
editor v2.0. For firmware v4.1, use editor v2.1.
3. Digitizer debugging.
Plug in the power and at the same time look at the LEDs.
a: Does the red power LED of the Digitizer light up ?
No:the fuse (a small glass tube with a very thin wire inside
it) inside the Digitizer may be blown (ie. the wire in the fuse is broken).
You can open the Digitizer by taking out the screws underneath the rubber
feet. Then replace the fuse - use only a 20x5 mm 1.5 A / 250 V fast acting
fuse. If the power LED still doesn't light up after replacing the fuse,
email us for further assistance.
3b: What does the green MIDI out LED do ?
Never flashes, never turns on: There is a problem with the
Digitizer hardware. Email us for further assistance.
Flashes once, then stays off: The Digitizer is in host mode.
Flashes twice, then stays off:The
Digitizer is in standalone mode.
Flashes once or twice, then lights up intermittently but at
a very high speed: Connect the MIDI cables and use the I-CubeX editor
to turn all inputs off individually. If that doesn't stop the MIDI out
LED from flashing continuously, change the sampling interval to 1000 -
the LED should start flashing only once every second. Then try again to
turn off all inputs.
Flashes once or twice, then stays steadily lit: There is a
problem with the Digitizer hardware. Email us for further assistance.
4. Editor debugging.
Before installing any software make sure you have the right
version of the editor. For Digitizers with firmware v3.5 use editor v1.52
(windows) or v1.51 (MacOS). For Digitizers with firmware 4.0 use editor
v2.00. For Digitizers with firmware v4.1 use editor v2.10.
If the editor doesn't install, installs with error messages,
crashes unexpectedly or complains otherwise with error messages, try any
or all of the following:
Make sure you have followed the installation instructions
in the readme file included with the installation package.
Power down and restart the computer.
Run scan disk (Windows) or DiskAid (MacOS) to verify the hard
disk is in good condition.
Unplug as many peripheral devices as possible and uninstall
their drivers.
Before installing or running the editor, close all programs
that you don't need for running the I-CubeX editor, including programs
in the system tray (Windows) or system extensions (MacOS). If you know
what you're doing in Windows, you may also close more programs by pressing
ctrl-alt-delete once and ending tasks in the task manager.
Minimize the number of installed programs (this may mean uninstalling
all the programs you may have installed, except the I-CubeX editor of
course)
Once you successfully installed and run the I-CubeX editor
start adding other software and peripherals, each time checking whether
the editor is still working given the new software or hardware addition.
5. Digitizer - Editor communications debugging.
Make sure there are no other programs running, including Max
(on MacOS). Reduce system tray icons (Windows) and extensions (MacOS)
to a minimum. Install (if not already installed) and startup the I-CubeX
editor. Connect a MIDI cable from the MIDI output of the MIDI interface
to the Digitizer MIDI input and a MIDI cable from the MIDI input of the
MIDI interface to the Digitizer MIDI output. Create a sensor object in
the editor and turn it on. If available use the "Check MIDI connections"
option in the I-CubeX editor to verify your MIDI connections, and/or go
through the questions below.
5a: Is the MIDI out LED of the MIDI interface flashing when
you turn on the input ?
No: Check whether you have selected the right MIDI device
in the I-CubeX editor.
Yes: Continue with 5b.
5b: Is the MIDI in LED of the Digitizer flashing when you
turn on the input ?
No: There is a problem with the MIDI cable connecting the
MIDI out of the MIDI interface and the Digitizer's MIDI input, or there
is a problem with the Digitizer's MIDI input. In the latter case emai
us for further assistance.
Yes: Continue with 5c.
5c: Is the MIDI out LED of the Digitizer flashing right after
the MIDI in LED flashes ?
No: There is a problem with the Digitizer hardware. Email
us for further assistance.
Yes: Continue with 5d.
5d: Is the MIDI in LED of the MIDI interface flashing when
you turn on the input ?
No: There is a problem with the MIDI cable connecting the
Digitizer's MIDI input and the MIDI out of the MIDI interface, or there
is a problem with the MIDI input of the MIDI interface.
If you cannot get your computer, MIDI drivers, MIDI interface
or MIDI cables to behave, try another MIDI interface and/or cables, delete
(power down, reboot) and re-install the MIDI drivers. Adding and installing
an extra MIDI interface may also help getting the primary MIDI interface
up and running. A MIDI monitoring tool like MIDI-Ox is helpful for checking whether the MIDI
interface is working. Your last resort may be to simply use another computer
(consider switching from MacOS to Windows or vice versa) if possible.
6. Digitizer configuration debugging.
Make sure the Digitizer is in stand alone mode. Connect a
sensor to input #1 of the Digitizer. Make sure the red wire of the sensor
faces up. Using the I-CubeX editor, create a new configuration, insert
a sensor object and turn on the sensor input.
6a: Is the Digitizer MIDI out LED flashing when activating
a sensor (e.g. touch a Touch sensor)?
No: Set the sampling rate to 50. The sampling rate may accidentally
have been set to it's maximum value (so that data is only sent once every
16 seconds and you may not have noticed that sensor data was sent by the
Digitizer). If setting the sampling rate has no effect, the Digitizer's
sysex ID may accidentally have been set to a number other than used in
your Max patches. Click the "Reset sysex ID" option in the I-CubeX
editor to fix this.
Yes: Continue with 6b.
6b: Is the green monitor bar in the editor showing that sensor
data is being received ?
No: Make sure the Digitizer is in stand alone mode.
|