my mvp crashes and restart randomly

[skippy_nz]

ive got a new log - this time i was sitting at my lappy checking the forum and my mvp was sitting at the main page then just rebooted all by itself - think theres a ghost in my system

[sub]

This was another 'the MVP disconnected for some unknown reason', which we unfortunately have had from time to time, ever since GB-PVR added MVP support.

There isnt really any way to tell specifically why it disconnected, unless you do the serial port mod to you MVP, which allows you can view the MVP debug messages via a terminal emulator. This would give a reason why it disconnected.

[skippy_nz]

This was another 'the MVP disconnected for some unknown reason', which we unfortunately have had from time to time, ever since GB-PVR added MVP support.

There isnt really any way to tell specifically why it disconnected, unless you do the serial port mod to you MVP, which allows you can view the MVP debug messages via a terminal emulator. This would give a reason why it disconnected.

is there any info on what / when / and how to do this mod ?

[sub]

There was an old post on http://www.shspvr.com/smf about adding a serial port.

[skippy_nz]

There was an old post on http://www.shspvr.com/smf about adding a serial port.

that sounds like hard work - think i will just have live with the thing rebooting every now and then.

cheers anyway

[mvallevand]

This was another 'the MVP disconnected for some unknown reason', which we unfortunately have had from time to time, ever since GB-PVR added MVP support.

There isnt really any way to tell specifically why it disconnected, unless you do the serial port mod to you MVP, which allows you can view the MVP debug messages via a terminal emulator. This would give a reason why it disconnected.

Adding a serial port is tough, and in my experience I haven't seen the benefit in debugging this particular problem with the Hauppauge dongle.

In emulation mode where I have more debug control, I get the same error although at the socket level it appears to be gbpvr that is closing the socket. My personal feeling it has to do with the reception of the Hauppauge heartbeat and the screen refresh commands. Overall gbpvr is more sensitive than the Hauppauge server when it comes to receiving an incorrect command sequence.

Also a more current link on adding a serial port to either mvp model is at

http://www.mvpmc.org/mvpmc_hardware_howto.html

Martin

[sub]

Adding a serial port is tough, and in my experience I haven't seen the benefit in debugging this particular problem with the Hauppauge dongle.

I actually find it really useful, and the messages usually give pretty good clues as to what the MVP didnr like. ...but my then my MVP came with a serial port, so I didnt have to grief of adding one myself.

In emulation mode where I have more debug control, I get the same error although at the socket level it appears to be gbpvr that is closing the socket. My personal feeling it has to do with the reception of the Hauppauge heartbeat and the screen refresh commands. Overall gbpvr is more sensitive than the Hauppauge server when it comes to receiving an incorrect command sequence.

Thats not really been something I've seen with the Hauppauge MVP client - I'm guessing this relates more to the differences between your emulation and the real MVP software. The most common thing I see is the MVP choosing to disconnect because of GB-PVR taking too long to respond to its ping command.

[mvallevand]

Thats not really been something I've seen with the Hauppauge MVP client - I'm guessing this relates more to the differences between your emulation and the real MVP software. The most common thing I see is the MVP choosing to disconnect because of GB-PVR taking too long to respond to its ping command.

Without a doubt the problem is mine but I do see exactly the opposite scenario, I see a ping go to gbpvr, ethereal sees it and then the connection dies, with the gbpvr error message too long to respond or whatever.

Martin

[skippy_nz]

I actually find it really useful, and the messages usually give pretty good clues as to what the MVP didnr like. ...but my then my MVP came with a serial port, so I didnt have to grief of adding one myself.

Thats not really been something I've seen with the Hauppauge MVP client - I'm guessing this relates more to the differences between your emulation and the real MVP software. The most common thing I see is the MVP choosing to disconnect because of GB-PVR taking too long to respond to its ping command.

hey sub - just had a thought - since i live in welly aswell - do you want to swap mvp's for a day or 2 and see if i can get some logs for you to see if its something you can fix ?

cheers
skip

[skippy_nz]

Some routers don't support media streaming so well, that's where you might want to look into which ones does. Mine does.

i dont think thats my issue as its rebooting when the mvp is at the main menu - if it crashed while streaming then i think you have a vaild point - but mine is always when pressing the back button or sitting a the menu

cheers
skip