Draft:Integra Serial Control Protocol

Submission declined on 24 May 2026 by Devonian Wombat (talk). This draft reads like an advertisement. Wikipedia is an encyclopedia, not a platform for promotion or marketing. Drafts that are exclusively promotional may be deleted without notice. Wikipedia articles must be written neutrally in a formal, impersonal, and dispassionate way. They should not read like a blog post, advertisement, or fan page. Rewrite the draft to remove: promotional language: see Words to watch; personal commentary: opinions or direct addresses to the reader; informal language. Instead, only summarize in your own words a range of independent, reliable, published sources that discuss the subject. If you have a conflict of interest (e.g. you are the subject, an employee, or a relative) or are being paid to edit, you must disclose this to comply with Wikipedia's Terms of Use. This draft's references do not show that the subject meets Wikipedia's criteria for inclusion. The draft requires multiple published secondary sources that: provide significant coverage: discuss the subject in detail, not just brief mentions or routine announcements; are reliable: from reputable outlets with editorial oversight; are independent: not connected to the subject, such as interviews, press releases, the subject's own website, or sponsored content. Please add references that meet all three of these criteria. If none exist, the subject is not yet suitable for Wikipedia. If you would like to continue working on the submission, click on the "Edit" tab at the top of the window. If you have not resolved the issues listed above, your draft will be declined again and potentially deleted. If you need extra help, please ask us a question at the AfC Help Desk or get live help from experienced editors. Please do not remove reviewer comments or this notice until the submission is accepted. Where to get help If you need help editing or submitting your draft, please ask us a question at the AfC Help Desk or get live help from experienced editors. These venues are only for help with editing and the submission process, not to get reviews. If you need feedback on your draft, or if the review is taking a lot of time, you can try asking for help on the talk page of a relevant WikiProject. Some WikiProjects are more active than others so a speedy reply is not guaranteed. How to improve a draft Wikipedia:Contributing to Wikipedia – a basic overview on how to edit Wikipedia. Help:Wikitext – how to use the markup Help:Referencing for beginners – how to include references Wikipedia:Article development – how to develop your article Wikipedia:Writing better articles – how to improve your article Wikipedia:Verifiability – make sure your article includes reliable third-party sources You can also browse Wikipedia:Featured articles and Wikipedia:Good articles to find examples of Wikipedia's best writing on topics similar to your proposed article. Improving your odds of a speedy review To improve your odds of a faster review, tag your draft with relevant WikiProject tags using the button below. This will let reviewers know a new draft has been submitted in their area of interest. For instance, if you wrote about a female astronomer, you would want to add the Biography, Astronomy, and Women scientists tags. Add tags to your draft Editor resources Easy tools: Citation bot (help) | Advanced: Fix bare URLs Declined by Devonian Wombat 2 months ago. Last edited by Devonian Wombat 2 months ago. Reviewer: Inform author. Resubmit Please note that if the issues are not fixed, the draft will be declined again.

Submission declined on 7 March 2026 by Youshouldchooseausernamethat (talk). This draft is not adequately supported by reliable sources. Wikipedia's verifiability policy requires that all content be supported by reliable sources. Reliable sources include: reputable newspapers, magazines, academic journals, and books from respected publishers. Unacceptable sources include: personal blogs, social media, predatory publishers, most tabloids, and websites where anyone can contribute. Replace any unreliable sources with high-quality sources. If you cannot find a reliable source for the material, it should be removed. Declined by Youshouldchooseausernamethat 5 months ago.

• Comment: See WP:NOTGUIDE, this reads like a product page or instructional pamphlet rather than a description of the subject. In addition, most of the sources appear to be to primary sources associated with Integra, or to blogs such as Mikhail Kulesh's that are not reliable sources due to a lack of editorial oversight. Devonian Wombat (talk) 21:38, 24 May 2026 (UTC)

• Comment: Thank you for your submission. For an article this long with this much information, you will need more citations. Four of the six citations appear after the name of the article. Citations do not need to go here; there is no point in adding this right after the front. Additionally, it contains an excessive amount of intricate detail, which is generally prohibited. It is, however, well formatted, especially the tables, with potential notability. Youshouldchooseausernamethat (Youshouldtalk) 00:49, 7 March 2026 (UTC)

Integra Serial Control Protocol

Communication protocol
Abbreviation	ISCP
Developers	Intergra and Onkyo
Introduction	August 22, 2003; 22 years ago (2003-08-22)

Integra Serial Control Protocol (ISCP):^{[1] [2][3][4]}is a proprietary command protocol developed by Integra (subdivision of Onkyo) and Onkyo for controlling home audio and home theater equipment. It is used to remotely operate devices such as AV receivers, preamplifiers, and disc players, enabling functions like power management, input selection, volume control, and status querying. The protocol is also used by some of Pioneer (after Pioneer Home Electronics sold to Onkyo) products.^[5][6]

