<task xml:lang="en" id="GUID-E81D70B1-FB3F-501D-AD3F-038C8BE997BF"><title>Updating the Network PSY Central Repository Initialization File </title><shortdesc>This topic shows you how to modify the settings of the Network PSY and the Network Location Manager so that they do not conflict with each other. </shortdesc><prolog><metadata><keywords/></metadata></prolog><taskbody><context><p>As described in <xref href="GUID-D0C20045-FCC5-53CB-BBDB-7AA058C9139E.dita">Network PSY Overview</xref>, the Network PSY does not integrate directly with positioning hardware. It uses the Network Location Manager with a Network Protocol Module to connect the Location Server (<codeph>eposserver.exe</codeph>) to positioning hardware. </p> <p>There are two places that information about the properties of the Network PSY and Network Protocol Module are stored: </p> <ul><li id="GUID-6443AE6F-BBD2-5519-A09E-A9EAFA0A0C2A"><p>The Network PSY registers itself as a PSY with the LBS subsystem using a Central Repository Initialization file <filepath>10285abe.cre</filepath> with keys defined by the <xref href="GUID-DA2DC704-CE65-54FB-9049-4E1C73092EDF-GENID-1-12-1-19-1-1-10-1-5-1-5-1-8-1.dita">Positioning Plug-in Information API</xref>. </p> </li> <li id="GUID-6511E265-0964-5FB6-A0E7-22AD101DAAAF"><p>The Network Location Manager uses the file <filepath>networklocationmanager.ini</filepath> to specify the positioning properties of your Network Protocol Module and network. </p> </li> </ul> <p>The description of the properties of the Network PSY and the Network Protocol Module must be correctly described in both <filepath>networklocationmanager.ini</filepath> and <filepath>10285abe.cre</filepath>. </p> <p>This procedure assumes you have created a Network Protocol Module for your device's positioning hardware and have modified <filepath>networklocationmanager.ini</filepath> to describe correctly the properties of the Network Protocol Module/network. </p> </context> <steps-unordered><step id="GUID-2F964162-CFC7-5FA3-AC3B-F38C8B5C404B"><cmd/><info>The contents of <filepath>networklocationmanager.ini</filepath> as supplied with the Symbian platform are shown below. You need to modify this if your Network Protocol Module and network have different properties from the ones shown here. </info> <stepxmp><codeblock id="GUID-D3CAEB9A-B377-50A7-8424-39B575B00F1D" xml:space="preserve">

