The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Re: xPLRioNet - MVP


  • Subject: Re: xPLRioNet - MVP
  • From: "happy_hammer66" <bill.mcmahon@xxxxxxxxx>
  • Date: Sat, 21 May 2005 12:04:17 -0000

Update:

Took a rio and MVP to the attic, erased all settings in client and dhcp
xml files, loaded an earlier version of xplrionet,MVP started to work.
unplugged it,took it downstairs, same problem. MVP stuck on 2nd/3rd
bar. Whats the difference? well i have two hubs in the attic so it may
be it was going through the two of them to get to the server when
downstairs but maybe only one in the attic. At this point i remembered
an earlier problem with the Rio's not booting when connected to a 100mg
hub and had to be connected to a 10mg hub although i hadn't seen that
problem for a long time. So i inserted a 10mg hub between the MVP
downstairs and the wall socket and sure enough, up it booted.
Its not all joy though, while playing music and watching pictures, it
hung. restarting xplrionet fixed it. Also, problems when getting other
rios to boot, often you'll see "stuck on server", check the
Clients xml
will show its been given the same ip as as another rio or mvp. Still
some progress, will now try to get the later versions of xplrionet
installed to see if that will help the hamging issue. Is 10mg OK for
the MVP of must it be 100mg for music and pictures at the same time?

thx, bill






xPL Links: http://www.xplproject.org.uk http://www.xplhal.com http://www.xpl.myby.co.uk
To Post a Message: ukha_xpl@xxxxxxx
To Subscribe:  ukha_xpl-subscribe@xxxxxxx
To Unsubscribe:  ukha_xpl-unsubscribe@xxxxxxx

xPL Main Index | xPL Thread Index | xPL Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.