Microchip Technology PL360 User manual

Brand: Microchip Technology

Model: PL360

Type: User manual

PL360

PL360 Physical Calibration

Description

The PL360 is a programmable modem for narrow-band Power Line Communication (PLC), able to run

any PLC protocol in the frequency band below 500 kHz.

This device has been designed to comply with FCC, ARIB, KN60 and CENELEC EN50065 regulations

matching requirements of Internet of Things and Smart Energy applications. It supports state-of-the-art

narrow-band PLC standards such as ITU G.9903 (G3-PLC), ITU G.9904 (PRIME) as well as any other

narrow-band PLC protocols, at the same time being a future-proof platform able to support the evolution

of these standards.

The PL360 has been conceived to be driven by external Microchip host devices, thus providing an

additional level of flexibility on the host side. The Microchip host device loads the proper PLC-protocol

firmware before modem operation and controls the PL360 modem.

Implementation of firmware protocols over PL360 requires some values be calculated by calibration;

therefore, calibration process is essential in order to get the optimal PLC signal transmission behavior in

accordance with customer specifications.

User Guide

DS50002818A-page 1

Table of Contents

Description.......................................................................................................................1

1. Overview....................................................................................................................3

2. Physical Layer Capabilities........................................................................................4

2.1. Transmission Modes.................................................................................................................... 4

2.2. Impedance Detection................................................................................................................... 5

2.3. Equalization..................................................................................................................................7

3. How to Get Calibration Values...................................................................................8

4. How to Use Calibration Values................................................................................ 11

4.1. G3 Projects.................................................................................................................................11

4.2. PRIME Projects.......................................................................................................................... 12

5. Appendix A - Setup Description...............................................................................14

6. Appendix B - Requirements for phycalibrationtool.py..............................................15

7. Revision History.......................................................................................................16

7.1. Rev A - 10/2018......................................................................................................................... 16

The Microchip Web Site................................................................................................ 17

Customer Change Notification Service..........................................................................17

Customer Support......................................................................................................... 17

Microchip Devices Code Protection Feature................................................................. 17

Legal Notice...................................................................................................................18

Trademarks................................................................................................................... 18

Quality Management System Certified by DNV.............................................................19

Worldwide Sales and Service........................................................................................20

PL360

User Guide

DS50002818A-page 2

1. Overview

The objective of this user guide is to explain the transmission stage of the physical layer in G3 and

PRIME protocols and then show how to obtain more accurate calibration values in order to:

• Meet power injection requirements

• Meet signal quality requirements

• Compensate nonlinearities of the power supply, related to components tolerances and PCB layout

• Compensate nonlinearities of the coupling design, related to components tolerances and PCB

layout

To help in this calibration process of the PL360 PHY layer, Microchip provides the PHY Calibration Tool,

an open source application developed with Python

The Microchip G3 and PRIME stack implementations include default PHY layer configuration values

optimized for the Evaluation Kits. With the help of the PHY Calibration Tool it is possible to obtain the

configuration values for the customer´s hardware implementation.

PL360

Overview

User Guide

DS50002818A-page 3

2. Physical Layer Capabilities

The firmware implementation for G3 and PRIME protocols make use of the following concepts in

relationship with the transmission and reception stages:

• Transmission Modes

• Impedance Detection

• Equalization

2.1 Transmission Modes

Transmission modes are configurations applied to the PHY layer in order to improve the performance,

efficiency and spectrum ripple of the output driver according to the impedance detected in the line.

Depending on the detected impedance, two Transmission modes are defined:

• HI_STATE. Mode optimized for high impedance (Z > 20Ω)

• VLO_STATE. Mode optimized for very low impedance (Z < 10Ω)

Additionally, the PHY layer can modify the signal gain in a way that offers optimum results when

combined with the Transmission mode. This behavior is controlled by the PIB

PHY_PARAM_CFG_AUTODETECT_BRANCH. There are three operation modes:

• FIXED_STATE_FIXED_GAIN: Transmission mode and gain are fixed

