The sketch for the whole project is at the bottom of the page. Each one is a different milestone in the project, so you can pick-and-choose examples without unnecessary code. I also include four, count-em four, example Arduino sketches. In this tutorial I'll lead you through my thought process as this project developed. With that in mind, let me say up front that up until now I had no experience with either the SpeakJet chip or any sort of embedded network/wifi devices. We already had the Tweeting Kegerator tutorial, which allows the hardware to post metrics over a wired network connection, so for this project I instead wanted the network side of the project to affect the hardware in some interesting (and of course wireless) way. First, to demonstrate the capability of the WiFly module, and second, to interact with hardware from a browser in a unique way. Remember that you won’t see any pump icons on the client until you have set up pumps using Enabler Configuration.This project started with two goals. If there is a mismatch, the application will work partially or not at all. VersionĮnsure that the Enabler client module incorporated into the POS application is the same version as the Server part of The Enabler software. To test that your machines are configured correctly, we recommend you use the demonstration program pumpdemo.exe in the Enabler directory. Note: For servers running Windows Vista, Windows XP or Windows Server 2003 (SP2), refer to our FAQ page What security settings are required for Enabler Server PCs running WinXP SP2 or later? for additional steps. Make sure “Run application on the following computer” is not checked.Make sure “Run application on this computer:” is checked.Make sure “Run application on the computer where the data is located” is not checked.Make sure “Run application on this computer” is not checked.Enter the name of the computer running the Enabler Server in the box underneath.Make sure that “Run application on the following computer:” is checked.Right click on Enabler Pump Server and select Properties… Client Computers Windows 2003 (SP2) / Windows XP / Windows Vista:Įxpand the explorer on the left-hand side to see the list of registered DCOM servers as shown below: Select the entry for Enabler Pump Server, and click properties. On each computer accessing the Enabler, including the server, run the Windows DCOM Configuration Utility, DCOMCNFG, from a command prompt or the Start – Run… menu. Normally you can use .x addresses safely. Try setting both machines to a static (fixed) IP address instead of using “Automatically obtain an IP address” (DHCP).Check that both client and server have an IP address, by typing “ipconfig” at a command prompt.If using an Ethernet hub/switch/router, ensure it is configured to allow the two machines to communicate.Check that the “link” indicator is lit on both client and server network cards.Check that both client and server Ethernet cables are connected.If you have any other error when trying to ping the server:.Once installed, check the configuration as described in 2 (below), and then try to ping the server again. The ping.exe program is installed as part of TCP/IP. The name specified is not recognised as an internal or external command, operable program or batch file.Įnsure that TCP/IP is installed. If the ping command does not work, check the following: If this command works correctly it will list replies from the server. Open a command prompt on the Client machine and type the following command: TCP/IPįirst establish that the TCP/IP network is working correctly. Check the following items to troubleshoot your problem. If any of these are not right then The Enabler Client will be able to connect to the Server. ODBC configuration (if you need to access the Enabler Database).Windows Firewall (for systems running Windows XP SP2 or later).The Client to Server connection for Enabler versions up-to V3 relies on correct setup for:
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |