What happened to WGL Designs? (wgldesigns.com)- the RAIN8 site?

[mcbill20@yahoo.com]

Hello. Last year I was looking at the RAIN8-PC sprinkler controller at
wgldesigns.com. Now that my current sprinkler controller is dead I had
planned on ordering one. However, when I go to wgldesigns.com the site
doesn't appear to be there. Does anyone know if the company is still
around?

Also, assuming they are and that I can get a RAIN8, I have a question.
I noticed a few posts about problems with certain sprinkler solenoids
due to the RAIN8 using a triac and therefore only having 500 milliamps
available. I have a sprinkler system that was put in around 986 I think
so it's definitely not the latest. Any opinions on whether I'll have to
replace all my solenoids if I go with a RAIN8?

Thanks.
Bill

[BruceR]

Maybe it was a temporary problem. http://www.wgldesigns.com/ seems to be
working fine.

From:mcbill20@yahoo.com
mcbill20@yahoo.com

> Hello. Last year I was looking at the RAIN8-PC sprinkler controller at
> wgldesigns.com. Now that my current sprinkler controller is dead I had
> planned on ordering one. However, when I go to wgldesigns.com the site
> doesn't appear to be there. Does anyone know if the company is still
> around?
>
> Also, assuming they are and that I can get a RAIN8, I have a question.
> I noticed a few posts about problems with certain sprinkler solenoids
> due to the RAIN8 using a triac and therefore only having 500 milliamps
> available. I have a sprinkler system that was put in around 986 I
> think so it's definitely not the latest. Any opinions on whether I'll
> have to replace all my solenoids if I go with a RAIN8?
>
> Thanks.
> Bill

[Brian W. Antoine]

On Wed, 25 May 2005 08:41:48 GMT, "BruceR" <brNOSPAM@hawaii.com> wrote:

>Maybe it was a temporary problem. http://www.wgldesigns.com/ seems to be
>working fine.
>
>From:mcbill20@yahoo.com
>mcbill20@yahoo.com
>
>> Hello. Last year I was looking at the RAIN8-PC sprinkler controller at
>> wgldesigns.com. Now that my current sprinkler controller is dead I had
>> planned on ordering one. However, when I go to wgldesigns.com the site
>> doesn't appear to be there. Does anyone know if the company is still
>> around?
>>
>> Also, assuming they are and that I can get a RAIN8, I have a question.
>> I noticed a few posts about problems with certain sprinkler solenoids
>> due to the RAIN8 using a triac and therefore only having 500 milliamps
>> available. I have a sprinkler system that was put in around 986 I
>> think so it's definitely not the latest. Any opinions on whether I'll
>> have to replace all my solenoids if I go with a RAIN8?

Yep, they only handle 500ma roughly and you can also zap them with
static. I've got one channel on mine that I can't use now and my last
email to them about getting the unit RMA'd didn't get a reply.

Probably the only way you're going to tell for sure is to put an
ampmeter inline with the solenoid and actually see what it draws
using your current controller. Test each one, I saw some pretty
good variation from one solenoid to another in my system and they
were all the same brand, installed at the same time.

[mcbill20@yahoo.com]

BruceR wrote:
> Maybe it was a temporary problem. http://www.wgldesigns.com/ seems to be
> working fine.
>
> From:mcbill20@yahoo.com
> mcbill20@yahoo.com
>
> > Hello. Last year I was looking at the RAIN8-PC sprinkler controller at
> > wgldesigns.com. Now that my current sprinkler controller is dead I had
> > planned on ordering one. However, when I go to wgldesigns.com the site
> > doesn't appear to be there. Does anyone know if the company is still
> > around?
> >
> > Also, assuming they are and that I can get a RAIN8, I have a question.
> > I noticed a few posts about problems with certain sprinkler solenoids
> > due to the RAIN8 using a triac and therefore only having 500 milliamps
> > available. I have a sprinkler system that was put in around 986 I
> > think so it's definitely not the latest. Any opinions on whether I'll
> > have to replace all my solenoids if I go with a RAIN8?
> >
> > Thanks.
> > Bill

Thanks. There definitely seems to be a problem with the site though. I
still can't get to it through HTTP. The DNSlookup comes up with
64.17.184.157 but something is hanging along the way. Here's the output
from a traceroute:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\>nslookup
Default Server: a.dcx.mho.net
Address: 64.58.4.2

> www.wgldesigns.com
Server: a.dcx.mho.net
Address: 64.58.4.2

Non-authoritative answer:
Name: www.wgldesigns.com
Address: 64.17.184.157

> exit

C:\>tracert 64.17.184.157