• FIXED_STATE_VAR_GAIN: Transmission mode is fixed but the gain is managed by the Automatic

Gain Control (AGC) block to achieve signal level injection target

• AUTO_STATE_VAR_GAIN: Transmission mode and gain are managed dynamically to optimize the

output according to the line impedance and signal level injection target

Since each Transmission mode is optimized within an impedance range, it doesn't work properly in terms

of performance/efficiency when operating outside such range. Let’s suppose we have set a signal

injection objective of 110 dBuV for both HI and VLO modes. The following figures show the response of

forced modes in an impedance range from 0 to 50Ω.

PL360

Physical Layer Capabilities

User Guide

DS50002818A-page 4

Figures show the signal level when both Transmission mode and gain are fixed. In each mode, the

injected transmission signal is in its intended range, but out of such range, each mode is not achieving

the injection objectives. Also it can be seen that the response has a much more stable trend for

impedance above 20Ω, and below that, the transmission driver is more dependent on impedance

detected.

It is also possible to enable a configuration feature where transmission mode is fixed, but slight changes

in gain are allowed (PHY_ID_CFG_AUTODETECT_IMPEDANCE). This allowed variation in gain is not

enough to meet injection objective.

To meet objective in all impedance range (with some limitations in low impedance as explained above),

we have to rely on operation mode recommended where an Impedance Detection and Adaptation

algorithm is implemented in the Physical layer.

2.2 Impedance Detection

The following figure shows the response in AUTO_STATE_VAR_GAIN (1) operation mode, where the

system updates its response depending on the impedance detected in reception and following signal

level, compared to the fixed modes:

PL360

Physical Layer Capabilities

User Guide

DS50002818A-page 5

This adaptation is achieved by defining thresholds to switch from HI to VLO mode, and vice versa, which

determine the points where Transmission mode is changed.

These thresholds are defined such that the switch from HI to VLO is done in a lower impedance than the

switch from VLO to HI, obtaining a hysteresis window to avoid continuous switching between states which

will lead to a continuous change in signal injection, which is an undesirable scenario.

The following figure illustrates such thresholds and the hysteresis window they achieve:

As shown in the figure, the Auto response has been obtained sweeping from high to low impedance, this

is why the switch is done near the lower value of the hysteresis window (some point between 10 and

PL360

Physical Layer Capabilities

User Guide

DS50002818A-page 6

15Ω). If the sweep is done in the opposite way, from low to high impedance, the transition will be done

near the higher value of the hysteresis window, so the curve will follow the VLO curve inside the window

and then switch to HI curve just above 20Ω.

It is also seen that the Auto curve does not follow the trend of the forced ones exactly. This is because the

algorithm performs a fine tuning in each transmission according to the detected signal value, trying to

adjust more closely to the signal injection objectives.

2.3 Equalization

Usually the output transmission driver has a non-flat response inside the working band (ripple).

Depending on the difference between carriers, we may fall in a response out of the specification which

has to be corrected to meet the constraints.

The Physical layer is able to perform this equalization by means of signal pre-distortion, which

compensates the effect of the external driver, reducing the ripple, to give a final response closer to a flat

one.

Equalization has a tight relation with the Transmission modes seen in previous sections; in fact, each

Transmission mode defines a particular equalization. As configurations are different for each mode, the

response is also different, which requires different equalization.

An important aspect to take into account is that the objective of the equalization is to reduce ripple, giving

a flatter response, but keeping the average signal injection. Therefore, care must be taken in order to

reduce signal in some carriers and increase it in others, resulting in the same response after integrating

the signal level inside the operation band.

The following figure shows an example of equalization in the G3 Cenelec-A band:

The figure shows how the ripple is reduced after equalization, keeping the same signal average in band

(overlapped curves).

PL360

Physical Layer Capabilities

User Guide

DS50002818A-page 7

3. How to Get Calibration Values

Microchip provides a Python script named "phycalibrationtool.py" in order to get optimal calibration values

implied in the signal emission characterization which could affect to the ripple, amplitude and impedance

