When I first got the Siteplayer working, I remember a simple demo that
would show the buttons and let you switch the LEDs on/off.  Now that I
have loaded the Radio demo, I can't find that original sample
anywhere.  Do we have source to that, or was it just something
pre-loaded into the site player?

Thanks!
-Steve

Jack,

You are an angel from heaven. Thank you.

Chris


BTW, if you do decide to provide a dynamic DNS service, please develop the
"IP change-detect-o-tron" to run under linux as well as windows. DNS2go's
runs under windows only. (One can also view an auto-refreshing web page of
theirs to accomplish the same thing, but not very elegant.)

----- Original Message -----
From: "Jack Schoof" <jschoof@...>
To: <siteplayer@egroups.com>
Sent: Friday, December 08, 2000 12:52 PM
Subject: [siteplayer] Re: SitePlayer and Network Setup


> Christopher:
>
> Actually SitePlayer responds to all ports, not just 80.  Just set your
> router to any port of your choosing and it will work.
>
> We are also looking into the possibility of providing a dynamic IP
> service.
>
> Jack
>
>
> --- In siteplayer@egroups.com, "Christopher King"
> <christopherking@c...> wrote:
> > For what it's worth, for anybody having trouble getting SitePlayer
> to work
> > on a simple network:
> >
> > The details in this post are specific to my network, but are
> generally
> > applicable to all small networks, I would imagine.
> >
> > I have RoadRunner (Time Warner) residential service, which assigns
> IPs
> > dynamically when the cable modem resets or is powered on. The cable
> modem
> > acts as a DHCP server for the single network device (computer)
> connected to
> > it.
> >
> > If more than one computer (or network device, ie SitePlayer) uses
> this
> > network connection, then a router must be used (hardware or
> software) and
> > all network devices must have static IPs assigned to them within a
> range of
> > IP addresses reserved for private, internal networks. Two that I
> know of are
> > 10.2.8.X and 192.168.0.X. (Any network gurus out there could weigh
> in on
> > this matter.) So my main development computer might be 10.2.8.1, my
> linux
> > box is 10.2.8.2, and my siteplayer might be 10.2.8.3. If I had
> chosen the
> > 192 scheme, then I would have left my SitePlayer as 192.168.1.250.
> >
> > I have not used a hub to connect multiple computers to the cable
> modem. I do
> > not see how traffic would be routed properly to the appropriate
> network
> > device. (Maybe it would, but I don't see how.) Since my limited
> experience
> > tells me that cable modems (or DSL adapters, for that matter) are
> not
> > capable of Network Address Translation, it seems that one must use
> a router.
> > I use a LinkSys 4-port EtherFast router. (And by the way, for those
> of you
> > out there using this router, please be advised that the "loopback"
> function
> > does not work properly in firmware versions above 1.30. Current
> shipping
> > version is at least this.) What does this mean? That means that you
> won't be
> > able to access other devices on your network EXCEPT FROM THE WAN.
> (Whoospie
> > daisy.) I had to download v1.22 from the Linksys site to make it
> work
> > properly.  Since then, I have had no problem accessing either the
> Linux box
> > or the SitePlayer from my main development computer. All I have to
> do is
> > open location 192.168.1.250 (or whatever I configured the
> SitePlayer as) in
> > the browser (any browser) and get the SitePlayer's index page.
> >
> > For Linksys router users: You will also have to set the "port
> forwarding" of
> > port 80 to the static IP of your SitePlayer. (And of course, this
> asumes
> > that you have assigned static IPs to all your network devices, and
> have
> > disabled the DHCP function of the router.)
> >
> > The one thing I haven't been able to do yet is this:
> >
> > *****************************Wish List to SitePlayer people:
> > ******************************
> >
> > The router forwards all incoming requests on port 80 to the linux
> box.
> > SitePlayer's configuration to serve its pages on only port 80 does
> not allow
> > me to have both the main web server and SitePlayer accessible from
> the WAN.
> >
> > It would be nice if I could configure SitePlayer to serve pages on
> some
> > other port of my choosing, so that I could forward those ports to
> > SitePlayer. Thus, I could access my SitePlayer from the Wan like
> this:
> > mydomain.com:88 and get the SitePlayer.
> >
> > I know that the device is designed for industrial applications, but
> even in
> > an industrial setting I could see that this flexibility would be
> valuable.
> >
> > Chris King
> >
> > PS: How do I maintain a domain name with a dynamic IP? I use
> dns2go.com
> > which, for a reasonable fee, updates their DNS servers with your
> current IP.
> > (Hey, yeah I want to make a million dollars. But I don't have it
> yet. Gotta
> > economize. Static IPs are expensive, ya know?)
>
>
>
> To unsubscribe from this group, send an email to:
> siteplayer-unsubscribe@egroups.com
>
>
>

Andy-

Although the SitePlayer contains a processor, it is really just a peripheral
chip. In most cases, you need a separate controller running things, and it
communicates with the SitePlayer across the serial interface, using object
packets. So your controller decides it wants to put a character string up on
the web page interface, and sends the necessary object packet to the
SitePlayer (via serial). This character string is now available to any web
browser with access to the SitePlayer. If the contents of the string object
are changed from the browser (as determined by polling or by using the
interrupt provided for object change notification), the controller can read
the object back across the serial port.

It is a bit confusing. It would have been nice if NetMedia had provided a
few more samples.

Chris

----- Original Message -----
From: <arm@...>
To: <siteplayer@egroups.com>
Sent: Friday, December 08, 2000 12:22 PM
Subject: [siteplayer] Re: Serial Port Communications


> --- In siteplayer@egroups.com, "Chris Peterson" <clp@a...> wrote:
> > If I understand correctly, you need to define a 16 byte object and
> reference
> > it in your webpage.
>
> Been there, done that.
>
> > To update the object from the serial port, you
> send an
> > object packet: Write or WriteX command followed by the object
> address and
> > its data.
>
> Who sends a write request to where???  Does the browser
> send the write request to the SitePlayer?  For example,
> do you put the Write command into a Form?  Can you
> hum a few bars (show an example)?
>
> >In other words, the data stream to the serial port needs
> to be
> > slightly more complex than just the 16 characters. I hope I'm
> correct,
> > because I'm setting up to do it this way.
>
> Do you suggest that the write request comes in through
> the serial port?  That does not make sense to me.
>
> Obviously I'm confused.
>
> -- andy

--- In siteplayer@egroups.com, "Chris Peterson" <clp@a...> wrote:
> If I understand correctly, you need to define a 16 byte object and
reference
> it in your webpage.

Been there, done that.

> To update the object from the serial port, you
send an
> object packet: Write or WriteX command followed by the object
address and
> its data.

Who sends a write request to where???  Does the browser
send the write request to the SitePlayer?  For example,
do you put the Write command into a Form?  Can you
hum a few bars (show an example)?

>In other words, the data stream to the serial port needs
to be
> slightly more complex than just the 16 characters. I hope I'm
correct,
> because I'm setting up to do it this way.

Do you suggest that the write request comes in through
the serial port?  That does not make sense to me.

Obviously I'm confused.

-- andy



>
> Chris Peterson
>
>
> ----- Original Message -----
> From: <arm@h...>
> To: <siteplayer@egroups.com>
> Sent: Friday, December 08, 2000 11:07 AM
> Subject: [siteplayer] Serial Port Communications
>
>
> > Has anyone got the serial port communications to work?
> > I don't mean the Serial Tester. I mean has anyone
> > programmed an Object Packet? For the life if me,
> > I cannot figure out where to put the command byte.
> > In the HTML?  In the Definition file?  An example
> > would be very helpful.  I want to begin by programming
> > the SitePlayer to update a web page with a 16-byte
> > ASCII text message, each time the message arrives
> > at the serial port.

If I understand correctly, you need to define a 16 byte object and reference
it in your webpage. To update the object from the serial port, you send an
object packet: Write or WriteX command followed by the object address and
its data. In other words, the data stream to the serial port needs to be
slightly more complex than just the 16 characters. I hope I'm correct,
because I'm setting up to do it this way.

Chris Peterson


----- Original Message -----
From: <arm@...>
To: <siteplayer@egroups.com>
Sent: Friday, December 08, 2000 11:07 AM
Subject: [siteplayer] Serial Port Communications


> Has anyone got the serial port communications to work?
> I don't mean the Serial Tester. I mean has anyone
> programmed an Object Packet? For the life if me,
> I cannot figure out where to put the command byte.
> In the HTML?  In the Definition file?  An example
> would be very helpful.  I want to begin by programming
> the SitePlayer to update a web page with a 16-byte
> ASCII text message, each time the message arrives
> at the serial port.

For Netscape users we say:

If the above display does not seem to update, try your
"reload" button. If that helps, follow these directions
to automate the update process.

Choose: Edit/Preferences/Advanced/Cache
Click on "Every time"


Another option is to write a Java applet that fetches
the data and updates the browser display within the
applet.



==========================================================

--- In siteplayer@egroups.com, "Russ " <russ377@y...> wrote:
> Hi,
>
> I'm curious to know how others have approached the problem of
needing
> to assure the latest data from the SitePlayer module is being
> displayed in the browser.
>
> So far, I've been playing around with META tags like:
>
> <META HTTP-EQUIV="pragma" CONTENT="no-cache">
> <META HTTP-EQUIV="expires" CONTENT="0">
> <META HTTP-EQUIV="refresh" CONTENT="30">
>
> These tags are supposed to tell browser caches to always get a fresh
> copy of the page ( every 30 secs in the above example ) but from
what
> I have read, there are no guarantees the request will be honored by
> either the client browser or any other caching systems that may be
> between the user and the SitePlayer module.
>
> Aside from these tags, does anyone have another suggestion or
> possibly a few comments on how to address this issue?
>
> Thanks in advance for your help!
>
>
> Best Regards,
>
> Russ O'Rourke

Has anyone got the serial port communications to work?
I don't mean the Serial Tester. I mean has anyone
programmed an Object Packet? For the life if me,
I cannot figure out where to put the command byte.
In the HTML?  In the Definition file?  An example
would be very helpful.  I want to begin by programming
the SitePlayer to update a web page with a 16-byte
ASCII text message, each time the message arrives
at the serial port.

Christopher:

Actually SitePlayer responds to all ports, not just 80.  Just set your
router to any port of your choosing and it will work.

We are also looking into the possibility of providing a dynamic IP
service.

Jack


--- In siteplayer@egroups.com, "Christopher King"
<christopherking@c...> wrote:
> For what it's worth, for anybody having trouble getting SitePlayer
to work
> on a simple network:
>
> The details in this post are specific to my network, but are
generally
> applicable to all small networks, I would imagine.
>
> I have RoadRunner (Time Warner) residential service, which assigns
IPs
> dynamically when the cable modem resets or is powered on. The cable
modem
> acts as a DHCP server for the single network device (computer)
connected to
> it.
>
> If more than one computer (or network device, ie SitePlayer) uses
this
> network connection, then a router must be used (hardware or
software) and
> all network devices must have static IPs assigned to them within a
range of
> IP addresses reserved for private, internal networks. Two that I
know of are
> 10.2.8.X and 192.168.0.X. (Any network gurus out there could weigh
in on
> this matter.) So my main development computer might be 10.2.8.1, my
linux
> box is 10.2.8.2, and my siteplayer might be 10.2.8.3. If I had
chosen the
> 192 scheme, then I would have left my SitePlayer as 192.168.1.250.
>
> I have not used a hub to connect multiple computers to the cable
modem. I do
> not see how traffic would be routed properly to the appropriate
network
> device. (Maybe it would, but I don't see how.) Since my limited
experience
> tells me that cable modems (or DSL adapters, for that matter) are
not
> capable of Network Address Translation, it seems that one must use
a router.
> I use a LinkSys 4-port EtherFast router. (And by the way, for those
of you
> out there using this router, please be advised that the "loopback"
function
> does not work properly in firmware versions above 1.30. Current
shipping
> version is at least this.) What does this mean? That means that you
won't be
> able to access other devices on your network EXCEPT FROM THE WAN.
(Whoospie
> daisy.) I had to download v1.22 from the Linksys site to make it
work
> properly.  Since then, I have had no problem accessing either the
Linux box
> or the SitePlayer from my main development computer. All I have to
do is
> open location 192.168.1.250 (or whatever I configured the
SitePlayer as) in
> the browser (any browser) and get the SitePlayer's index page.
>
> For Linksys router users: You will also have to set the "port
forwarding" of
> port 80 to the static IP of your SitePlayer. (And of course, this
asumes
> that you have assigned static IPs to all your network devices, and
have
> disabled the DHCP function of the router.)
>
> The one thing I haven't been able to do yet is this:
>
> *****************************Wish List to SitePlayer people:
> ******************************
>
> The router forwards all incoming requests on port 80 to the linux
box.
> SitePlayer's configuration to serve its pages on only port 80 does
not allow
> me to have both the main web server and SitePlayer accessible from
the WAN.
>
> It would be nice if I could configure SitePlayer to serve pages on
some
> other port of my choosing, so that I could forward those ports to
> SitePlayer. Thus, I could access my SitePlayer from the Wan like
this:
> mydomain.com:88 and get the SitePlayer.
>
> I know that the device is designed for industrial applications, but
even in
> an industrial setting I could see that this flexibility would be
valuable.
>
> Chris King
>
> PS: How do I maintain a domain name with a dynamic IP? I use
dns2go.com
> which, for a reasonable fee, updates their DNS servers with your
current IP.
> (Hey, yeah I want to make a million dollars. But I don't have it
yet. Gotta
> economize. Static IPs are expensive, ya know?)

DHCP in some circumstances would ask too many times for an address.
Also on some routers it would not get one at all.  Should be
completely fixed with this new release.  It has now been tested in
house with Linsys DSL/Cable Modem router, UMAX Plus Router, NT4 as a
DHCP server, Linux as a DHCP server, various shareware DHCP servers.

Also some browsers/tcp/ip stacks would not always work correctly
(SitePlayer's fault).  So we were able to get traces from some
customers and found the problem.

Happy Upgrading!

Jack

--- In siteplayer@egroups.com, segroups@t... wrote:
> -=> On Thu, 7 Dec 2000 18:23:25 -0700 , David Holcomb
<dholcomb@n...> said:
>
> > SitePlayer Firmware Update v1.3
>
> Excellent!  I look forward to installing this.
>
> > **DO NOT TOUCH SITEPLAYER FOR 15 SECONDS AFTER FIRMWARE DOWNLOAD
IS
> > COMPLETE**
>
> Important safety tip. :)
>
> > SitePlayer Firmware Update History
> > v1.3
> > · Fixes for web page loading under some browsers or network
circumstances
> > · Fixes concerning DHCP
>
> Can you please elaborate a little on these points?  What changes
were
> made to the DHCP behavior?
>
> Thanks,
> -Steve

Siteplayer now works, but the receiver export file (receiver_export.htm)
transfer seems to hang after some data has been sent.  Is this still an
issue with the firmware or is it now something with my network.  I would
expect all pages to load extremely quickly since there is no network
activity here at this time.  Anyone also have the same problem?  By the way,
what is siteplayer's maximum response time (latency)?  Is there is a
specification for it?

Frank Herschell

> -----Original Message-----
> From: dholcomb@... [mailto:dholcomb@...]
> Sent: Thursday, December 07, 2000 11:32 PM
> To: siteplayer@egroups.com
> Subject: [siteplayer] Firmware Direct Link
>
>
> Until the link on the download page is fixed, you can get the
> firmware upgrade at
> http://www.siteplayer.com/docs/siteplayerfirmwarev13.zip
>
> David
> NetMedia
>
>
>
> To unsubscribe from this group, send an email to:
> siteplayer-unsubscribe@egroups.com
>
>
>

Until the link on the download page is fixed, you can get the
firmware upgrade at
http://www.siteplayer.com/docs/siteplayerfirmwarev13.zip

David
NetMedia

For what it's worth, for anybody having trouble getting SitePlayer to work
on a simple network:

The details in this post are specific to my network, but are generally
applicable to all small networks, I would imagine.

I have RoadRunner (Time Warner) residential service, which assigns IPs
dynamically when the cable modem resets or is powered on. The cable modem
acts as a DHCP server for the single network device (computer) connected to
it.

If more than one computer (or network device, ie SitePlayer) uses this
network connection, then a router must be used (hardware or software) and
all network devices must have static IPs assigned to them within a range of
IP addresses reserved for private, internal networks. Two that I know of are
10.2.8.X and 192.168.0.X. (Any network gurus out there could weigh in on
this matter.) So my main development computer might be 10.2.8.1, my linux
box is 10.2.8.2, and my siteplayer might be 10.2.8.3. If I had chosen the
192 scheme, then I would have left my SitePlayer as 192.168.1.250.

I have not used a hub to connect multiple computers to the cable modem. I do
not see how traffic would be routed properly to the appropriate network
device. (Maybe it would, but I don't see how.) Since my limited experience
tells me that cable modems (or DSL adapters, for that matter) are not
capable of Network Address Translation, it seems that one must use a router.
I use a LinkSys 4-port EtherFast router. (And by the way, for those of you
out there using this router, please be advised that the "loopback" function
does not work properly in firmware versions above 1.30. Current shipping
version is at least this.) What does this mean? That means that you won't be
able to access other devices on your network EXCEPT FROM THE WAN. (Whoospie
daisy.) I had to download v1.22 from the Linksys site to make it work
properly.  Since then, I have had no problem accessing either the Linux box
or the SitePlayer from my main development computer. All I have to do is
open location 192.168.1.250 (or whatever I configured the SitePlayer as) in
the browser (any browser) and get the SitePlayer's index page.

For Linksys router users: You will also have to set the "port forwarding" of
port 80 to the static IP of your SitePlayer. (And of course, this asumes
that you have assigned static IPs to all your network devices, and have
disabled the DHCP function of the router.)

The one thing I haven't been able to do yet is this:

*****************************Wish List to SitePlayer people:
******************************

The router forwards all incoming requests on port 80 to the linux box.
SitePlayer's configuration to serve its pages on only port 80 does not allow
me to have both the main web server and SitePlayer accessible from the WAN.

It would be nice if I could configure SitePlayer to serve pages on some
other port of my choosing, so that I could forward those ports to
SitePlayer. Thus, I could access my SitePlayer from the Wan like this:
mydomain.com:88 and get the SitePlayer.

I know that the device is designed for industrial applications, but even in
an industrial setting I could see that this flexibility would be valuable.

Chris King

PS: How do I maintain a domain name with a dynamic IP? I use dns2go.com
which, for a reasonable fee, updates their DNS servers with your current IP.
(Hey, yeah I want to make a million dollars. But I don't have it yet. Gotta
economize. Static IPs are expensive, ya know?)

-=> On Thu, 7 Dec 2000 18:23:25 -0700 , David Holcomb <dholcomb@...>
said:

> SitePlayer Firmware Update v1.3

Excellent!  I look forward to installing this.

> **DO NOT TOUCH SITEPLAYER FOR 15 SECONDS AFTER FIRMWARE DOWNLOAD IS
> COMPLETE**

Important safety tip. :)

> SitePlayer Firmware Update History
> v1.3
> · Fixes for web page loading under some browsers or network circumstances
> · Fixes concerning DHCP

Can you please elaborate a little on these points?  What changes were
made to the DHCP behavior?

Thanks,
-Steve

Hi,

As mentioned before, I've been using the static IP mode with an
address of 192.168.100.200 quite successfully.  That's not to say it
was without some early troubles.  After using Serial Tester utility
to modify the default factory IP address on the module, I noticed
that the new address was only good as long as the SitePlayer had not
been reset or power cycled.  As soon as either of those events
happened, the unit reverted back to the factory loaded default.  What
solved the problem was to change the IP and DCHP settings ($DHCP
off / $InitialIP "192.168.100.200") in the rcvr.spd file, recompile
and download via the SiteLinker program.  After that, the IP settings
stayed put and it's been running fine ever since.

SitePlayer Firmware Update v1.3

You must be able to communicate with SitePlayer using SiteLinker in order to
use the update. Test SiteLinker's communication by loading the RCVR.SPB file
into SitePlayer with Download SitePlayer F4 command. If you cannot find
SitePlayer with SiteLinker, use the Serial Tester program to Get or Set
SitePlayer's IP address. Make sure your Password and IP address are set
properly under SiteLinker's Configure menu.

**DO NOT TOUCH SITEPLAYER FOR 15 SECONDS AFTER FIRMWARE DOWNLOAD IS
COMPLETE**
Power must not be interupted! Do not press the reset button during this
period!

1. Download and Unzip Update ( http://www.siteplayer.com/downloads.htm )
2. Start SiteLinker program
3. Load Firmware Update with File, Open menu
4. Update SitePlayer with Download SitePlayer F4 command
5. DO NOT TOUCH SITEPLAYER FOR 15 SECONDS AFTER DOWNLOAD IS COMPLETE
6. Reload web pages with SiteLinker after the 15 seconds have passed

SitePlayer Firmware Update History
v1.3
· Fixes for web page loading under some browsers or network circumstances
· Fixes concerning DHCP

David Holcomb
dholcomb@...

-=> On Thu, 7 Dec 2000 18:22:04 -0600, "John Corstvet" <john@...> said:

> Frank,
> Mine worked perfectly the first and every time I've tried it.  I set it up
> using DHCP served from a 3Com Internet Firewall 25.

I first tried to use mine with a static (fixed) IP number, but didn't
have any luck, so I tried DHCP soon after.  It worked fine with DHCP,
and has been taking connections for the last several days.  I never
went back to static IP addressing, so I don't know if it was something
simple.

I'm running Linux with the DHCP v2 beta 1 server serving the siteplayer.

Strangely, the siteplayer issues a DHCPDISCOVER & DHCPREQUEST every
hour or so, sometimes more often.  There were 25 requests yesterday.
Very irregular.  Anyone know why?  None of my other DHCP clients do this.
I'm wondering if the siteplayer is somehow rebooting, since it
shouldn't need to do a DISCOVER more than once.

-Steve

Dec  7 00:36:48 mango dhcpd: DHCPDISCOVER from 00:03:75:00:04:6a via eth0
Dec  7 02:18:16 mango dhcpd: DHCPDISCOVER from 00:03:75:00:04:6a via eth0
Dec  7 02:19:11 mango dhcpd: DHCPDISCOVER from 00:03:75:00:04:6a via eth0
Dec  7 04:00:39 mango dhcpd: DHCPDISCOVER from 00:03:75:00:04:6a via eth0
Dec  7 05:42:06 mango dhcpd: DHCPDISCOVER from 00:03:75:00:04:6a via eth0
Dec  7 05:43:02 mango dhcpd: DHCPDISCOVER from 00:03:75:00:04:6a via eth0
Dec  7 07:24:29 mango dhcpd: DHCPDISCOVER from 00:03:75:00:04:6a via eth0
Dec  7 09:05:56 mango dhcpd: DHCPDISCOVER from 00:03:75:00:04:6a via eth0
Dec  7 10:47:24 mango dhcpd: DHCPDISCOVER from 00:03:75:00:04:6a via eth0
Dec  7 10:48:19 mango dhcpd: DHCPDISCOVER from 00:03:75:00:04:6a via eth0
Dec  7 12:29:47 mango dhcpd: DHCPDISCOVER from 00:03:75:00:04:6a via eth0
Dec  7 14:11:14 mango dhcpd: DHCPDISCOVER from 00:03:75:00:04:6a via eth0
Dec  7 15:52:41 mango dhcpd: DHCPDISCOVER from 00:03:75:00:04:6a via eth0

Frank,
Mine worked perfectly the first and every time I've tried it.  I set it up
using DHCP served from a 3Com Internet Firewall 25.  I looked in the
firewall to find the IP address it was issued was 10.0.1.6.  I connected
using Microsoft Internet Explorer 5.5 to http://10.0.1.6 and was able to
exercise the red and green LEDs and read the two pushbuttons.  I've had
about 15 minutes to play with it since I received it last week.  I've been
out of town since then.
John Corstvet

-----Original Message-----
From: Frank Herschell [mailto:frankh@...]
Sent: Thursday, December 07, 2000 18:04
To: siteplayer@egroups.com
Subject: RE: [siteplayer] Connection problem

Hi,

I also have problems connecting to the siteplayer development board.  Here
is what I did:

My company's intranet uses static IP addresses and there is a cubicle next
to me that has the IP address labeled on the computer (192.168.200.221).  I
took the Ethernet cable from that computer and plugged it into siteplayer.
I used the serial tester application to reconfigure siteplayer to match the
IP address of that next cubicle.  I then pinged that address from my
computer with success (four replies with less than 10nS response time).  If
I pinged siteplayer and received 2 replies, and then quickly disconnected
the Ethernet cable from siteplayer, the remaining two pings failed.  This
was my test of success in communication.

Then I tried to connect to siteplayer using ie5 (http://192.168.200.221/)
(with "Use a proxy server" turned off) and could not connect.  I tried
Netscape and Opera browsers and found the same result of no connection.  I
then did a port scan (on the siteplayer IP address) and found that no ports
were listening - in particular, port 80 was not responding.  I thought maybe
the siteplayer I received did not have the web pages flashed into it, so I
reloaded it using Sitelinker, reconfigured the IP address, with no success.
I took siteplayer home and tried it on my own internal network and had the
same no connection problem (although ping did always work as above).  I also
tried using different IP address without success.  Am I missing something,
or is everyone having similar problems?  By the way I'm running NT4 SP6 at
work with switches on the network, and both NT5 and win98 at home with a hub
on the network.

Thanks for any help in advance.

Frank Herschell

> -----Original Message-----
> From: David Holcomb [mailto:dholcomb@...]
> Sent: Thursday, December 07, 2000 4:47 PM
> To: 'siteplayer@egroups.com'
> Subject: RE: [siteplayer] Connection problem
>
>
> Ray Barnett,
> The problem you are experiencing could be the result of a bug we've found.
> We hope to have a firmware update posted by this evening 12/7/00 at
> http://www.siteplayer.com/downloads.htm .
>
> David Holcomb
> dholcomb@...
>
> > ----------
> > From:       Ray Barnett[SMTP:Barnett_Ray@...]
> > Reply To:   siteplayer@egroups.com
> > Sent:       Thursday, December 07, 2000 1:33 PM
> > To:         siteplayer@egroups.com
> > Subject:    [siteplayer] Connection problem
> >
> > Hi,
> >
> > I received by SitePlayer development board this morning which was
> > great! However, although I can connect to it over TCP/IP to download
> > sites to it (the demo receiver one and one I've developed), I seem
> > unable to contact it using Internet Explorer.
> >
> > I've assigned it a TCP/IP address manually, and switched off DHCP. I
> > can ping the assigned address. I can download sites to the IP
> > address - network lights come on and no errors reported. So I'm
> > convinced I have a working TCP/IP connection and working SitePlayer
> > module. However, attempts to browse pages from it result in "The page
> > cannot be displayed" error, which occurs after 30s or so.
> >
> > I've tried specifying the specific url (e.g.
> > http://10.0.0.20/index.htm) but still no luck.
> >
> > Any advice, suggestions or help would be much appreciated.
> >
> > Ray Barnett.
> >
> >
> >
> > To unsubscribe from this group, send an email to:
> > siteplayer-unsubscribe@egroups.com
> >
> >
> >
>
>
> To unsubscribe from this group, send an email to:
> siteplayer-unsubscribe@egroups.com
>
>
>



To unsubscribe from this group, send an email to:
siteplayer-unsubscribe@egroups.com

Hi,

I also have problems connecting to the siteplayer development board.  Here
is what I did:

My company's intranet uses static IP addresses and there is a cubicle next
to me that has the IP address labeled on the computer (192.168.200.221).  I
took the Ethernet cable from that computer and plugged it into siteplayer.
I used the serial tester application to reconfigure siteplayer to match the
IP address of that next cubicle.  I then pinged that address from my
computer with success (four replies with less than 10nS response time).  If
I pinged siteplayer and received 2 replies, and then quickly disconnected
the Ethernet cable from siteplayer, the remaining two pings failed.  This
was my test of success in communication.

Then I tried to connect to siteplayer using ie5 (http://192.168.200.221/)
(with "Use a proxy server" turned off) and could not connect.  I tried
Netscape and Opera browsers and found the same result of no connection.  I
then did a port scan (on the siteplayer IP address) and found that no ports
were listening - in particular, port 80 was not responding.  I thought maybe
the siteplayer I received did not have the web pages flashed into it, so I
reloaded it using Sitelinker, reconfigured the IP address, with no success.
I took siteplayer home and tried it on my own internal network and had the
same no connection problem (although ping did always work as above).  I also
tried using different IP address without success.  Am I missing something,
or is everyone having similar problems?  By the way I'm running NT4 SP6 at
work with switches on the network, and both NT5 and win98 at home with a hub
on the network.

Thanks for any help in advance.

Frank Herschell

> -----Original Message-----
> From: David Holcomb [mailto:dholcomb@...]
> Sent: Thursday, December 07, 2000 4:47 PM
> To: 'siteplayer@egroups.com'
> Subject: RE: [siteplayer] Connection problem
>
>
> Ray Barnett,
> The problem you are experiencing could be the result of a bug we've found.
> We hope to have a firmware update posted by this evening 12/7/00 at
> http://www.siteplayer.com/downloads.htm .
>
> David Holcomb
> dholcomb@...
>
> > ----------
> > From:  Ray Barnett[SMTP:Barnett_Ray@...]
> > Reply To:  siteplayer@egroups.com
> > Sent:  Thursday, December 07, 2000 1:33 PM
> > To:  siteplayer@egroups.com
> > Subject:  [siteplayer] Connection problem
> >
> > Hi,
> >
> > I received by SitePlayer development board this morning which was
> > great! However, although I can connect to it over TCP/IP to download
> > sites to it (the demo receiver one and one I've developed), I seem
> > unable to contact it using Internet Explorer.
> >
> > I've assigned it a TCP/IP address manually, and switched off DHCP. I
> > can ping the assigned address. I can download sites to the IP
> > address - network lights come on and no errors reported. So I'm
> > convinced I have a working TCP/IP connection and working SitePlayer
> > module. However, attempts to browse pages from it result in "The page
> > cannot be displayed" error, which occurs after 30s or so.
> >
> > I've tried specifying the specific url (e.g.
> > http://10.0.0.20/index.htm) but still no luck.
> >
> > Any advice, suggestions or help would be much appreciated.
> >
> > Ray Barnett.
> >
> >
> >
> > To unsubscribe from this group, send an email to:
> > siteplayer-unsubscribe@egroups.com
> >
> >
> >
>
>
> To unsubscribe from this group, send an email to:
> siteplayer-unsubscribe@egroups.com
>
>
>

I've narrowed down my problem, but not fully resolved it:

Using another PC, I was initially getting an error message back from
my web proxy, so clearly for whatever reason, despite having "bypass
proxy server for local addresses" checked, it wasn't. Adding the
SitePlayer's IP address to the list of local exclusions fixed access
for the other PC - so I now have one PC accessing Siteplayer!

However, my original PC (which also happens to be the web proxy),
still will not connect, despite adding the SitePlayer IP address to
the list of "do not use proxy server with addresses beginning". No
error message is returned by the proxy, and I can see from the LAN
lights that the PC and SitePlayer have a brief conversation when I
request a page, before giving up.

So, I'd be happy to admit it's a problem with my setup, except that I
can happily connect to other IIS web servers on my local LAN, just
not SitePlayer. Any clues?

Ray Barnett.

Hi Kevin,

I don't know if your cable modem is using DHCP, but as I understand
it, most cable systems use a static IP address.  A quick way to check
( if you are using Windows ) is to open the control panel, then click
on the Network icon.  Select TCP/IP->yournetworkadaptorname from the
list and then press the button marked Properties.  Here, you can look
on the IP Address tab.  If you have "Obtain an IP address
automatically" selected, you are using DHCP and something on your
system is providing the address, either the cable company or perhaps
your cable modem.

Another thing to be aware of is that it's likely your cable modem box
is using NAT ( Network Address Translation ) to take the single
static IP address the cable company gives you and mapping it to a
range of private IP addresses.  If you see a private IP address
listed in the network settings for your computer ( the spaces
under "Specify an IP address" are filled in ) then you have the
freedom to assign your own private IP address to your SitePlayer
module.

If you are interested, you can read about private IP addressing at
http://www.eclipse.net/~amw/tutorial/private.shtml and more about IP
networks at
http://ourworld.compuserve.com/homepages/j_helmig/tcpip.htm

Hope this helps!


Regards,

Russ O'Rourke

Hi,

I'm curious to know how others have approached the problem of needing
to assure the latest data from the SitePlayer module is being
displayed in the browser.

So far, I've been playing around with META tags like:

<META HTTP-EQUIV="pragma" CONTENT="no-cache">
<META HTTP-EQUIV="expires" CONTENT="0">
<META HTTP-EQUIV="refresh" CONTENT="30">

These tags are supposed to tell browser caches to always get a fresh
copy of the page ( every 30 secs in the above example ) but from what
I have read, there are no guarantees the request will be honored by
either the client browser or any other caching systems that may be
between the user and the SitePlayer module.

Aside from these tags, does anyone have another suggestion or
possibly a few comments on how to address this issue?

Thanks in advance for your help!


Best Regards,

Russ O'Rourke

Hi,

I recieved my siteplayer about a week ago and still cannot get a
network connection.  I am on a cable modem and am using a Linksys 5
port 10/100( I think) hub.  I do not know if DHCP is being used and
Cablevision will not give any information out about there system.

Can anybody help?

Thanks
Kevin McCusker

Ray Barnett,
The problem you are experiencing could be the result of a bug we've found.
We hope to have a firmware update posted by this evening 12/7/00 at
http://www.siteplayer.com/downloads.htm .

David Holcomb
dholcomb@...

> ----------
> From:  Ray Barnett[SMTP:Barnett_Ray@...]
> Reply To:  siteplayer@egroups.com
> Sent:  Thursday, December 07, 2000 1:33 PM
> To:  siteplayer@egroups.com
> Subject:  [siteplayer] Connection problem
>
> Hi,
>
> I received by SitePlayer development board this morning which was
> great! However, although I can connect to it over TCP/IP to download
> sites to it (the demo receiver one and one I've developed), I seem
> unable to contact it using Internet Explorer.
>
> I've assigned it a TCP/IP address manually, and switched off DHCP. I
> can ping the assigned address. I can download sites to the IP
> address - network lights come on and no errors reported. So I'm
> convinced I have a working TCP/IP connection and working SitePlayer
> module. However, attempts to browse pages from it result in "The page
> cannot be displayed" error, which occurs after 30s or so.
>
> I've tried specifying the specific url (e.g.
> http://10.0.0.20/index.htm) but still no luck.
>
> Any advice, suggestions or help would be much appreciated.
>
> Ray Barnett.
>
>
>
> To unsubscribe from this group, send an email to:
> siteplayer-unsubscribe@egroups.com
>
>
>

Hi Ray,

I've been playing with my new module too...  I've been testing with
IE 5.50.4134 on several computers with no problems so far.  Like you,
I also have a static IP and DHCP disabled.

You are probably do have a good network connection back to the
module, but the sure-fire way to know if it is really being pinged is
to disconnect the network cable while pinging the address.  If you
see the address stop and start responding as you unplug and plug the
cable into the connector, you can truly be sure you are talking.

The only easy suggestion I can think of is to ask if you have the
SitePlayerPC running.  It's possible the SitePlayerPC server is
causing interference.

Hope this helps!

Regards,

Russ O'Rourke

Hi,

I received by SitePlayer development board this morning which was
great! However, although I can connect to it over TCP/IP to download
sites to it (the demo receiver one and one I've developed), I seem
unable to contact it using Internet Explorer.

I've assigned it a TCP/IP address manually, and switched off DHCP. I
can ping the assigned address. I can download sites to the IP
address - network lights come on and no errors reported. So I'm
convinced I have a working TCP/IP connection and working SitePlayer
module. However, attempts to browse pages from it result in "The page
cannot be displayed" error, which occurs after 30s or so.

I've tried specifying the specific url (e.g.
http://10.0.0.20/index.htm) but still no luck.

Any advice, suggestions or help would be much appreciated.

Ray Barnett.

Siteplayer is truly a marvelous device. I have already done some neat
stuff with it!

I would like a couple of things to be different in SitePlayerPC:

1) It has a demo timeout (at least the downloaded one does). It would
be nice if that went away.

2) It would be nice if one could specify which IP port it listens on.
When I run it on my main development machine, I have to stop the web
server that normally runs on port 80 there.

With version 1.0 build #50 SiteLinkPC works with a Danish version of
Windows2000.

/jens ancker

-----Oprindelig meddelelse-----
Fra: Jens Vincent Ancker [mailto:ja@...]
Sendt: 22. november 2000 08:18
Til: siteplayer@egroups.com
Emne: SV: [siteplayer] SiteLinkPC does not work under chinese version
windows


Hi all:

maybe I have the same problem. I can't get siteplayer to work under a Danish
version of either Windows 98 or 2000. I haven't tried to use an English
version. When I upload the SPB file I get an runtime error 5.

Best regards

Jens Ancker
Eltronic A/S
DK-8722 Hedensted

-----Oprindelig meddelelse-----
Fra: pwang@... [mailto:pwang@...]
Sendt: 21. november 2000 17:48
Til: siteplayer@egroups.com
Emne: [siteplayer] SiteLinkPC does not work under chinese version
windows



Hi all:
    after several hours hard working, I found that the sitelink or
sitelinkPC does not work under chinese version of Windows
98/NT/2000/ME. When I use a english windows ME, the problem solved. I
don't know why? and I hope someone in netmedia can fix the problem
soon.
by the way, BasicX has the same problem. program can't be downloaded
into BX-24 when I used a chinese windows.

Eric Wang
pwang@...
National central University
Dept. of Environmental Engineering
Taiwan



To unsubscribe from this group, send an email to:
siteplayer-unsubscribe@egroups.com






To unsubscribe from this group, send an email to:
siteplayer-unsubscribe@egroups.com

Hi all:

maybe I have the same problem. I can't get siteplayer to work under a Danish
version of either Windows 98 or 2000. I haven't tried to use an English
version. When I upload the SPB file I get an runtime error 5.

Best regards

Jens Ancker
Eltronic A/S
DK-8722 Hedensted

-----Oprindelig meddelelse-----
Fra: pwang@... [mailto:pwang@...]
Sendt: 21. november 2000 17:48
Til: siteplayer@egroups.com
Emne: [siteplayer] SiteLinkPC does not work under chinese version
windows


Hi all:
    after several hours hard working, I found that the sitelink or
sitelinkPC does not work under chinese version of Windows
98/NT/2000/ME. When I use a english windows ME, the problem solved. I
don't know why? and I hope someone in netmedia can fix the problem
soon.
by the way, BasicX has the same problem. program can't be downloaded
into BX-24 when I used a chinese windows.

Eric Wang
pwang@...
National central University
Dept. of Environmental Engineering
Taiwan



To unsubscribe from this group, send an email to:
siteplayer-unsubscribe@egroups.com

Hi all:
    after several hours hard working, I found that the sitelink or
sitelinkPC does not work under chinese version of Windows
98/NT/2000/ME. When I use a english windows ME, the problem solved. I
don't know why? and I hope someone in netmedia can fix the problem
soon.
by the way, BasicX has the same problem. program can't be downloaded
into BX-24 when I used a chinese windows.

Eric Wang
pwang@...
National central University
Dept. of Environmental Engineering
Taiwan