Scrib Posted February 26, 2016 Share Posted February 26, 2016 Not directly a C4 issue, but figure I'd post here in case I am forced to get a new receiver. So my Pioneer Elite VSX-51 just started to act up. It simply drops off the network every few seconds, then reconnects a few seconds later, only to drop off again. This just started happening. No config changes on my end and even plugged it into a different switch and used a different cable to rule out any other issues. I'm going to call Pioneer tomorrow and see if they can help with anything, but I'm not hopeful. I'm on the latest firmware and the unit is about 4 years old. I suppose NIC ports can just fail, but this pisses me off. So on to the real question. What would be a reasonable replacement for this receiver? It needs to be IP controllable, which is why I'm all grumpy about this because I can't control the volume right now on this TV. Obviously needs to be C4 compatible. PING 10.0.1.112 (10.0.1.112): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 Request timeout for icmp_seq 2 Request timeout for icmp_seq 3 Request timeout for icmp_seq 4 Request timeout for icmp_seq 5 Request timeout for icmp_seq 6 Request timeout for icmp_seq 7 Request timeout for icmp_seq 8 Request timeout for icmp_seq 9 Request timeout for icmp_seq 10 Request timeout for icmp_seq 11 Request timeout for icmp_seq 12 Request timeout for icmp_seq 13 64 bytes from 10.0.1.112: icmp_seq=13 ttl=128 time=1185.295 ms 64 bytes from 10.0.1.112: icmp_seq=15 ttl=128 time=5.536 ms 64 bytes from 10.0.1.112: icmp_seq=16 ttl=128 time=1.550 ms 64 bytes from 10.0.1.112: icmp_seq=17 ttl=128 time=2.083 ms 64 bytes from 10.0.1.112: icmp_seq=18 ttl=128 time=10.027 ms 64 bytes from 10.0.1.112: icmp_seq=19 ttl=128 time=6.521 ms 64 bytes from 10.0.1.112: icmp_seq=20 ttl=128 time=6.402 ms Request timeout for icmp_seq 21 Request timeout for icmp_seq 22 Request timeout for icmp_seq 23 Request timeout for icmp_seq 24 Request timeout for icmp_seq 25 Request timeout for icmp_seq 26 Request timeout for icmp_seq 27 Request timeout for icmp_seq 28 Request timeout for icmp_seq 29 Request timeout for icmp_seq 30 Request timeout for icmp_seq 31 Request timeout for icmp_seq 32 Request timeout for icmp_seq 33 Request timeout for icmp_seq 34 Request timeout for icmp_seq 35 Request timeout for icmp_seq 36 Request timeout for icmp_seq 37 Request timeout for icmp_seq 38 Request timeout for icmp_seq 39 Request timeout for icmp_seq 40 Request timeout for icmp_seq 41 Request timeout for icmp_seq 42 64 bytes from 10.0.1.112: icmp_seq=41 ttl=128 time=2901.981 ms 64 bytes from 10.0.1.112: icmp_seq=43 ttl=128 time=897.772 ms 64 bytes from 10.0.1.112: icmp_seq=44 ttl=128 time=1.504 ms 64 bytes from 10.0.1.112: icmp_seq=45 ttl=128 time=3.995 ms 64 bytes from 10.0.1.112: icmp_seq=46 ttl=128 time=2.466 ms 64 bytes from 10.0.1.112: icmp_seq=47 ttl=128 time=4.854 ms 64 bytes from 10.0.1.112: icmp_seq=48 ttl=128 time=6.252 ms 64 bytes from 10.0.1.112: icmp_seq=49 ttl=128 time=3.179 ms 64 bytes from 10.0.1.112: icmp_seq=50 ttl=128 time=15.795 ms Request timeout for icmp_seq 52 Link to comment Share on other sites More sharing options...
Scrib Posted February 26, 2016 Author Share Posted February 26, 2016 For what it's worth, looks like Neil came up with a solution to move me over to a serial connection. That should get me there. Link to comment Share on other sites More sharing options...
SY3 Posted February 26, 2016 Share Posted February 26, 2016 Just 2 nights ago I just had a similar issue happen to my VSX-60. Network connection will stay on for a few hrs and then drop completely. Only way to get it back it is to reset the network settings. Been working for over 2 years without any issues. Moved it over to serial and seems to be working fine now. Link to comment Share on other sites More sharing options...
Scrib Posted February 26, 2016 Author Share Posted February 26, 2016 2 hours ago, sally said: Just 2 nights ago I just had a similar issue happen to my VSX-60. Network connection will stay on for a few hrs and then drop completely. Only way to get it back it is to reset the network settings. Been working for over 2 years without any issues. Moved it over to serial and seems to be working fine now. Interesting. I was told Onkyo's have the same issue, even worse. So you moved over to serial, no issues? I have some cat5 to serial adapters on their way, so I'll make the jump at some point. Link to comment Share on other sites More sharing options...
SY3 Posted February 26, 2016 Share Posted February 26, 2016 I have a HC300 next to the receiver so connecting a serial cable was an easy fix. I don't use any network features of the receiver so that's not so much of an issue. I'll still call Pioneer to see what can be done to fix it. It just 2.5 years old so I think its out of warranty now but still worth a shot. Link to comment Share on other sites More sharing options...
vstar Posted February 26, 2016 Share Posted February 26, 2016 serial is the way to go in my opinion when there is a serial port is available on the device to be controlled even if driver supports IP also still worth it to run a serial connection. Link to comment Share on other sites More sharing options...
jfh Posted February 27, 2016 Share Posted February 27, 2016 11 hours ago, Scrib said: Interesting. I was told Onkyo's have the same issue, even worse. So you moved over to serial, no issues? I have some cat5 to serial adapters on their way, so I'll make the jump at some point. I had Onkyo for over a year with rock solid IP control. I mentioned this in another thread, but there seem to be more problems with receiver IP control since 2.8. I saw a huge jump in unreliability when the only change in my system was the upgrade to 2.8/2.81. There are a number of possible reasons for it, but wirh problems reported for Onkyo/Integration, Pioneer and Yamaha recently you wonder if there is an underlying problem with C4 (or the drivers all not playing nice after the 2.8 upgrade). It doesn't seem that C4 is interested in the issue though. I've had a problem ticket opened for months without a peep. Using serial is fine, as long as your receiver has a serial port. Otherwise you have to get creative and create a programmatic babysitter for your receiver. A wireless outlet switch, the Chowmain Ping driver and some programming have probably stopped my wife from insisting that we rip out C4 ... Link to comment Share on other sites More sharing options...
jfh Posted February 27, 2016 Share Posted February 27, 2016 11 hours ago, Scrib said: Interesting. I was told Onkyo's have the same issue, even worse. So you moved over to serial, no issues? I have some cat5 to serial adapters on their way, so I'll make the jump at some point. I had Onkyo for over a year with rock solid IP control. I mentioned this in another thread, but there seem to be more problems with receiver IP control since 2.8. I saw a huge jump in unreliability when the only change in my system was the upgrade to 2.8/2.81. There are a number of possible reasons for it, but wirh problems reported for Onkyo/Integration, Pioneer and Yamaha recently you wonder if there is an underlying problem with C4 (or the drivers all not playing nice after the 2.8 upgrade). It doesn't seem that C4 is interested in the issue though. I've had a problem ticket opened for months without a peep. Using serial is fine, as long as your receiver has a serial port. Otherwise you have to get creative and create a programmatic babysitter for your receiver. A wireless outlet switch, the Chowmain Ping driver and some programming have probably stopped my wife from insisting that we rip out C4 ... Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.