algorithm detection used by firmware on G3 and PRIME protocol implementations (Figure 3-3).

Requirements for phycalibrationtool.py can be found in 6. Appendix B - Requirements for

phycalibrationtool.py.

This application works over phy_tester_tool firmware, so this project example must be running on the

host microcontroller of PL360 board.

Along the test process, the PLC signal may be connected to different impedance loads; therefore, it is

strongly recommended to uncouple the PLC signal as far as possible from the mains power supply of the

device under test (Figure 3-1).

Figure 3-1. Calibration Setup

The Physical Calibration process implies the following steps:

• Initialization: set default equalization and gain calibration values used by PHY Calibration Tool

• Equalization: the objective is to get a flatter frequency response of the signal on the band in use; for

that a maximum ripple must be defined below the customer limits; as general rule, Microchip

recommends a margin of 0'5-1dB in order to handle the different impedance load of the

equalization performed

• Gain Calibration: the objective of gain calibration is to get the desired signal power in a range of

variable gain for AUTO GAIN mode. An initial gain must be defined and customer must decide

minimum and maximum values for AUTO GAIN mode. The minimum value could impact on the

performance of VLOW mode when emitting against high impedance if the system can't emit low

enough to maintain the signal on the PLC line. After modifying gain it is strongly recommended to

measure the ripple again in order to check if has been affected due to non-linearity when using a

high level of power

• Max RMS Level Process: the process gets the target RMS values for each Transmission mode

• Thresholds Process: the process calculates the threshold values in order to pass between

Transmission modes (high to VLOW and opposite)

PL360

How to Get Calibration Values

User Guide

DS50002818A-page 8

Figure 3-2. PHY Calibration Tool Main Window

Figure 3-3 shows the relationship between the steps and the firmware implementation, where:

• GAIN_C: Present Gain Value: a valid value between the maximum and minimum set on calibration

• RMS_C: RMS Power Calculated

• RMS_C_C: RMS Power Calculated Corrected used for threshold comparing in order to change the

TX mode

Figure 3-3. Firmware Transmission Path Implementation

PL360

How to Get Calibration Values

User Guide

DS50002818A-page 9

All the calibration steps require a similar setup to Figure 3-1 (more information about setup in section 6.

Appendix B - Requirements for phycalibrationtool.py)

"Equalization" and "Gain Calibration" steps must be run iteratively and require the user evaluation (ripple

and power measurements). On the other hand, the PHY Calibration Tool will automatically look for the

best values on "Max RMS Process" and "Thresholds Process" steps.

CAUTION

In each iteration, equalization must be reset in order to restore default values.

Figure 3-4. PHY Calibration Tool Workflow

INIT

Default

Equalization

Gain

POWER MEASURE

RIPPLE MEASURE

EQUALIZATION

•

Reset

Values

•

Get

optimized

Values

Insert

equalized

response.

Insert

maximum

ripple

required

Preview

preliminary

correction

•

Equalization

loss

automatically

compensated

SCRIPT

Calc MAX_

RMS

_VALUES

SCRIPT

Calc THRESHOLD

VALUES

Ripple

OK?

YES

REPORT

GAIN

Adjust

GAIN INI

Power

OK?

YES

PL360

How to Get Calibration Values

User Guide

DS50002818A-page 10

4. How to Use Calibration Values

The PHY Calibration Tool generates an output configuration file (Figure 4-1) which provides the required

information to be included on G3 and PRIME projects for PL360 in order to take in account the customer

calibration.

Figure 4-1. Configuration File Report

4.1 G3 Projects

The PHY Calibration Tool generates a report file (“atpl360_coup_cfg_G3_<BAND>.h“ where <BAND>

depends on the working band) which contains the custom values that must be overwritten in the file

“common\components\plc\atpl360\G3\atpl360_coup_cfg.h”.

PL360

How to Use Calibration Values

User Guide

DS50002818A-page 11

Figure 4-2. Physical Calibration Parameters Received with PHY Calibration Tool

4.2 PRIME Projects

The PHY Calibration Tool generates the report file “atpl360_coup_cfg_PRIME.h“ which contains the

