Good Morning George, I've been following this subject in the group discussion and agree that the conversation is moving in and out (like most conversations) of the primary question at hand. To answer your question the following is what I'm using: 1. On the PC side, I have a basic wireless router (D-Link) set up (i.e. cable modem connected to the wireless router and desktop PC). My home wireless setup is also WPA-PSK secured (i.e. requiring additional security settings and passcodes be set on any other wireless devices connected to my wireless home network). 2. On the Disklavier side (I have a Mark IV and Ver. 4.0 system software), I have an ethernet LAN cable connected between the LAN port from the Disklavier IO Center and a Pelican Wireless Gaming Adapter. The Pelican unit provides the wireless connectivity between the Disklavier and my home network/web. The Pelican wireless adapter is primarily aimed at X-Box users/gamers who wants to connect their X-Boxes wirelessly to the internet so they can play games with others across the web. Despite the name, the Pelican unit is a wireless network adapter and access point. One needs to perform an initial setup and configure the Pelican unit to connect to the home wireless network first prior to making the LAN connection to the Disklavier. On the Disklavier side, the System Network setup is set to DHCP. The overall set up is fairly simple and it works well for me. I used it successfully for downloading and upgrading the system software and using the Disklavier Radio and IDC application. Our Disklavier is normally powered off when not in use. Ocassionally I have to "reboot" the Pelican unit (unplug the power for a few seconds) and reset the System Network settings to re-establish the wireless connections. BTW - I also have 50 ft length ethernet LAN cable just in case (LOL). One note - I personally do not like the adapters that uses the regular home AC outlet ports to make LAN connections between devices. I'm sure they are designed correctly but I'm not comfortable with them. Best Regards, George Kong ________________________________ From: George F. Litterst <PianoBench@...> To: disklavier@yahoogroups.com Sent: Thu, July 8, 2010 8:12:03 AM Subject: Re: [disklavier] Re: what wireless internet ethernet bridge works best with disklaviers ?? Good morning, everyone. I think that the conversation has become confused. The question is really this: What device do many Mark IV owners connect to the ethernet port of their Disklavier to that the Disklavier can connect wirelessly from that point to a wi-fi router (such as the Airport Extreme). The device is question is known as a wireless bridge because it wireless bridges the distance that would normally be connected with a cable. The Airport Extreme is not a wireless bridge. It is true that the Disklavier has a wi-fi feature, but its purpose is to connect to the PRC-100 or to the tablet controller. Therefore, if you want wireless connectivity to your local area network, you need a wireless bridge. I have one such device that was made by Buffalo. However, Buffalo was sued over this product, and I don't believe that it is available in this country any more. It would be interesting to know what other people use. I know some have reported success using an Apple Airport Express. I was never able to get mine to work in this capacity. Regards, PianoBench www.georgelitterst. com www.timewarptech. com On Jul 7, 2010, at 10:09 AM, varipapa wrote: >The Airport Extreme is a wireless router/bridge all in one. Just connect your >cable modem or other 'internet' box to the WAN port. > >There are 4 LAN ports too, one of which can be used to connect the Mark 4. > >--- In disklavier@yahoogro ups.com, mark wilson <marksletters2@ ...> wrote: >> >> at the apple store they tell me the airport is a wireless transmitter. ... >> a BRIDGE is a wireless reciever >> >> how do you connect the airport to the i/o unit of your mark 4?.
Message
Re: [disklavier] Re: what wireless internet ethernet bridge works best with disklaviers ??
2010-07-08 by George Kong
Attachments
- No local attachments were found for this message.