Originally designed for RS-232 serial communication, ISCP was later adapted for network transport over TCP/IP, commonly referred to as eISCP (Ethernet ISCP). This evolution allowed Integra and Onkyo components to be integrated into IP-based home automation systems and software controllers.

lates version is 1.53 (3 February 2025)^[1]

ISCP over serial uses a simple 3-wire RS-232C connection with the following parameters^[1][7]

The physical connector is a 9-pin female D-sub:

A straight-through cable is used to connect the device to a PC or controller.

Messages are ASCII text and follow this structure:^[1]

Start Character: 8 bits

Start Character of ISCP message. !

Destination Unit type Character: 8 bits

Indicate type; discovery x and p, Zone 1-8

Command: 32 bits

Command/Status/Question/Event Notice type

Parameter: Variable length

Command/Status/Question/Event Notice parameter

End Character: 8-16 bits

indicate end of ISCP message.[CR] or [LF] or [CR][LF]

A typical controller → device message for "Power On" is:

where:

• ! is the start character
• 1 is the destination unit type (1 = receiver)
• PWR01 is the ISCP command and parameter
• [CR], [LF], or [CR][LF] terminates the message

A device → controller response indicating "Power Standby" may look like:

Special characters used by the protocol:

Ethernet Integra Serial Control Protocol

Communication protocol
Abbreviation	eISCP
Developers	Intergra and Onkyo
Based on	ISCP over RS232
Ports	TCP 60128, UDP 60128, for Auto Detect using broadcast (v1.19)

With the introduction of network-enabled receivers, ISCP was encapsulated for transport over TCP/IP. This form is known as eISCP or ISCP over Ethernet.^[1]

Modern receivers (introduced after 2011, with version 1.19 or higher) support automatic discovery on a local network, allowing controllers to find compatible devices without manual configuration. This makes setup simpler and avoids the need to know IP addresses in advance.

To begin discovery, a controller broadcasts a short “device search” message over the local network using UDP on port 60128. Onkyo and Integra devices respond to a generic query x, while Pioneer models use a slightly different variant p. Any receiver that understands ISCP will reply with an identification message. The protocol doesn't list any multicast support, so inter Subnet of auto discovery is not supported.^[1]

Each responding device sends back a single line containing its model name, control port, regional variant, and a unique identifier (typically derived from its network address). From this information, the controller can present a human-readable device name, determine how to connect, and establish a control session automatically.

This mechanism enables plug-and-play behavior in home automation systems: receivers appear on the network, announce themselves, and can be added by the user without manual network setup.

An eISCP packet consists of a binary header followed by the standard ISCP message:^[1]

Header Size: 32 bits

Size of the eISCP header. Currently 0x00000010 (big-endian)

Data Size: 32 bits

Length of the eISCP data section (big-endian)

Version: 8 bits

ISCP version, currently 0x01

Reserved: 24 bits

Reserved for future extensions.

Start Character: 8 bits

Start Character of eISCP message. !

Destination Unit type Character: 8 bits

Indicate type; discovery x and p, Zone 1-8

Command: 32 bits

Command/Status/Question/Event Notice type

Parameter: Variable length

Command/Status/Question/Event Notice parameter

End Character: 8-16 bits

indicate end of eISCP message.[CR] or [LF] or [CR][LF]

eISCP provides no built-in authentication, encryption, or access control.^[1] Commands and status messages are transmitted in clear text over TCP, and any client on the same internet that can reach the receiver's control port can issue commands or subscribe to status updates.

The protocol assumes a trusted local network environment and was designed for closed home or automation networks rather than exposure to untrusted or public networks.

As a result:

• Any reachable client can control the device if the port is accessible.
• Commands and metadata can be observed by passive network monitoring.
• Device discovery relies on unauthenticated UDP broadcasts.

In practice, eISCP security is typically provided by the surrounding network infrastructure, such as router, firewall and VLAN segmentation.

ISCP defines three fundamental message types; Command, Question, and Notification to manage communication between a controller and a receiver. The protocol is designed for point-to-point communication between a third-party controller and a single receiver.^[1]

The receiver and controller exchange short textual messages representing device state and control actions. All interactions follow a request/response or event-driven pattern, ensuring that the controller can both control the device and remain synchronized with its current status.