custom values that must be included on PRIME projects. The process must be done for each channel in

use. Table 4-1 shows the correspondence between report file and application code.

Table 4-1. Correspondence for PHY Calibration Tool File Report

MAX_RMS_HI_TABLE static const uint32_t spul_max_rms_hi

MAX_RMS_VLO_TABLE static const uint32_t spul_max_rms_vlo

TH1_HI_TABLE Not in use

TH2_HI_TABLE static const uint32_t spul_th_hi

TH1_VLO_TABLE Not in use

TH2_VLO_TABLE static const uint32_t spul_th_vlo

PREDIST_COEF_HI_TABLE static const uint16_t spus_equ_hi_BAND

PREDIST_COEF_VLO_TABLE static const uint16_t spus_equ_vlo_BAND

PL360

How to Use Calibration Values

User Guide

DS50002818A-page 12

IFFT_GAIN_HI_INI/MIN/MAX static const uint16_t spus_gain_hi

IFFT_GAIN_VLO_INI/MIN/MAX static const uint16_t spus_gain_vlo

DACC_CFG_TABLE static const uint32_t spul_dacc_cfg_BAND

Depending on the project, correspondence will be located on different files:

• phy_tester_tool: thirdparty\prime_ng\phy\atpl360\apps\phy_tester_tool\phy_tester_tool.c

• apps_1_4_prime_base_modem: thirdparty\prime_ng\pal\atpl360_prime\source\pal.c

Figure 4-3. Correspondence Location on apps_1_4_prime_base_modem Project

PL360

How to Use Calibration Values

User Guide

DS50002818A-page 13

5. Appendix A - Setup Description

This appendix shows the requirements of the setup in order to perform the physical calibration of a device

using a PL360.

If the DUT uses a non-isolated coupling, the ground of the control tool and the ground of the

instrumentation must be properly isolated from the ground of the LISN.

• Important considerations:

– Depending on the measurement, you can measure in time (oscilloscope) or in frequency

(spectrum/signal analyzer) domains on the BNC output of the LISN using a 50Ω terminal

– Power level in the BNC output of the LISN is 6 dB below the real value, but it is also possible

to measure directly in the PLC output using the proper measurement tools. Use caution when

PLC output is connected directly to 230 VAC mains

– Syncp’s symbols in G3 power are 3 dB higher than frame symbols

– The power of payload symbols, emitted in PRIME, is around 4dB below preamble symbols

• SETUP 1: CISPR LISN in order to determine power injected against CISPR LISN in HI_STATE

forced mode:

– Connect DUT against CISPR LISN

– Start Transmission (Label Menu>PHY Transmission >Start Transmission)

– Measure in the BNC output of CISPR LISN using a 50Ω terminal

• SETUP 2: 2Ω-LISN in order to determine power injected against 2Ω-LISN in VLO_STATE forced

mode:

– Connect DUT against 2Ω-LISN

– Start Transmission (Label Menu>PHY Transmission >Start Transmission)

– Measure in the BNC output of 2Ω-LISN using a High Impedance probe (using 50Ω terminal,

the measurement is slightly modified but it can be compensated)

PL360

Appendix A - Setup Description

User Guide

DS50002818A-page 14

6. Appendix B - Requirements for phycalibrationtool.py

This appendix shows the requirements in order to run the phycalibrationtool.py script.

To run "phycalibrationtool.py" script, it is needed to install:

• Python 3 Suite

• Python 3 Libraries:

– xlswriter

– pyserial

– pyvisa

– xlrd

– openpyxl

– pillow

– matplotlib

– future

• Microchip plc_tools_common-2.1.3 Python Library

• Microchip plc_tools_phy_tester_public-2.0.1 Python Library

• Microchip plc_tools_utils-2.0.3 Python Library

Attention: In order to install a Python 3 library as xlswriter, you must run "python pip install

xlswriter".

PL360

Appendix B - Requirements for phyc...

User Guide

DS50002818A-page 15

7. Revision History

7.1 Rev A - 10/2018