</codeblock> </stepxmp> <info>For a full description of the meanings of these keys, see <xref href="GUID-DA2DC704-CE65-54FB-9049-4E1C73092EDF-GENID-1-12-1-19-1-1-10-1-5-1-5-1-8-1.dita">Positioning Plug-in Information API</xref>. </info> <info>The important keys for this task are shown in the following table: </info> <stepxmp><table id="GUID-5FAAB3F8-23F0-5EEA-951D-A400192F8A52"><tgroup cols="4"><colspec colname="col0"/><colspec colname="col1"/><colspec colname="col2"/><colspec colname="col3"/><thead><row><entry>Key name</entry> <entry>Key value</entry> <entry>Meaning</entry> <entry>Description</entry> </row> </thead> <tbody><row><entry><p> <codeph>KPSYTimeToFirstFix</codeph>  </p> </entry> <entry><p> <codeph>0x4</codeph>  </p> </entry> <entry><p>Time to First Fix </p> </entry> <entry><p>This must be the same time as the <codeph>TimeToFirstFix</codeph> value in <filepath>networklocationmanager.ini</filepath>. </p> <p> <b>Important note: In the PSY Central Repository Initialization file the time is specified in microseconds. In the Integration Module .ini file the time is specified in milliseconds.</b>  </p> </entry> </row> <row><entry><p> <codeph>KPSYTimeToNextFix</codeph>  </p> </entry> <entry><p> <codeph>0x5</codeph>  </p> </entry> <entry><p>Time to Next Fix </p> </entry> <entry><p>This must be the same time as the <codeph>TimeToNextFix</codeph> value in <filepath>networklocationmanager.ini</filepath>. </p> <p> <b> Important note: In the PSY Central Repository Initialization file the time is specified in microseconds. In the Integration Module .ini file the time is specified in milliseconds. </b>  </p> </entry> </row> <row><entry><p> <codeph>KPSYHorizontalAccuracy</codeph>  </p> </entry> <entry><p> <codeph>0x6</codeph>  </p> </entry> <entry><p>Horizontal Accuracy </p> </entry> <entry><p>This must be the same as the <codeph>HorizontalAccuracy</codeph> value in <filepath>networklocationmanager.ini</filepath>. The value is specified in metres. </p> </entry> </row> <row><entry><p> <codeph>KPSYVerticalAccuracy</codeph>  </p> </entry> <entry><p> <codeph>0x7</codeph>  </p> </entry> <entry><p>Vertical Accuracy </p> </entry> <entry><p>This must be the same as the <codeph>VerticalAccuracy</codeph> value in <filepath>networklocationmanager.ini</filepath>. The value is specified in metres. </p> </entry> </row> <row><entry><p> <codeph>KPSYCostIndicator</codeph>  </p> </entry> <entry><p>0x8 </p> </entry> <entry><p>Cost Indicator </p> </entry> <entry><p>This must be the same as the <codeph>CostIndicator</codeph> value in <filepath>networklocationmanager.ini</filepath>. The value is an integer taken from the <xref href="GUID-1AA235FA-CEC1-3853-8F96-C538C02B596D.dita#GUID-1AA235FA-CEC1-3853-8F96-C538C02B596D/GUID-78C084A0-43F8-3040-BD98-70E2E62A5D45"><apiname>TPositionQuality::TCostIndicator</apiname></xref> enum. </p> </entry> </row> <row><entry><p> <codeph>KPSYPowerConsumption</codeph>  </p> </entry> <entry><p> <codeph>0x9</codeph>  </p> </entry> <entry><p>Power Consumption </p> </entry> <entry><p>This must be the same as the <codeph>PowerConsumption</codeph> value in <filepath>networklocationmanager.ini</filepath>. The value is an integer taken from the <xref href="GUID-1AA235FA-CEC1-3853-8F96-C538C02B596D.dita#GUID-1AA235FA-CEC1-3853-8F96-C538C02B596D/GUID-AD77543D-625A-39CF-A1D5-F5B5636E17F7"><apiname>TPositionQuality::TPowerConsumption</apiname></xref> enum. </p> </entry> </row> <row><entry><p> <codeph>KPSYTechnologyType</codeph>  </p> </entry> <entry><p> <codeph>0xa</codeph>  </p> </entry> <entry><p>Technology Type </p> </entry> <entry><p>This must be the same as the <codeph>TechnologyType</codeph> value in <filepath>networklocationmanager.ini</filepath>. The value is taken from the <xref href="GUID-B098F3DB-E2FE-3C5A-8508-4B04D954AB26.dita#GUID-B098F3DB-E2FE-3C5A-8508-4B04D954AB26/GUID-03AF8C51-1CAF-3F4C-BED1-17844FAE8423"><apiname>TPositionModuleInfo::_TTechnologyType</apiname></xref> enum. </p> <p> <b>Important note: In the PSY Central Repository Initialization file the value is specified as decimal integer. In the Integration Module .ini file the value is specified in binary.</b>  </p> <p>In the file shown above, the value of 2 for this key specifies that the Network PSY supports a technology type of <codeph>ETechnologyNetwork</codeph> = 2 = 0010 in binary. </p> </entry> </row> <row><entry><p> <codeph>KPSYCapabilities</codeph>  </p> </entry> <entry><p> <codeph>0xc</codeph>  </p> </entry> <entry><p>Device Capabilities </p> </entry> <entry><p>This must be the same as the <codeph>Capabilities</codeph> value in <filepath>networklocationmanager.ini</filepath>. The value is taken from the <xref href="GUID-B098F3DB-E2FE-3C5A-8508-4B04D954AB26.dita#GUID-B098F3DB-E2FE-3C5A-8508-4B04D954AB26/GUID-4A84D57F-D202-3F79-8094-139D69630C6D"><apiname>TPositionModuleInfo::_Capabilities</apiname></xref> enum. </p> <p> <b>Important note: In the PSY Central Repository Initialization file the value is specified as a decimal integer. In the Integration Module .ini file the value is specified in binary.</b>  </p> <p>In the file shown above the value of 15 for this key specifies that the Network PSY supports the capabilities: </p> <p> <codeph>ECapabilityHorizontal + ECapabilityVertical +