XM / Sirius Worklog - Page 4

smeesseman · 09-07-2007, 06:38 PM

Quote: Originally Posted by midiwall

is that when the symptom was happening, looking at the XM settings showed... (wait for it, it's a good one!) ...Device = XMPCR.

Very weird.

"The settings" - as you went into Settings when CF running, and it was listed in Settings as XMPCR? Or you looked at the config.xml file right after it happened? Can you give me all the info you can on that?

midiwall · 09-07-2007, 07:02 PM

Quote: Originally Posted by smeesseman

"The settings" - as you went into Settings when CF running, and it was listed in Settings as XMPCR? Or you looked at the config.xml file right after it happened? Can you give me all the info you can on that?

Very similar to:

Back from hibernate
Noted XM not playing, no track info, but the signal strength info seemed valid (i.e., non-zero and changing live)
Randomly selected stations, bounced in and out of XM, started playback from Media, happened to look at NAV. Everything else seemed fine.
Looked at Settings from within CF, noted that Device = XMPCR
Exited CF, reloaded CF, XM came up. CF showed Device = XMDirect

I didn't explicitly look at the XML, but given that a restart of CF brought it back and showed valid info, I'd bet that the XML was "correct" in that it was still showing "XMDirect".

I'll check for sure the next time it happens.

smeesseman · 09-07-2007, 07:19 PM

Quote: Originally Posted by midiwall

Very similar to:

Back from hibernate
Noted XM not playing, no track info, but the signal strength info seemed valid (i.e., non-zero and changing live)
Randomly selected stations, bounced in and out of XM, started playback from Media, happened to look at NAV. Everything else seemed fine.
Looked at Settings from within CF, noted that Device = XMPCR
Exited CF, reloaded CF, XM came up. CF showed Device = XMDirect

I didn't explicitly look at the XML, but given that a restart of CF brought it back and showed valid info, I'd bet that the XML was "correct" in that it was still showing "XMDirect".

I'll check for sure the next time it happens.

When you come out of hibernation and it's still working, in Settings does it show XMDirect as it should? Put another way, it shows XMPCR only in the case where it does not work coming out of hibernation?

midiwall · 09-07-2007, 08:11 PM

Quote: Originally Posted by smeesseman

When you come out of hibernation and it's still working, in Settings does it show XMDirect as it should? Put another way, it shows XMPCR only in the case where it does not work coming out of hibernation?

A far as I've seen, yes, this is true. But honestly, I've fallen into the trap of only looking for the source of trouble when there there _is_ trouble.

I'll keep a closer eye.

Any hints on working with the log file so that I can get you pieces from there when this happens? Though, it looks more like the logging is just focused on commands and responses to the receiver.

smeesseman · 09-08-2007, 09:30 AM

Quote: Originally Posted by midiwall

A far as I've seen, yes, this is true. But honestly, I've fallen into the trap of only looking for the source of trouble when there there _is_ trouble.

I'll keep a closer eye.

Any hints on working with the log file so that I can get you pieces from there when this happens? Though, it looks more like the logging is just focused on commands and responses to the receiver.

If you can send it all that would be great (scottpm@ameritech.net). If too big look for the text "PowerMode Change:" and we can look around/after that area, which would indicate the system coming out of hibernation... The commands will tell me if it is trying to do the XMPCR way, or the XMDirect way, it won't say explicitly...

midiwall · 09-09-2007, 05:58 PM

Okay, 'tis your's for the pickin'!

http://www.midiwall.com/bug/misc/20070909_XMLog.zip
The ZIP is about 328k

It looks like there are two power cycles in there, but I've gone through 5 hibernate/resumes today, (two of them were hangs), so I'm curious as to why not all 5 are logged. Do you have a max size on the log? Or is it circular?

What I'll start doing is copying off the logs immediately after a hang. Sorry for this taking so long Scott.

jwlionking · 09-09-2007, 06:22 PM

Are you guys able to change your volume of xm? With the last update everything is working great but cannot change volume (only in XM) It will mute when you change to Music or whatever, just no volume control.

smeesseman · 09-10-2007, 10:21 AM

Quote: Originally Posted by jwlionking

Are you guys able to change your volume of xm? With the last update everything is working great but cannot change volume (only in XM) It will mute when you change to Music or whatever, just no volume control.

Hmm, not sure, maybe David can chime on on this...

smeesseman · 09-10-2007, 10:23 AM

Quote: Originally Posted by midiwall

Okay, 'tis your's for the pickin'!

http://www.midiwall.com/bug/misc/20070909_XMLog.zip
The ZIP is about 328k

It looks like there are two power cycles in there, but I've gone through 5 hibernate/resumes today, (two of them were hangs), so I'm curious as to why not all 5 are logged. Do you have a max size on the log? Or is it circular?

What I'll start doing is copying off the logs immediately after a hang. Sorry for this taking so long Scott.

It erases itself if it grows larger than 5 MB. But, from what I see, the log you sent was never erased, not sure why all 5 hibernates did not show up. The resumes that this log is showing though seem to be working and normal? Yeah, send me your log right after XM does not come back up after hibernating...

- Scott

midiwall · 09-10-2007, 11:35 AM

Okay... here's a fresh one. I caught it about 5-7 minutes (as soon as I could pull over!) after a failed resume.

http://www.midiwall.com/bug/misc/20070910_XMLog.zip
The ZIP is about 266k

smeesseman · 09-10-2007, 02:08 PM

Quote: Originally Posted by midiwall

Okay... here's a fresh one. I caught it about 5-7 minutes (as soon as I could pull over!) after a failed resume.

http://www.midiwall.com/bug/misc/20070910_XMLog.zip
The ZIP is about 266k

Aaah, that helped me find the issue. I'll have a new update posted within the hour...

smeesseman · 09-10-2007, 02:26 PM

A new build has been uploaded. This update includes attemped fix to hibernation/resume issues, as well as some other minor things, please see post #1 for details...

midiwall · 09-10-2007, 02:38 PM

Quote: Originally Posted by smeesseman

A new build has been uploaded. This update includes attempted fix to hibernation/resume issues, as well as some other minor things, please see post #1 for details...

Kick arse!

midiwall · 09-10-2007, 03:15 PM

Quote: Originally Posted by smeesseman

EDIT: 9/10/2007 3:28 PM EDT
Version 1.207
* Added function to check config.xml, in this way we do not include config.xml in the zip file below, i.e. your XM Settings will not get erased every time you update the SatRadio plugin from this thread...

Sounds good Scott, but... you don't create it if it's not there.

1.207 is running on the Bug, I'll let you know how it goes. Thanks!

smeesseman · 09-10-2007, 08:19 PM

Quote: Originally Posted by midiwall

Sounds good Scott, but... you don't create it if it's not there.

1.207 is running on the Bug, I'll let you know how it goes. Thanks!

that figures, i'm looking in the wrong path for it (thanks for checking that), i'll get this updated tonight sometime after I get the kids down to bed...

EDIT: Fixed @ 10:05PM U.S. EDT