Dan
Boot up Error codes
-
- KVRist
- 110 posts since 2 Dec, 2006
This is a followup on the boot up scare episode of January 10, 2014. Last night I did get the same error and on the self test the two error codes were: 31 and 15. Two things I noticed were that I was unable to connect to my computer via a crossover cable to use the receptor tools on my laptop and editing from the front panel were no longer available. My goal was to try and evaluate why a plugin installed recently errored out in the refresh step with a .dll not being recognized and in the log giving a null host response. According to previous communication an 31 error suggests that the system is not up to date. I installed the 2.01 20130709 OS recently and that is the only change I have made other than installing the SWAM instrument plugins for evaluation. The network issue looks like it may be hardware related as a few weeks ago I was able to access the receptor to install the plugins with the crossover cable. Manually re entering the crossover network numbers did not help as the address and netmask boxes are grayed out and underneath it read Error(s)lingering network. Today it says Error(s)ifplugd/ifplugd - starter both dead. Is this just something disconnected or did a componenet fail? HELP
Dan
Dan
-
- KVRian
- 691 posts since 13 May, 2004 from Silicon Valley
Hi Dan,
Muse publishes the error codes here. This is where I am quoting from:
31 = "The system is not up to date. Check for updates using duohost."
15 = "Networking up but services not started"
This is what I would suggest:
1.) First try to establish the network, and update the OS:
a.) Connect Receptor directly to your internet connection (ie. cat 5 to your router, no crossover), and connect a monitor / keyboard directly.
b.) Bring up receptor in 'Mixer Mode' (old UI host)
c.) If you are still getting the 'lingering network' message, try manually setting an IP address. Wait a few minutes (sometimes it takes a while for the message to go away, and for Receptor to negotiate the address with your router). Also, be sure the IP address you use does not collide with anything already connected to your router.
d.) after (c), change your network assignment on receptor to DHCP. You can only autoupdate from DHCP.
e.) reboot your receptor on to Duo Host (new UI Host).
f.) go to your software settings, and 'look for system update'.
This should update all components needed to their latest revisions.
Hopefully there are no problems along the way, but if there is, you probably need someone at Muse's support to walk you through this.
2.) Open a ticket, get someone in support to look at your system-log, and figure out why you are getting the code 31.
I hope this helps. Good Luck, Dan.
Regards,
Kevin L
Muse publishes the error codes here. This is where I am quoting from:
31 = "The system is not up to date. Check for updates using duohost."
15 = "Networking up but services not started"
This is what I would suggest:
1.) First try to establish the network, and update the OS:
a.) Connect Receptor directly to your internet connection (ie. cat 5 to your router, no crossover), and connect a monitor / keyboard directly.
b.) Bring up receptor in 'Mixer Mode' (old UI host)
c.) If you are still getting the 'lingering network' message, try manually setting an IP address. Wait a few minutes (sometimes it takes a while for the message to go away, and for Receptor to negotiate the address with your router). Also, be sure the IP address you use does not collide with anything already connected to your router.
d.) after (c), change your network assignment on receptor to DHCP. You can only autoupdate from DHCP.
e.) reboot your receptor on to Duo Host (new UI Host).
f.) go to your software settings, and 'look for system update'.
This should update all components needed to their latest revisions.
Hopefully there are no problems along the way, but if there is, you probably need someone at Muse's support to walk you through this.
2.) Open a ticket, get someone in support to look at your system-log, and figure out why you are getting the code 31.
I hope this helps. Good Luck, Dan.
Regards,
Kevin L
-
- KVRist
- Topic Starter
- 110 posts since 2 Dec, 2006
Sounds like a software issue thankfully. Glad it's not hardware related from the sound of it. I will look into this as soon as I can. They sent me a beta of version 2 for the 2series receptors (mine's a 2+) under the premise that I would not divulge that they did so I hope this isn't affecting that. I know that update was a priced update and i don't know if what I have varies from what eventually shipped. I am also not sure if what I am doing will allow me to work outside of mixer mode because of a couple of plugins I am using and the workarounds I use to get them to work as close to how I would like but that's another story. Thanks for the response.
Dan
Dan
-
nathankingcole nathankingcole https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=107457
- KVRist
- 224 posts since 15 May, 2006
Thanks for posting the error code link! I have been having the error startup message and self test option coming up. I got some support from Muse and it seemed to have been an issue with the soundcard having come slightly loose. I like the error code system for more quick and accurate trouble shooting, but the inconsistency of the boot up error screen process is troubling. I have had the unit start with an error, self test, shut down, restart with error screen, self test, shut down, then load fine. I haven't determined if there is a protocol to getting the normal startup after an error.