• Command Message is sent from the controller to the receiver to change the state of the device. The receiver also provides unsolicited feedback: if the receiver's internal status changes for any reason (for example, due to front-panel operation or another controller), it sends a Status Message to all connected controllers. This is to ensures that the controller can immediately verify that a command has been applied and remain synchronized with the actual device state.
• Question Message is used by the controller to query the current state of a function without modifying it. The receiver replies with a corresponding status message. Question communication allows a controller to initialize its state after connecting, recover from lost synchronization, or periodically verify device status
• Event Notice Communication, the receiver autonomously informs the controller when a system state changes. No prior request is required. Combined with persistent connections (as required by eISCP), this event-driven model enables real-time synchronization between the receiver and all connected control systems.

The ISCP command^[1] set is organized into functional domains that together cover the entire signal path of an AV receiver: power, inputs, volume, speakers, audio processing, video, networking, tuning, system status, and maintenance. Each domain follows the same interaction pattern:

• Set: change a value or state
• Up/Down / TG: stepwise or wrap-around adjustment
• QSTN: query the current state
• Status

Core domains include:

• System Control: PWR, SLP, RST, APD, ECO power, sleep, reset, and energy management.
• Volume and Muting: MVL, AMT, CMT, SWL, CTL, TCL master volume, muting, and per-channel levels.
• Tone and EQ: TFR, TFW, TFH, TCT, TSR, TSB, TSW, ACE, EQS, STW bass, treble, and equalization across speaker groups.
• Speaker Configuration: SPA/SPB, SPL, SPI, SPD zone selection, layout, size, and distance.
• Input and Signal Selection: SLI, SLR, SLA, VSL, ISS source selection, record-out, and input management.
• Listening and Processing Modes: LMD, DIR, LTN, RAS, ADY, ADQ, ADV, DVL, AEQ surround modes, room correction, and night processing.
• Video and HDMI Control: HDO, HAO, HAS, CEC, RES, VPM, VWM, HSF output routing, resolution, and picture modes.
• Information and Display: DIF, IFA, IFV, IFN, FLD device, audio, video, and network status.
• Networking and System: FWV, UPD, POP, TPD firmware, updates, UI messages, and thermal data.
• Tuner and Radio: TUN, PRS, PRM, and model-specific RDS, DAB, XM, SIRIUS, and HD Radio commands.
• Advanced Calibration: AEO, DSS, DBC, PCT, PCP room correction and phase control.
• Security and Locking: KYL, IRL front-panel and IR lockout.
• Network and Streaming Control: NTC, NAT, NAL, NTI, NTM, NTR, NST, NMS, NLS, NLA, NLT, NJA, NSV, NKY, NPU, NCP, NDS, NBS, NRI transport keys, menu navigation, playback status, metadata (artist/album/title), list rendering, album art, service selection, on-screen keyboard input, popup UI messages, device/network status, and receiver capability discovery.

Together, these command families provide complete remote control over the device, from basic power and input switching to advanced calibration, HDMI diagnostics, and UI interaction. ISCP exposes nearly every function of the receiver.

The ISCP specification has evolved steadily since its first release (v1.00) in 2003^[1], primarily to track new receiver generations, expand command coverage, and adapt to emerging control technologies. Early versions focused on basic serial control, while later revisions broadened support across the full product range and introduced new functional domains such as multi-zone control, dock integration, and network-based operation.

A major milestone occurred in 2011^[1] (v1.19) with the introduction of the Auto Detect Protocol over Ethernet, marking ISCP's transition from a purely point-to-point serial protocol into a network-aware control system. Subsequent versions refined eISCP behavior, standardized discovery, and added support for modern features such as RIHD, network audio, USB playback, Chromecast built-in, Play-Fi, and advanced surround formats.

From 2012 onward^[1], most updates focused on:

• Reorganizing command groups for RI, PORT, and NET/USB domains
• Extending command sets for emerging features (streaming, triggers, display data)
• Refining parameters and descriptions for consistency across model lines

In recent years^[1], updates have become more incremental, reflecting protocol maturity. Versions from 2019 onward mainly introduce:

• Minor structural or descriptive refinements

The latest revisions (2023–2025)^[1] demonstrate that ISCP remains actively maintained.

This chapter provides an overview of known Integra, Onkyo and Pioneer products that implement eISCP.^[6]

• RS-232
• Home automation
• Onkyo

• Home Assistant, Onkyo
• Homey, Onkyo Receiver
• Android Enhanced Music Controller lite (onpc)
• Android Enhanced Music Controller (onpc)
• IOS Enhanced Music Controller
• OpenHAB addon Onkyo

• GitHub: go-onkyo
• GitHub: mkulesh/onpc (Enhanced Music Controller)
• GitHub: Python3 library aioonkyo (Used by Home Assistant)
• GitHub: eISCP to RS232 ISCP bridge eiscp_bridge
• GitHub: eISCP to MQTT bridge eiscp2mqtt