Lectrosonics PT3 User Manual Page 23

  • Download
  • Add to my manuals
  • Print
  • Page
    / 30
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 22
Protocol Translator
TROUBLESHOOTING
The following are just general guidelines and initial suggestions. If a problem persists, please refer to the section,
SERVICE AND REPAIR.
No MIDI
communication
No AXlink
communication
No LecNet actions
AMX touch panel beeps
incessantly
MIDI translation
intermittent
AXlink channels work,
levels do not
AXlink translation intermit-
tent when MIDI also used
Monitored values
updated too infrequently
PT3 software connects
and disconnects
sporadically
PC cannot program PT3
LecNet LED glows
steadily, actions not
performed
Connect a known-good MIDI cable from the MIDI output jack of a musical keyboard to the PT3.
Set the keyboard to OMNI mode and be sure the base MIDI channel matches the MIDI channel
programmed into the PT3. If necessary, reprogram the PT3 with the base MIDI channel used by
the keyboard. Notes on the keyboard should cause the MIDI LED to flicker. Translated MIDI
messages should also cause the LecNet LED to flicker. If the LecNet LED glows steadily in
between notes and no translations are performed, see the last troubleshooting entry in the list.
Be sure AMX master is operational and cable is connected and correctly wired.The AXlink port
status LED should flash on and off slowly. Translated AXlink messages should cause the LecNet
LED to flicker. The PT3 should be detected, at least as an unknown device with the correct AXlink
device number, by the AMX master. From the AXCESS terminal emulator, the SHOW DEVICE
command may be used to verify this. If the LecNet LED glows steadily in between AXlink mes-
sages and no translations are performed, see the last troubleshooting entry in the list.
If the LecNet LED glows steadily in between incoming MIDI or AXlink messages, please refer to
the last troubleshooting entry in the list. While rapidly issuing a translated MIDI or AXlink mes-
sage, observe the LecNet LED. If it flashes rapidly in synch with your actions, a LecNet action is
being taken, but perhaps it isn't having the desired effect. Check your actions to make sure they
do what you want. Be sure you are addressing the correct LecNet device. Note that AM8 and
AM16 volume changes won't work until the Remote Levels On action is performed once. If the
LecNet LED flashes no faster than once a second, despite more rapid sending of translated
incoming messages, the LecNet device is either not connected or set to the wrong LecNet
address. The PT3's LecNet interface is timing out.
Try disconnecting the PT3. If this stops the beeping, then very likely there is an AXlink device
number conflict. Reprogram the PT3 after selecting a new AXlink device number in the Options
window. To find an available device number, start the AXCESS language, invoke the terminal
emulator, then type SHOW DEVICE. Any number not appearing in the list may be used.
The MIDI standard permits incomplete messages to be sent for maximum efficiency. This is valid
and will never be problematic if both the sender and receiver are always connected. If the MIDI
source (e.g. keyboard) has sent some messages before the PT3 was connected, it may be
necessary to issue a program change, note or controller change to force resynchronization. For a
more detailed explanation, see MIDI DEVICE SPECIFICATIONS.
The PT3 might be set to a bank other than 0. See AXLINK DEVICE SPECIFICATIONS for an
explanation of the BANK0 through BANK7 commands. The AMX master might not have the
levels properly connected. Refer to the included sample AXCESS code for the proper use of
CONNECT_LEVEL.
The PT3 was not designed to perform AXlink and MIDI translations at the same time. Both are
high-speed protocols which require the PT3's full attention.
Owing to the underlying protocols and communication speeds, as much as a two second latency
may be experienced when many monitors are active simultaneously. With fewer monitors active,
much crisper response is obtained. Action and string response times are not significantly affected
by the number of active monitors.
The various components of LecNet Master Pro must share not only the serial port connecting to
the LecNet, but the control of the LecNet devices themselves. When the PT3 software does not
occupy the active window, it suspends operation of the PT3, then releases the serial port. While
this behavior can be confusing, it was designed to allow the user to switch as freely as possible
among various LecNet control panel programs.
Be sure the PC's COM port is not used by any other device and the cable is connected to the PT3.
LecNet Master Pro should be able to detect the PT3 at LecNet address 255.
When the LecNet LED glows steadily, the PT3 is in standby mode. This mode is selected by
LecNet software when LecNet devices besides the PT3 must be accessed or controlled. The PT3
should return to normal operating mode when the PT3 software occupies the active window on
your computer. The PT3 may be forced into normal operating mode by unplugging the PC cable
and powering the PT3 off and on again.
Rio Rancho, NM – USA
23
Page view 22
1 2 ... 18 19 20 21 22 23 24 25 26 27 28 29 30

Comments to this Manuals

No comments