Tracing route to 64.17.184.157 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 62 ms 49 ms 49 ms adsl-64-58-18-254.mho.net
[64.58.18.254]
3 48 ms 49 ms 49 ms gateway-64-58-1-250.mho.net
[64.58.1.250]
4 50 ms 50 ms 52 ms bar3-serial5-1-0.Denver.savvis.net
[208.172.167.
29]
5 51 ms 52 ms 50 ms acr1.Denver.savvis.net [208.172.162.61]
6 82 ms 82 ms 82 ms dcr2-so-4-2-0.LosAngeles.savvis.net
[204.70.193.
86]
7 83 ms 85 ms 83 ms cw-gw.la2ca.ip.att.net [192.205.32.65]
8 85 ms 87 ms 89 ms tbr2-p012101.la2ca.ip.att.net
[12.123.29.6]
9 104 ms 104 ms 103 ms tbr2-cl2.sl9mo.ip.att.net
[12.122.10.13]
10 110 ms 104 ms 103 ms tbr2-cl7.cgcil.ip.att.net
[12.122.10.45]
11 120 ms 110 ms 110 ms gar1-p390.ipsin.ip.att.net
[12.123.210.25]
12 124 ms 122 ms 120 ms 12.118.180.62
13 123 ms 124 ms 125 ms 208.44.62.29
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

[mcbill20@yahoo.com]

Thanks. BTW, would you recommend this controller? If not, does anyone
know of another RS-232 sprinkler that is decent? (I definitely don't
want to use X-10, only serial control).

Thanks.
Bill

[BruceR]

When I click the link the site comes up instantly but a tracert gives
the same timeout result as you got. Go figure.

From:mcbill20@yahoo.com
mcbill20@yahoo.com

> BruceR wrote:
>> Maybe it was a temporary problem. http://www.wgldesigns.com/ seems
>> to be working fine.
>>
>> From:mcbill20@yahoo.com
>> mcbill20@yahoo.com
>>
>>> Hello. Last year I was looking at the RAIN8-PC sprinkler controller
>>> at wgldesigns.com. Now that my current sprinkler controller is dead
>>> I had planned on ordering one. However, when I go to wgldesigns.com
>>> the site doesn't appear to be there. Does anyone know if the
>>> company is still around?
>>>
>>> Also, assuming they are and that I can get a RAIN8, I have a
>>> question. I noticed a few posts about problems with certain
>>> sprinkler solenoids due to the RAIN8 using a triac and therefore
>>> only having 500 milliamps available. I have a sprinkler system that
>>> was put in around 986 I think so it's definitely not the latest.
>>> Any opinions on whether I'll have to replace all my solenoids if I
>>> go with a RAIN8?
>>>
>>> Thanks.
>>> Bill
>
> Thanks. There definitely seems to be a problem with the site though. I
> still can't get to it through HTTP. The DNSlookup comes up with
> 64.17.184.157 but something is hanging along the way. Here's the
> output from a traceroute:
>
> Microsoft Windows XP [Version 5.1.2600]
> (C) Copyright 1985-2001 Microsoft Corp.
>
> C:\>nslookup
> Default Server: a.dcx.mho.net
> Address: 64.58.4.2
>
>> www.wgldesigns.com
> Server: a.dcx.mho.net
> Address: 64.58.4.2
>
> Non-authoritative answer:
> Name: www.wgldesigns.com
> Address: 64.17.184.157
>
>> exit
>
> C:\>tracert 64.17.184.157
>
> Tracing route to 64.17.184.157 over a maximum of 30 hops
>
> 1 <1 ms <1 ms <1 ms 192.168.0.1
> 2 62 ms 49 ms 49 ms adsl-64-58-18-254.mho.net
> [64.58.18.254]
> 3 48 ms 49 ms 49 ms gateway-64-58-1-250.mho.net
> [64.58.1.250]
> 4 50 ms 50 ms 52 ms bar3-serial5-1-0.Denver.savvis.net
> [208.172.167.
> 29]
> 5 51 ms 52 ms 50 ms acr1.Denver.savvis.net [208.172.162.61]
> 6 82 ms 82 ms 82 ms dcr2-so-4-2-0.LosAngeles.savvis.net
> [204.70.193.
> 86]
> 7 83 ms 85 ms 83 ms cw-gw.la2ca.ip.att.net [192.205.32.65]
> 8 85 ms 87 ms 89 ms tbr2-p012101.la2ca.ip.att.net
> [12.123.29.6]
> 9 104 ms 104 ms 103 ms tbr2-cl2.sl9mo.ip.att.net
> [12.122.10.13]
> 10 110 ms 104 ms 103 ms tbr2-cl7.cgcil.ip.att.net
> [12.122.10.45]
> 11 120 ms 110 ms 110 ms gar1-p390.ipsin.ip.att.net
> [12.123.210.25]
> 12 124 ms 122 ms 120 ms 12.118.180.62
> 13 123 ms 124 ms 125 ms 208.44.62.29
> 14 * * * Request timed out.
> 15 * * * Request timed out.
> 16 * * * Request timed out.
> 17 * * * Request timed out.
> 18 * * * Request timed out.
> 19 * * * Request timed out.
> 20 * * * Request timed out.
> 21 * * * Request timed out.
> 22 * * * Request timed out.
> 23 * * * Request timed out.
> 24 * * * Request timed out.
> 25 * * * Request timed out.
> 26 * * * Request timed out.
> 27 * * * Request timed out.
> 28 * * * Request timed out.
> 29 * * * Request timed out.
> 30 * * * Request timed out.
>
> Trace complete.

[wkearney99]

