Sony RM-AV2100 Operating Instructions (primary manual) - Page 56

Troubleshooting continued, Symptom, Remedy

Page 56 highlights

Troubleshooting (continued) Symptom Remedy You hear beeps ("pip, pip, pip, pip, pip") and "NG" flashes. • Learning has not succeeded. See "For accurate learning" (page 20) and try the learning procedure again (page 16). • The component codes cannot be set. See the supplied "Component Code Numbers" and try setting the component codes again (page 8). • The data have not been transferred. See "Transferring data" (page 41) and try transferring the data again. • The data have not been received. See "Receiving the data" (page 43) and try receiving the data again. You hear beeps ("pip, pip") and "NG" flashes. • The Preset Lock function is on. Unlock the Preset Lock function (page 48), and try the component code setting or the learning function. • Signals have been programmed for that Component Select or SYSTEM CONTROL button using the learning function. Clear the learned signals (page 34, 40) and try programming the System Control function again. • Signal has been programmed for that key using the learning function. Clear the signal(s) (pages 20 and 21) and try programming the function or the display for the same key again, or try with another Component Select button. • Signals have been programmed for that macro key using the learning function. Clear the learned signals (page 20) and try programming the Channel Macro function for the same key again, or try with another macro key. • There are some keys, on which signals have been programmed, on the display for the Component Select button of the Commander when the commander receives the data from another Commander. Clear the signals (pages 20, 21 and "Notes" on page 44) and try receiving the data again. "NG" appears during learning. • Clear infrequently used learned keys (page 20), then carry out learning operations. A system control program does not function correctly. • Make sure that you have programmed the commands in the correct order (page 23). • Try changing the orientation of the Commander. If that does not help, try placing the components as close to each other as possible. • Check the status of the components and make sure that you have set the components properly to receive commands (page 27). • The component codes are changed or a new signals have been learned for a key or button that has been programmed with a series of commands. In this case, the new signals are transmitted when the series of commands is executed. • The interval may be too short. See "Changing the interval between operation steps" (page 30) and set a longer interval. 56

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76

56
Symptom
You hear beeps (“pip,
pip, pip, pip, pip”) and
“NG” flashes.
You hear beeps (“pip,
pip”) and “NG” flashes.
“NG” appears during
learning.
A system control
program does not
function correctly.
Remedy
• Learning has not succeeded. See “For accurate learning” (page 20) and
try the learning procedure again (page 16).
• The component codes cannot be set. See the supplied “Component
Code Numbers” and try setting the component codes again (page 8).
• The data have not been transferred. See “Transferring data” (page 41)
and try transferring the data again.
• The data have not been received. See “Receiving the data” (page 43) and
try receiving the data again.
• The Preset Lock function is on. Unlock the Preset Lock function (page
48), and try the component code setting or the learning function.
• Signals have been programmed for that Component Select or SYSTEM
CONTROL button using the learning function. Clear the learned signals
(page 34, 40) and try programming the System Control function again.
• Signal has been programmed for that key using the learning function.
Clear the signal(s) (pages 20 and 21) and try programming the function
or the display for the same key again, or try with another Component
Select button.
• Signals have been programmed for that macro key using the learning
function. Clear the learned signals (page 20) and try programming the
Channel Macro function for the same key again, or try with another
macro key.
• There are some keys, on which signals have been programmed, on the
display for the Component Select button of the Commander when the
commander receives the data from another Commander. Clear the
signals (pages 20, 21 and “Notes” on page 44) and try receiving the data
again.
• Clear infrequently used learned keys (page 20), then carry out learning
operations.
• Make sure that you have programmed the commands in the correct
order (page 23).
• Try changing the orientation of the Commander.
If that does not help,
try placing the components as close to each other as possible.
• Check the status of the components and make sure that you have set the
components properly to receive commands (page 27).
• The component codes are changed or a new signals have been learned
for a key or button that has been programmed with a series of
commands. In this case, the new signals are transmitted when the series
of commands is executed.
• The interval may be too short. See “Changing the interval between
operation steps” (page 30) and set a longer interval.
Troubleshooting (continued)