Document Initial document release.

PL360

Revision History

User Guide

DS50002818A-page 16

The Microchip Web Site

Microchip provides online support via our web site at http://www.microchip.com/. This web site is used as

a means to make files and information easily available to customers. Accessible by using your favorite

Internet browser, the web site contains the following information:

• Product Support – Data sheets and errata, application notes and sample programs, design

resources, user’s guides and hardware support documents, latest software releases and archived

software

• General Technical Support – Frequently Asked Questions (FAQ), technical support requests,

online discussion groups, Microchip consultant program member listing

• Business of Microchip – Product selector and ordering guides, latest Microchip press releases,

listing of seminars and events, listings of Microchip sales offices, distributors and factory

representatives

Customer Change Notification Service

Microchip’s customer notification service helps keep customers current on Microchip products.

Subscribers will receive e-mail notification whenever there are changes, updates, revisions or errata

related to a specified product family or development tool of interest.

To register, access the Microchip web site at http://www.microchip.com/. Under “Support”, click on

“Customer Change Notification” and follow the registration instructions.

Customer Support

Users of Microchip products can receive assistance through several channels:

• Distributor or Representative

• Local Sales Office

• Field Application Engineer (FAE)

• Technical Support

Customers should contact their distributor, representative or Field Application Engineer (FAE) for support.

Local sales offices are also available to help customers. A listing of sales offices and locations is included

in the back of this document.

Technical support is available through the web site at: http://www.microchip.com/support

Microchip Devices Code Protection Feature

Note the following details of the code protection feature on Microchip devices:

• Microchip products meet the specification contained in their particular Microchip Data Sheet.

• Microchip believes that its family of products is one of the most secure families of its kind on the

market today, when used in the intended manner and under normal conditions.

• There are dishonest and possibly illegal methods used to breach the code protection feature. All of

these methods, to our knowledge, require using the Microchip products in a manner outside the

operating specifications contained in Microchip’s Data Sheets. Most likely, the person doing so is

engaged in theft of intellectual property.

• Microchip is willing to work with the customer who is concerned about the integrity of their code.

PL360

User Guide

DS50002818A-page 17

• Neither Microchip nor any other semiconductor manufacturer can guarantee the security of their

code. Code protection does not mean that we are guaranteeing the product as “unbreakable.”

Code protection is constantly evolving. We at Microchip are committed to continuously improving the

code protection features of our products. Attempts to break Microchip’s code protection feature may be a

violation of the Digital Millennium Copyright Act. If such acts allow unauthorized access to your software

or other copyrighted work, you may have a right to sue for relief under that Act.

Legal Notice

Information contained in this publication regarding device applications and the like is provided only for

your convenience and may be superseded by updates. It is your responsibility to ensure that your

application meets with your specifications. MICROCHIP MAKES NO REPRESENTATIONS OR

WARRANTIES OF ANY KIND WHETHER EXPRESS OR IMPLIED, WRITTEN OR ORAL, STATUTORY

OR OTHERWISE, RELATED TO THE INFORMATION, INCLUDING BUT NOT LIMITED TO ITS

CONDITION, QUALITY, PERFORMANCE, MERCHANTABILITY OR FITNESS FOR PURPOSE.

Microchip disclaims all liability arising from this information and its use. Use of Microchip devices in life

support and/or safety applications is entirely at the buyer’s risk, and the buyer agrees to defend,

indemnify and hold harmless Microchip from any and all damages, claims, suits, or expenses resulting

from such use. No licenses are conveyed, implicitly or otherwise, under any Microchip intellectual

property rights unless otherwise stated.

Trademarks

The Microchip name and logo, the Microchip logo, AnyRate, AVR, AVR logo, AVR Freaks, BitCloud,

chipKIT, chipKIT logo, CryptoMemory, CryptoRF, dsPIC, FlashFlex, flexPWR, Heldo, JukeBlox, KeeLoq,

Kleer, LANCheck, LINK MD, maXStylus, maXTouch, MediaLB, megaAVR, MOST, MOST logo, MPLAB,