traceroutes depend on ICMP traffic being returned properly. If the upstream
router isn't configured to provide them then traces won't work properly.
There is a 'tpctraceroute' that will use regular TCP packets.

The site comes up fine from here in DC via Speakeasy's DSL network. Which,
BTW, if you're looking for a very competent ISP these are the folks to use.

-Bill Kearney

"BruceR" <brNOSPAM@hawaii.com> wrote in message news:pxble.34247
> When I click the link the site comes up instantly but a tracert gives
> the same timeout result as you got. Go figure.

[L. M. Rappaport]

On Thu, 26 May 2005 03:39:01 GMT, "BruceR" <brNOSPAM@hawaii.com> wrote
(with possible editing):

> When I click the link the site comes up instantly but a tracert gives
>the same timeout result as you got. Go figure.

That probably means there is a cache somewhere. The tracert indicates
a problem at the last site which produced a result (208.44.62.29).
The OP should notify his ISP.
--

Larry
Email to rapp at lmr dot com

>
>From:mcbill20@yahoo.com
>mcbill20@yahoo.com
>
>> BruceR wrote:
>>> Maybe it was a temporary problem. http://www.wgldesigns.com/ seems
>>> to be working fine.
>>>
>>> From:mcbill20@yahoo.com
>>> mcbill20@yahoo.com
>>>
>>>> Hello. Last year I was looking at the RAIN8-PC sprinkler controller
>>>> at wgldesigns.com. Now that my current sprinkler controller is dead
>>>> I had planned on ordering one. However, when I go to wgldesigns.com
>>>> the site doesn't appear to be there. Does anyone know if the
>>>> company is still around?
>>>>
>>>> Also, assuming they are and that I can get a RAIN8, I have a
>>>> question. I noticed a few posts about problems with certain
>>>> sprinkler solenoids due to the RAIN8 using a triac and therefore
>>>> only having 500 milliamps available. I have a sprinkler system that
>>>> was put in around 986 I think so it's definitely not the latest.
>>>> Any opinions on whether I'll have to replace all my solenoids if I
>>>> go with a RAIN8?
>>>>
>>>> Thanks.
>>>> Bill
>>
>> Thanks. There definitely seems to be a problem with the site though. I
>> still can't get to it through HTTP. The DNSlookup comes up with
>> 64.17.184.157 but something is hanging along the way. Here's the
>> output from a traceroute:
>>
>> Microsoft Windows XP [Version 5.1.2600]
>> (C) Copyright 1985-2001 Microsoft Corp.
>>
>> C:\>nslookup
>> Default Server: a.dcx.mho.net
>> Address: 64.58.4.2
>>
>>> www.wgldesigns.com
>> Server: a.dcx.mho.net
>> Address: 64.58.4.2
>>
>> Non-authoritative answer:
>> Name: www.wgldesigns.com
>> Address: 64.17.184.157
>>
>>> exit
>>
>> C:\>tracert 64.17.184.157
>>
>> Tracing route to 64.17.184.157 over a maximum of 30 hops
>>
>> 1 <1 ms <1 ms <1 ms 192.168.0.1
>> 2 62 ms 49 ms 49 ms adsl-64-58-18-254.mho.net
>> [64.58.18.254]
>> 3 48 ms 49 ms 49 ms gateway-64-58-1-250.mho.net
>> [64.58.1.250]
>> 4 50 ms 50 ms 52 ms bar3-serial5-1-0.Denver.savvis.net
>> [208.172.167.
>> 29]
>> 5 51 ms 52 ms 50 ms acr1.Denver.savvis.net [208.172.162.61]
>> 6 82 ms 82 ms 82 ms dcr2-so-4-2-0.LosAngeles.savvis.net
>> [204.70.193.
>> 86]
>> 7 83 ms 85 ms 83 ms cw-gw.la2ca.ip.att.net [192.205.32.65]
>> 8 85 ms 87 ms 89 ms tbr2-p012101.la2ca.ip.att.net
>> [12.123.29.6]
>> 9 104 ms 104 ms 103 ms tbr2-cl2.sl9mo.ip.att.net
>> [12.122.10.13]
>> 10 110 ms 104 ms 103 ms tbr2-cl7.cgcil.ip.att.net
>> [12.122.10.45]
>> 11 120 ms 110 ms 110 ms gar1-p390.ipsin.ip.att.net
>> [12.123.210.25]
>> 12 124 ms 122 ms 120 ms 12.118.180.62
>> 13 123 ms 124 ms 125 ms 208.44.62.29
>> 14 * * * Request timed out.
>> 15 * * * Request timed out.
>> 16 * * * Request timed out.
>> 17 * * * Request timed out.
>> 18 * * * Request timed out.
>> 19 * * * Request timed out.
>> 20 * * * Request timed out.
>> 21 * * * Request timed out.
>> 22 * * * Request timed out.
>> 23 * * * Request timed out.
>> 24 * * * Request timed out.
>> 25 * * * Request timed out.
>> 26 * * * Request timed out.
>> 27 * * * Request timed out.
>> 28 * * * Request timed out.
>> 29 * * * Request timed out.
>> 30 * * * Request timed out.
>>
>> Trace complete.
>