PLEASE NOTE: VoxPro Controllers should not be returned to Wheatstone using this form. Refer to this document for VoxPro Controller information.

Possible Solution:

In Navigator, go to the problem blade and ensure that the "Slave Mode" box isn't checked under Master Preference. Also check that Master Preference is enabled; if this has been turned off, blades will not properly enter the system if they can't find a master.

Possible Solution:

One or more of the 2142 op-amp IC chips is more than likely bad, and it's shorting out the power supply. Failed IC chips may be hot to the touch. Try removing the socketed ICs and boot the blade up; if the Wheatstone logo stops flashing, replace the failed ICs. This document tells you which IC maps to which output. You can purchase the chips online in the Wheatstone Store.

Possible Solution:

One or more of the 2142 op-amp IC chips could be bad. Failed ICs may be hot to the touch. 

This document will tell you which chips match to which outputs. These chips are socketed and available for purchase online in the Wheatstone Store.

Possible Solution:

Check your IP settings, swap your cable, or try a different switch port. Try turning off the PC firewall. If Navigator can't connect, go to Preferences, and click the Set button under Network to make sure that Navigator is talking on the correct IP. Go to a command prompt and try to ping the device to rule out a network issue.

Before you proceed:

Connect with the Surface Setup GUI to your console. Make sure that the correct IP address and Blade ID of the Mix Engine blade are both displayed under Blade Info. If not, enter the information, click apply, and then reboot the surface so the console can connect to the mix engine.

Before you proceed:

Some consoles need to be added as a peripheral device in Navigator (see the console manual for details) for the headphone jack and cue speaker destinations to appear. On the LXE, the headphone jack and cue speaker need to be added as devices on the meter bridge. So check that the destinations exist, and then check that the headphone and cue source are routed to their appropriate destination.  Call us in support if you need help with this; you may not need to send anything in.

Before you proceed:

Check the status LED on the console power supply to ensure it is making power. Ensure the power supply cable is seated correctly and securely. Confirm the DC cable going to the console isn't loose or disconnected.

If this is a LXE and all of the OLEDs are dark, call us in support; we may be able to remotely connect and reprogram the modules without needing to ship anything in.

Before you proceed:

Our support team can remote into your local PC and reload the software in the panel host cards. We should try that first. If we do need you to send anything in, it will just be the panel host cards and not the entire console. Give us a call and we will help you troubleshoot this further.

Before you proceed:

This is most likely an issue with the Surface Host CPU, which on a Blade 3 is contained inside the console mix engine blade and not within the console. Call us in support and we will help you get the parts that you need to do the work yourself without having to ship the blade back and forth.

Possible Solution:

If the M-1 has all LEDs on the front panel lit and appears to be locked up, try re-programming the IP using the mac address in the M-1 GUI. Right click on the control area and click Hardware/Assign IP. Input MAC address from sticker on unit and start. We advise plugging straight into the unit for this.

Possible Solution:

Check IC chips with socket connections and all processor sound settings.

PLEASE NOTE: VoxPro Controllers should not be returned to Wheatstone using this form. Refer to this document for VoxPro Controller information.

Possible Solution:

In Navigator, go to the problem blade and ensure that the "Slave Mode" box isn't checked under Master Preference. Also check that Master Preference is enabled; if this has been turned off, blades will not properly enter the system if they can't find a master.

Possible Solution:

One or more of the 2142 op-amp IC chips is more than likely bad, and it's shorting out the power supply. Failed IC chips may be hot to the touch. Try removing the socketed ICs and boot the blade up; if the Wheatstone logo stops flashing, replace the failed ICs. This document tells you which IC maps to which output. You can purchase the chips online in the Wheatstone Store.

Possible Solution:

One or more of the 2142 op-amp IC chips could be bad. Failed ICs may be hot to the touch. 

This document will tell you which chips match to which outputs. These chips are socketed and available for purchase online in the Wheatstone Store.

Possible Solution:

Check your IP settings, swap your cable, or try a different switch port. Try turning off the PC firewall. If Navigator can't connect, go to Preferences, and click the Set button under Network to make sure that Navigator is talking on the correct IP. Go to a command prompt and try to ping the device to rule out a network issue.

Before you proceed:

Connect with the Surface Setup GUI to your console. Make sure that the correct IP address and Blade ID of the Mix Engine blade are both displayed under Blade Info. If not, enter the information, click apply, and then reboot the surface so the console can connect to the mix engine.

Before you proceed:

Some consoles need to be added as a peripheral device in Navigator (see the console manual for details) for the headphone jack and cue speaker destinations to appear. On the LXE, the headphone jack and cue speaker need to be added as devices on the meter bridge. So check that the destinations exist, and then check that the headphone and cue source are routed to their appropriate destination.  Call us in support if you need help with this; you may not need to send anything in.

Before you proceed:

Check the status LED on the console power supply to ensure it is making power. Ensure the power supply cable is seated correctly and securely. Confirm the DC cable going to the console isn't loose or disconnected.

If this is a LXE and all of the OLEDs are dark, call us in support; we may be able to remotely connect and reprogram the modules without needing to ship anything in.

Before you proceed:

Our support team can remote into your local PC and reload the software in the panel host cards. We should try that first. If we do need you to send anything in, it will just be the panel host cards and not the entire console. Give us a call and we will help you troubleshoot this further.

Before you proceed:

This is most likely an issue with the Surface Host CPU, which on a Blade 3 is contained inside the console mix engine blade and not within the console. Call us in support and we will help you get the parts that you need to do the work yourself without having to ship the blade back and forth.

Possible Solution:

If the M-1 has all LEDs on the front panel lit and appears to be locked up, try re-programming the IP using the mac address in the M-1 GUI. Right click on the control area and click Hardware/Assign IP. Input MAC address from sticker on unit and start. We advise plugging straight into the unit for this.

Possible Solution:

Check IC chips with socket connections and all processor sound settings.