Korg Polysix MIDI Interface
Korg Polysix MIDI Interface
Korg Polysix MIDI Interface
Korg Polysix MIDI Interface
P6
P6
P6
P6----M
M
M
M Owner‘s
Owner‘s
Owner‘s
Owner‘s Manual
Manual
Manual
Manual
8
88
8----427 / v. 1.00
427 / v. 1.00
427 / v. 1.00
427 / v. 1.00
Copyright © 2021 CHD Elektroservis. All rights reserved.
No part of this publication may be reproduced in any form without the written permission of CHD Elektroservis.
22
22
22
22
6
66
6
APPENDICES
APPENDICES
APPENDICES
APPENDICES
6.1
6.1
6.1
6.1 ERROR STATUS INDICATION
ERROR STATUS INDICATION
ERROR STATUS INDICATION
ERROR STATUS INDICATION
If any fatal error occurs during the interface operation, the interface stops the MIDI communication and it
disconnects itself from instrument’s circuits. However, the instrument still can be controlled by its own
keyboard, panel knobs and switches. The error status is indicated by yellow blinking of the interface’s indication
LED. The number of LED blinks is indicating the error type (see table 6). If an error occurs, the interface must be
reset to restore the operation – it is necessary to turn the instrument off and then on after a while.
Table 6
Table 6
Table 6
Table 6 –
––
– Error Types
Error Types
Error Types
Error Types
Number of blinks
Number of blinks
Number of blinks
Number of blinks Error Type
Error Type
Error Type
Error Type
1
Access to interface’s internal memory failed (fatal error)
2
Interface’s internal memory too busy (fatal error)
3
Unsuccessful write to a interface’s internal memory cell (fatal error)
4
MIDI input buffer overflows (can be solved automatically – see chapter 4.1.2)
5
MIDI output buffer overflows (can be solved automatically – see chapter 4.1.2)
6.2
6.2
6.2
6.2 ERRORS CAUSED BY MIDI LOOP
ERRORS CAUSED BY MIDI LOOP
ERRORS CAUSED BY MIDI LOOP
ERRORS CAUSED BY MIDI LOOP
When the P6-M interface is controlled by a sequencer (HW or SW) and the devices are connected bi-
directionally (with both MIDI cables – see fig. 2) and the sequencer isn’t set correctly, communication loop
might occur and the entire MIDI system “freezes”. All MIDI data incoming from sequencer to interface’s input
are transferred to interface’s output (THRU function) and again back to the sequencer in this case. This causes
infinite cyclic transfer of the same MIDI data through the sequencer.
To avoid this situation, throughput of MIDI data from input to output must be turned off in the DAW /
Sequencer. This function is usually called MIDI ECHO or MIDI THRU. Check the user manual of your DAW /
Sequencer for that setting.
Fig. 19
Fig. 19
Fig. 19
Fig. 19 –
––
– Memory protection jumper
Memory protection jumper
Memory protection jumper
Memory protection jumper
6.3
6.3
6.3
6.3 USER MEMORY PROTECTION
USER MEMORY PROTECTION
USER MEMORY PROTECTION
USER MEMORY PROTECTION
All user data stored in the user memory can be
protected against unwanted rewriting after the
memory is filled with your own data (i.e. when you
have saved your own values of global and patch
parameters).
There is a jumper header on the interface board (see
fig. 19). If the two left pins of the header labeled as
MEM are interconnected / shorted by standard jumper
(part of the device delivery), the memory protection is
active. All data can be still read from the memory but
any writting to the memory is disabled.
If you try to write a Data to the memory (e.g. using CC
#119 or a SysEx command) when the protection is
active, the MIDI command is ignored and the interface transmits the [F0 00 20 21 ii 45 70 05 7F xx F7 hex
F0 00 20 21 ii 45 70 05 7F xx F7 hex
F0 00 20 21 ii 45 70 05 7F xx F7 hex
F0 00 20 21 ii 45 70 05 7F xx F7 hex] SysEx
message to MIDI output as an info about the disabled command execution.
Actual status of the memory protection can be also read on demand – for details please see the MIDI SysEx
Communication manual.
Summary of Contents for 8-427
Page 32: ......
