Symbian OS Communications (779884), страница 79
Текст из файла (страница 79)
It is possible to use a CF card-based Bluetooth module, suchas the Brainboxes BL-565. When you insert this card in your laptop,Windows will ask you which driver to install. Use the advanced installoption to select the driver yourself, prevent Windows from searching fora driver, and tell it that you will select the driver manually.
The type ofdriver you want is ‘Ports (COM & LPT)’, then in ‘(Standard port types)’ youcan select ‘Communications Port’. Windows warns you that the drivermay not be compatible with your hardware – just say ‘Yes’ to continueinstallation.Once you’ve installed the driver, go to Device Manager in Windowsto find out which COM port number your card was assigned. Make a noteof this, and then use either the SDK configuration dialogs, or the manualmethod described next, to configure the correct port number in SymbianOS.
The Brainboxes card we used supported the BCSP protocol, so makesure you select the correct HCI type when configuring the emulator. Onceconfigured, the hardware should just work.Whichever hardware you are using, you must set the appropriate COMport number in the bt.bt.esk file, which on the emulator can be found in/epoc32/release/winscw/udeb/z/private/101f7989/esock/. The [hci] section contains a port= attribute, which should beset to the appropriate Symbian OS COMM port number, bearing in mindthe note earlier in this chapter about the difference between Symbian OSand Windows COM port numbering!Make sure that you first type "port= " and then the number.
Theremust be no space between the port and the equals sign. Then insert394SETTING UP FOR DEVELOPMENTexactly one space, then the port number - otherwise the S60 SDK toolsmay not be able to parse and configure the file.In previous releases of Symbian OS (v7.0 to v8.0), the file was calledbt.esk and lived in /epoc32/winscw/c/system/data/. In v8.1the file was renamed to bt.bt.esk, but remained in the samelocation.In very early releases (pre-v7.0, and some versions of 7.0s and 8.0asuch as the ones shipped in the S60 2nd edition SDKs), it lived in/epoc32/wins/c/system/data/.The appropriate HCI can be chosen by altering thehcidllfilename= tag to either hci_bcsp.dll or hci_h4.dll.Using Bluetooth hardware with a USB connectionThis is a new feature in the S60 3rd edition, Feature Pack 2 SDK; althoughthe configuration option to use a USB HCI appears in the Feature Pack 1SDK, but has no effect. However, there is a download available from theForum Nokia website (http://www.forum.nokia.com), called ‘S60 SDK BTdriver’, that can be used with the S60 3rd edition SDK, and the S60 3rdedition, Feature Pack 1 SDK.
After it has been installed on the 3rd edition,Feature Pack 1 SDK, the menu option to use a USB HCI works correctly.Instructions are included in the package for installing the driver andconfiguring the emulator to use it. We used a TDK USB Bluetooth dongleto test this functionality, which worked successfully with in conjunctionwith S60 3rd edition, Feature Pack 1 SDK.13.2IrDAInfrared is supported on the emulator with the addition of an IR pod. Aswith Bluetooth, IR pods are connected via RS-232 to the emulator. TheSymbian OS emulator does not support IR pods that connect via USB.Using USB-to-serial adaptors to connect serial-based IR pods is also notrecommended, as the speed at which the IR pod operates is typically setby wiggling the flow control lines, and many USB-to-serial adaptors donot perform this operation faithfully – leaving Symbian OS and the IR poddisagreeing about which state they are in.There are 10 different IR pods supported, although experience showsthat even IR pods that are not supported are likely to conform to theIRDA395signalling used by a supported pod.
The best advice is to experimentand see!The supported pods are:• Actisys 220L• Actisys 220L+• Actisys 220Li• iFoundry 8001aThe following models are not as well supported, are supported buthave been discontinued, or are harder to find:• Tekram IR-210• ConnectTech (unspecified model)• Extended Systems Jeteye 7201• Extended Systems Jeteye 7401 (also supports the 7501) – often labelledXTNDAccess instead of Jeteye• Parallax (unspecified model).In all cases, Symbian OS needs a basic serial port interface to the IRpod.
This means you must not install any Windows drivers that comewith the IR pod you are using. You can see if there are any IR driversinstalled by looking in the Windows Device Manager and checking for‘Infrared devices’. If you see your IR pod listed there you will need touninstall the Windows drivers before Symbian OS can use it.13.2.1 Setting up the Easy Way – Using the SDK ConfigurationDialogsThe easiest way to choose the port number in the UIQ3.0 SDK, using theSDKConfig app, is to go to the ‘communications’ tab and to select theappropriate port.
However, if you want to use a pod that isn’t compatiblewith JetEye 7401, such as the Jeteye 7501, Parallax or iFoundry 8001a,then you’ll have to edit the configuration file as indicated later.Similarly, if you want to alter the settings for the S60 3rd edition SDK,you’ll need to start the emulator, go to the ‘Tools’ menu and choose‘Preferences’, then select the ‘PAN’ tab, enable IrDA and choose theappropriate COM port.
Again, if you need to use a pod other than thedefault Jeteye 7401, you’ll need to edit the config file manually.396SETTING UP FOR DEVELOPMENTNote that these user interfaces for the selection of the COM port usethe Windows numbering system, not the Symbian OS one!13.2.2 Setting up the Manual Way – Editing the Config FileThe config file you need to edit is called ir.irda.esk, and is locatedin the /epoc32/release/winscw/udeb/z/private/101f7989/esock/ directory.The two settings you need to change are the irPod and irPhysicalCommPort.
The irPhysicalCommPort should be set to the valueof the Symbian OS COMM port to which the IR pod is attached, bearingin mind the note at the beginning of this chapter about the differences innumbering between Symbian OS and Windows COMM ports.The irPod value should be set to one of following nine options,depending on which IR pod you are using:actisys220l, actisys220l+, actisys220li, tekram, jeteye7201, jeteye7401,parallax, ifoundry8001a, or connectTechAs per the Bluetooth case, make sure the ‘=’ sign on the config isimmediately after the variable name, then there is precisely one space,and then the value, for example irPod= actisys220l.13.3Network Connections for IPThere are various different ways to connect the emulator to an IP network – which one you choose depends on a combination of personalpreference, what hardware you have available, whether you need accessto a specific network (e.g., for sending and receiving MMS) and whichyou can get to work for your particular setup.Table 13.2 provides a list of these options (which we’ll refer to by ashort name) and the situations in which you can use them.The first three methods of connection are the preferred methods –however, sometimes the second three can come in handy so we mentionthem for the sake of completeness.There is one more solution – called WinTunnel – that can be used,but as WinTunnel is not widely available outside Symbian we will notdiscuss it here.13.3.1 Setting up the Easy Way – Using the SDK ConfigurationDialogsFirst, some good news.
The SDK teams have created tools that will do alot of the work for you! In the case of the S60 3rd edition emulator youNETWORK CONNECTIONS FOR IP397Table 13.2 Network connections for IPTechnologyHardware requiredWinPCapA wired Ethernet card on your PC,1 and a networkconnection from that Ethernet cardWinTAPAny IP connection from your PC, and the ability toenable Internet Connection Sharing on your PCWinSockAny IP connection from your PCNT RASTwo serial ports on your PC (or a second PC), the abilityto enable NT RAS on the PC, and an IP connection fromthe PCAnalog modemAn analog modemMobile phoneA serial link (RS-232, Bluetooth or infrared) to asupported phonealready have the WinSock method set up for you.
In the case of the UIQ3.0 emulator, if you allow it to install WinPCap during installation, you’llhave the WinPCap method available – although you still need to run theSDKConfig program provided, go to the Communications tab, and press‘Apply Ethernet’ to set it up. In either case, this can save you a lot of work.However, there will be circumstances where something isn’t workingdue to your specific network or PC configuration. To deal with thesecases, we’ll offer some debugging tips below, in addition to showing youwhat the SDK tools are actually doing behind the scenes.13.3.2 Configuring CommsDatFirst we should mention a topic that affects you no matter which manualconfiguration method you use – configuring CommsDat.CommsDat is the repository for all IP-related communications settingson Symbian OS and it also contains important information about defaultTSYs, and, for certain TSYs, configuration information.Be warned – altering the data in CommsDat gives you a lot morefreedom than using the UI configuration mechanisms, but it’s also1Note that most WLAN connections will fail to work with this method, as Ethernetpackets are transmitted from Symbian OS in Ethernet II or 802.3 format which is incompatiblewith most WLAN chipsets.
![](https://s.studizba.com/z.php?f=/templates/si/i/noavatar.png&w=100&h=100&t=1"){kind=avatar}