OptoLyzer, PIC, picoPower, PICSTART, PIC32 logo, Prochip Designer, QTouch, SAM-BA, SpyNIC, SST,

SST Logo, SuperFlash, tinyAVR, UNI/O, and XMEGA are registered trademarks of Microchip Technology

Incorporated in the U.S.A. and other countries.

ClockWorks, The Embedded Control Solutions Company, EtherSynch, Hyper Speed Control, HyperLight

Load, IntelliMOS, mTouch, Precision Edge, and Quiet-Wire are registered trademarks of Microchip

Technology Incorporated in the U.S.A.

Adjacent Key Suppression, AKS, Analog-for-the-Digital Age, Any Capacitor, AnyIn, AnyOut, BodyCom,

CodeGuard, CryptoAuthentication, CryptoAutomotive, CryptoCompanion, CryptoController, dsPICDEM,

dsPICDEM.net, Dynamic Average Matching, DAM, ECAN, EtherGREEN, In-Circuit Serial Programming,

ICSP, INICnet, Inter-Chip Connectivity, JitterBlocker, KleerNet, KleerNet logo, memBrain, Mindi, MiWi,

motorBench, MPASM, MPF, MPLAB Certified logo, MPLIB, MPLINK, MultiTRAK, NetDetach, Omniscient

Code Generation, PICDEM, PICDEM.net, PICkit, PICtail, PowerSmart, PureSilicon, QMatrix, REAL ICE,

Ripple Blocker, SAM-ICE, Serial Quad I/O, SMART-I.S., SQI, SuperSwitcher, SuperSwitcher II, Total

Endurance, TSHARC, USBCheck, VariSense, ViewSpan, WiperLock, Wireless DNA, and ZENA are

trademarks of Microchip Technology Incorporated in the U.S.A. and other countries.

SQTP is a service mark of Microchip Technology Incorporated in the U.S.A.

Silicon Storage Technology is a registered trademark of Microchip Technology Inc. in other countries.

GestIC is a registered trademark of Microchip Technology Germany II GmbH & Co. KG, a subsidiary of

Microchip Technology Inc., in other countries.

All other trademarks mentioned herein are property of their respective companies.

PL360

User Guide

DS50002818A-page 18

ISBN: 978-1-5224-3695-9

Quality Management System Certified by DNV

ISO/TS 16949

Microchip received ISO/TS-16949:2009 certification for its worldwide headquarters, design and wafer

fabrication facilities in Chandler and Tempe, Arizona; Gresham, Oregon and design centers in California

and India. The Company’s quality system processes and procedures are for its PIC

MCUs and dsPIC

DSCs, KEELOQ

code hopping devices, Serial EEPROMs, microperipherals, nonvolatile memory and

analog products. In addition, Microchip’s quality system for the design and manufacture of development

systems is ISO 9001:2000 certified.

PL360

User Guide

DS50002818A-page 19

AMERICAS ASIA/PACIFIC ASIA/PACIFIC EUROPE

Corporate Office

2355 West Chandler Blvd.

Chandler, AZ 85224-6199

Tel: 480-792-7200

Fax: 480-792-7277

Technical Support:

http://www.microchip.com/

support

Web Address:

www.microchip.com

Atlanta

Duluth, GA

Tel: 678-957-9614

Fax: 678-957-1455

Austin, TX

Tel: 512-257-3370

Boston

Westborough, MA

Tel: 774-760-0087

Fax: 774-760-0088

Chicago

Itasca, IL

Tel: 630-285-0071

Fax: 630-285-0075

Dallas

Addison, TX

Tel: 972-818-7423

Fax: 972-818-2924

Detroit

Novi, MI

Tel: 248-848-4000

Houston, TX

Tel: 281-894-5983

Indianapolis

Noblesville, IN

Tel: 317-773-8323

Fax: 317-773-5453

Tel: 317-536-2380

Los Angeles

Mission Viejo, CA

Tel: 949-462-9523

Fax: 949-462-9608

Tel: 951-273-7800

Raleigh, NC

