LCRF

Privacy preferences

Choose optional purposes independently. You can change or withdraw your choice at any time from the footer.

Strictly necessary

Required for security, session functions and storing your privacy choice.

Always active
Preferences

Remembers optional display or language settings when these features are enabled.

Analytics

Uses first-party visitor and session identifiers to measure pages, referrals and inquiry interactions.

Marketing

Allows marketing measurement or third-party advertising technologies if they are introduced in the future.

Contact LCRF for RF Projects

Contact LCRF with RF project requirements, operating conditions, quantities and document needs for quotation, technical review or sample coordination.

Engineering inquiry

Share your RF requirement

Share the product, operating requirements and project context. Our engineering team will route your request to the right specialist.

AttachmentsAttach drawings, BOMs, specifications or test files. Up to 5 files, 10 MB each and 25 MB total.
or drag and dropPDF, DOCX, XLSX, CSV, TXT, JPG, PNG, S1P and S2P
Typically reviewed within one business dayProject information is handled confidentially

Before you send

Give the request a clear engineering boundary

A model number is useful, but an actionable RF inquiry also states where the hardware sits, the conditions it must handle and the decision your team needs to make.

01
Product or signal-chain role
Name the product family or SKU when known. Otherwise describe the function: source, conversion, gain, filtering, switching, distribution, monitoring, interconnect, antenna, power, thermal or test.
02
Operating conditions
Include frequency range, signal or waveform, gain or loss, power or noise target, linearity, impedance, interfaces, supply, control, cooling and environment where they affect selection.
03
Commercial context
State prototype, evaluation or production stage; expected quantity; destination; target schedule; and whether the request is for quotation, technical evaluation, a sample or documentation.
04
Evidence and deliverables
List the records needed for the next decision, such as datasheet, outline drawing, test conditions, inspection evidence, compliance context or a project-specific acceptance basis.

Request handling

A controlled path from intake to a scoped response

The route depends on the facts supplied and the project stage. Open assumptions are identified before a configuration, document set or commercial scope is treated as agreed.

  1. 01

    Intake and routing

    The form records the request type, organization, destination, quantity stage, technical context and attachments so the inquiry can be directed to the relevant review path.

  2. 02

    Technical and commercial review

    Available product records, operating assumptions, evidence needs, configuration limits and commercial inputs are checked together. Missing facts or conflicts are returned as focused questions.

  3. 03

    Scoped response

    The response may identify a standard product path, request further data, define a feasibility review or state the configuration, evidence and commercial boundary that can be offered.

Direct contact

Use the channel that matches the information

Use email for engineering records and detailed requirements. Use WhatsApp for brief commercial coordination. Response timing depends on scope, completeness and project stage.