Tel: 919-844-7510

New York, NY

Tel: 631-435-6000

San Jose, CA

Tel: 408-735-9110

Tel: 408-436-4270

Canada - Toronto

Tel: 905-695-1980

Fax: 905-695-2078

Australia - Sydney

Tel: 61-2-9868-6733

China - Beijing

Tel: 86-10-8569-7000

China - Chengdu

Tel: 86-28-8665-5511

China - Chongqing

Tel: 86-23-8980-9588

China - Dongguan

Tel: 86-769-8702-9880

China - Guangzhou

Tel: 86-20-8755-8029

China - Hangzhou

Tel: 86-571-8792-8115

China - Hong Kong SAR

Tel: 852-2943-5100

China - Nanjing

Tel: 86-25-8473-2460

China - Qingdao

Tel: 86-532-8502-7355

China - Shanghai

Tel: 86-21-3326-8000

China - Shenyang

Tel: 86-24-2334-2829

China - Shenzhen

Tel: 86-755-8864-2200

China - Suzhou

Tel: 86-186-6233-1526

China - Wuhan

Tel: 86-27-5980-5300

China - Xian

Tel: 86-29-8833-7252

China - Xiamen

Tel: 86-592-2388138

China - Zhuhai

Tel: 86-756-3210040

India - Bangalore

Tel: 91-80-3090-4444

India - New Delhi

Tel: 91-11-4160-8631

India - Pune

Tel: 91-20-4121-0141

Japan - Osaka

Tel: 81-6-6152-7160

Japan - Tokyo

Tel: 81-3-6880- 3770

Korea - Daegu

Tel: 82-53-744-4301

Korea - Seoul

Tel: 82-2-554-7200

Malaysia - Kuala Lumpur

Tel: 60-3-7651-7906

Malaysia - Penang

Tel: 60-4-227-8870

Philippines - Manila

Tel: 63-2-634-9065

Singapore

Tel: 65-6334-8870

Taiwan - Hsin Chu

Tel: 886-3-577-8366

Taiwan - Kaohsiung

Tel: 886-7-213-7830

Taiwan - Taipei

Tel: 886-2-2508-8600

Thailand - Bangkok

Tel: 66-2-694-1351

Vietnam - Ho Chi Minh

Tel: 84-28-5448-2100

Austria - Wels

Tel: 43-7242-2244-39

Fax: 43-7242-2244-393

Denmark - Copenhagen

Tel: 45-4450-2828

Fax: 45-4485-2829

Finland - Espoo

Tel: 358-9-4520-820

France - Paris

Tel: 33-1-69-53-63-20

Fax: 33-1-69-30-90-79

Germany - Garching

Tel: 49-8931-9700

Germany - Haan

Tel: 49-2129-3766400

Germany - Heilbronn

Tel: 49-7131-67-3636

Germany - Karlsruhe

Tel: 49-721-625370

Germany - Munich

Tel: 49-89-627-144-0

Fax: 49-89-627-144-44

Germany - Rosenheim

Tel: 49-8031-354-560

Israel - Ra’anana

Tel: 972-9-744-7705

Italy - Milan

Tel: 39-0331-742611

Fax: 39-0331-466781

Italy - Padova

Tel: 39-049-7625286

Netherlands - Drunen

Tel: 31-416-690399

Fax: 31-416-690340

Norway - Trondheim

Tel: 47-72884388

Poland - Warsaw

Tel: 48-22-3325737

Romania - Bucharest

Tel: 40-21-407-87-50

Spain - Madrid

Tel: 34-91-708-08-90

Fax: 34-91-708-08-91

Sweden - Gothenberg

Tel: 46-31-704-60-40

Sweden - Stockholm

Tel: 46-8-5090-4654

UK - Wokingham

Tel: 44-118-921-5800

Fax: 44-118-921-5820

Worldwide Sales and Service

User Guide

DS50002818A-page 20

Microchip Technology PL360 User manual

Microchip Technology PL360 User manual

Microchip Technology PL360 User manual

Related papers

Other documents