2.2.6 Information ........................................................................................................................................ 5
3 Command List .............................................................................................................................................. 6
5.1 Communication Control .......................................................................................................................... 21
5.1.1 Communication Start ...................................................................................................................... 21
5.1.2 Control Sequence ........................................................................................................................... 21
5.1.3 Communication Errors .................................................................................................................... 21
5.1.4 Communication End ........................................................................................................................ 21
This document describes the command specifications to control the Wireless System charger developed in
Audio-Technica.
The following table shows the definition of terms used in this document.
Ter m Description
Host A device that issues control commands. It refers to application software or a
control device.
Device A device to be controlled.
AT device An Audio-Technica product device.
Message A character string transmitted per communication in data format.
Command A command statement to control a device. It is included in a message.
Parameter Used in combination with a command. It is a setting value that specifies a
command behavior.
The numeric representation is defined as follows:
Binary number: Specify a value followed by b. Example: 1010 0110b
Hexadecimal number: Specify a value preceded by 0x. Example: 0xA6
1
Page 5
2 Basic Specifications
The update function updates the Wireless System via TCP protocol.
Table 2-1 Communication Interfaces
No Item Content Remarks
1. Communication
system
2. Transmission
speed
3. Port number
4. Maximum data
length
5. Compatible
connector
Full duplex
10Mbps / 100Mbps
TCP (control): 17300
UDP (notification): 17000
287 bytes (including line
feed codes)
Device side: RJ45
connector (compatible
with 10/100 Mbps)
Cable: CAT5e or higher
Each port number is fixed and cannot be
changed.
32 bytes for Ethernet communication
header, 255 bytes for control commands
Transmitted commands are categorized as follows:
Table 2-2 Communication Interfaces
No Command Content Remarks
1. Set Command Action command Change the charger settings.
2. Get Command Action command Obtain the charger settings and status.
3. ACKAcknowledge Respond to a Set Command.
4.
NAK
5. AnswerSetting change notification Respond to a Get Command.
6. Information Status change notification Report the charger settings and status
7. Req Command Action request Request an action to the host.
Negative acknowledge Respond to a Set Command.
① For delimiter, half-width space (␣:0x20) will be used.
② Commands use basically ASCII code. For specific commands UTF-8 is used (Example: Device naming
・・・ means space
↲・・・ means CR(0x0d)
・・・ means command parameter
The table below shows command protocol of the action commands.
Table 2-3 Command protocol of action commands
No. Item ContentSize Remarks
1. Command Command string 5byte Refer to “3.Table of commands”
2. Handshake
Select
3. Model ID Unused 4byte Fixed 0000
4. Unit No Unused 2byte Fixed 00
5. Continue
Select
6. Parameter Command parameter 0byte~ Refer to chapter4
7. End Character Sign for end of message 1byte CR (0x0D)
When a command is sent by the host, the following parameters can be abbreviated. This is done by using
comma (,) punctuation for unspecified data.
Example. When a whole abbreviation of the parameter
Sequence execution
system
Divided message system 2byte NC: No divided message
1byte H: Handshake method (Unused)
O: One-Way method
S: ACK/NAK format
CS: Head of divided message
CM: Divided message
CE: End of divided message
sprchS000000NC,,,,,,,,, ↲
However, depending on the command
“Error” can occur when a whole abbreviation of the parameter
“Unspecified” can occur when no abbreviation of the parameter
Cases above and parameters which cannot be abbreviated are described by each command from chapter
4.2 on.
Below, is the acknowledgment command format.
Table 2-4 Response to the acknowledgment command format
No Item Contentsize Remarks
1. Command Command string 5byte Refer to “3.Table of commands”
2. ACK ACK 3byte Fixed ACK
3. End Character Sign for end of message 1byte CR (0x0D)
3
Page 7
Below, is the negative acknowledgment command format.
Table 2-5 Response to negative acknowledgment command format
No Item Contentsize Remarks
1. Command Command string 5byte Refer to “3.Table of commands”
2. NAK NAK 3byte Fixed NAK
3. Error Code Error code 2byte Refer to Table 2-6
4. End Character Sign for end of message 1byte CR (0x0D)
Below, are the error codes.
Table 2-6 Error Code
Error code Error content Remarks
01 Grammar error
02 Invalid command
03 Divided
Transmission Error
04 Parameter error
05 Transmit timeout Unused
90 Busy Unable to process due to busy state
92 Busy (Safe Mode) Unable to process due to p-Fail (power interruption)
93 Busy (Extension) Unable to process due to Extension mode (CU link)
99 Other errors Other errors than above
・ No mandatory request
・ Failure in mandatory request command string
・ Defined length of a command string is not appropriate
・ Max. length of command string including line feed code is
exceeded
・Cannot find command
(Refers to an unknown command or a command, which the device
cannot use.)
・Referred to “CM” or “CE” in a state, when “CS” Continue Select
is not received.
・ Refers to an invalid RX
・ Parameter is out of the defined range
・ When trying to change a parameter, which cannot be changed
(i.e. change “Priority” during talk,...)
Below, is the setting status notification.
Table 2-7 Command format of setting status notification
No Item Contentsize Remarks
1. Command Command string 5byte Refer to “3.Table of commands”
2. Model ID Unused 4byte Fixed 0000
3. Unit No Unused 2byte Fixed 00
4. Continue
Select
5. Parameter Command parameter 0byte~ Refer to chapter4 and 5
6. End Character Sign for end of message 1byte CR (0x0D)
Divided message system 2byte NC: No divided message
CS: Head of divided message
CM: Divided message
CE: End of divided message
4
Page 8
Below, is the changing status notification.
Table 2-8 Command format of changing status notification
No Item Contentsize Remarks
1. Modify MD 2byte Fixed MD
2. CommandCommand string5byteRefer to “3.Table of commands”
3. Model ID Unused 4byte Fixed 0000
4. Unit No Unused 2byte Fixed 00
5. Continue
Select
6. Parameter Command parameter 0byte~ Refer to chapter5
7. End Character Sign for end of message 1byte CR (0x0D)
Divided message system 2byte NC: No divided message
CS: Head of divided message
CM: Divided message
CE: End of divided message
Below, is the requesting status notification. ( This command is not used for wireless system)
Table 2-9 Command format of c status notification
No Item Contentsize Remarks
1.
2.
3.
4.
5.
6.
7.
Request
Command
Model ID
Unit No
Continue
Select
Parameter
End Character
RQ 2byte Fixed RQ
Command string5byteRefer to “3.Table of commands”
Unused 4byte Fixed 0000
Unused 2byte Fixed 00
Divided message system 2byte NC: No divided message
CS: Head of divided message
CM: Divided message
CE: End of divided message
Command parameter 0byte~ Refer to chapter4
Sign for end of message 1byte CR (0x0D)
5
Page 9
3 Command List
No.
1 Model Info
2
Category
Command
gprmi
gveri
Table 2-10 Command List
Command Name
Model parameter information
acquisition request
Version information acquisition request
Remarks
Obtain the model parameter information.
Obtain the version information.
type
set get info
○
○
Ref.
3 System Setting
4
5 Network Setting
6
7
8
9 Status
10
11 Boot Mode
12 request
snmlb
gnmlb
snetw
gnetw
silog
gilog
gschg
nschg
gmode
rfrst
Name label setting change request
Name label setting acquisition request
Network setting change request
Network setting acquisition request
Log setting change request
Log setting acquisition request
Charge status acquisition request
Charge status notification
Mode acquisition request
Reset request (to factory settings)
Change the name label settings.
Obtain the name label settings.
Change the network parameter settings.
Obtain the network parameter settings.
Change the log settings.
Obtain the log settings.
Obtain the charge status.
Report a change in the charge status.
Obtain the boot mode.
Reset to the factory settings.
○
○
○
○
○
○
○
○
○
○
13
14
rdflp
rrbot
Display flip and flash request (for
identify)
Reboot request
Flip and flash the display.
Reboot the system.
6
○
○
Page 10
4 TCP Communications
To control the Wireless System charger from the host, TCP protocol is used for communications.
The graphic below illustrates the communication control flow of the IP control.
WirelessSystem
PowerON
Se tti ng m ana gement
function
Initialization
Booting
IP Contorl
Host
Wait for defining IP-Address
(IP config mode)
Generate Socket
Wait for Connection
Establish connection from Host
Wait for rece ive
Processing each command
Change of setting or state
After the system start, “Initializing” follows “Waiting for connection”
After established host connection, on “Waiting for connection” follows “Waiting for
The received command will be processed depending on the internal process task and a
If the host will be disconnected, “Waiting for transmission” changes to “Waiting for
Send command from Host
ACK/NAK or Answer
〜〜〜
Disconne ct from Host
〜〜〜
Send informat ion to Host (Multic ast)
Fig. 4-1 Communication Control Flow
transmission”
result (ACK/NAK) will be sent. But because this process is asynchronous, it is also possible
to receive commands during processing (without waiting for ACK/NAK or Answer, the next
command can be sent). Although based on the command, NAK(90:BUSY) can also occur.
connection”
7
Page 11
The host establishes connections with the Wireless System.
Multiple hosts cannot be connected. This is single connection.
Table 2-11 Communication Control Parameters
No Name Default Setting Remarks
1. IP Address Auto
2. Port No 17300
As “Set Command” response, the wireless system sends back ACK/NAK to the source.
<Example> Refer below for chage request of RX parameter setting.
WirelessSystem
Setting management
function
IP contorol
Host
Lock key input
Change
RX param eter
ACK/NAK
Unlock key input
Graph 4-2 Set Command Processing Sequence
In terms of Set Command, when errors like grammar error, parameter failure etc. occur, the command NAK
will sent to the source and run the key input unlock.
Set RX
Parameter
8
Page 12
m
As “Get Command” response, the wireless system sends back Answer to the source.
<Example> Refer below for Receive Parameter Setting Acquisition Request sequence.
WirelessSy stem
Also for Get Command, when errors like grammar error, parameter failure etc. occur, the command NAK
will sent to the source.
Setting manageme nt
function
Refe r to rec eive settin g
Answer/NC
IP control
Get RX
Parameter
Fig. 4-3 Get Command Process Sequence
Host
WirelessSyste
Setting management
funtion
Refer to RX
parameter
(unspecified)
NAK 04
Fig. 4-4 Get Command Process Sequence (NAK)
IP control
Host
Get RX Parameter
9
Page 13
The request command sends whether the command was accepted or not to the sender via ACK/NAK and
then performs the requested process if it was accepted (ACK response).
There is a subsequent command available to send the measurement result to the sender.
[1] Command involving reset
<Example> The sequence of reset request (to factory settings) is shown below.
WirelessSystem
Se tt in g m ana gem ent
function
Refer to
system status
Lock key entry
Ack/Nak
Reset
(Set to factory
settings)
IP c on trol
Request Reset
Disconnect with reset
Fig. 2-5 Request Command Process Sequence (Command Involving Reset)
* For NAK responses (telegraphic error, system busy status, etc.), the system is not reset.
Key entry is also unlocked.
Host
10
Page 14
Refer below, in case of ACK/NAK transmitting error sequence.
Wire lessSystem
Host
Change RX parameter
ACK/NAK
IP contorol
Set RX Param eter
Sendinng error
×
Timeout
Disconnect from Host
Fig. 2-6 Transmitting Error Sequence
Refer below, in case of ACK/NAK receiving error sequence.
Wire lessSystem
Setting ma nagement
function
IP control
Host
Indicate
"error"
Receive error
×
Set RXPara m eter
Disconnect
Fig. 2-7 Receiving Error Sequence
Devided Message is not used for IP control.
The host can disconnect at a random timing while ending the communication.
When a disconnection occurs, the Wireless System clears the status of the applied connection (eg. While
sending a file, etc.) and transitions to “Waiting for connection”. Further, the same process applies also
in case of a disconnected cable etc.
In case of a repeated communication, the host establishes a connection.
11
Disconnect
Indicate
"error"
Page 15
The following example represents the correspondence between a command to send and the command format table.
See the table and change the value to desired one in each parameter.
IP address acquisition method: Static
IP address: 192.168.0.30
Subnet mask: 255.255.255.0
Gateway: 192.168.0.1
Automatic device detection setting: Off
Notification enable: On
Notification by charge rate change: On
Notification by charge time change: Off
Multicast address: 225.0.0.100
Multicast port number: 17000
NTP enable: On
NTP server address: 172.16.13.15
NTP server port number: 8000
Timezone (time difference from UTC): +1300
DST enable: On
Start time: 7/1 00:00
End time: 9/30 23:30
Device ID: 101
6 ParameterParameter
IP SettingIP settings
IP Config modeIP address acquisition method s tring0Auto
IP addressIP addressstringnnn.nnn.nnn.nnn
Subnet mas kSubnet maskstringnnn.nnn.nnn.nnn
Gatew ayGateways tringnnn.nnn.nnn.nnn
Allow Discovery
IP Control Notif ic ationIP c ontrol notification s etting
NotificationNotification enablestring0Off
Charge Rate
Charge Time
Multic ast AddressMulticas t addres sstringnnn.nnn.nnn.nnn
Multic ast Port NoMultic ast port numberstr ingnnnnn1 to 65535
NTP Serv erNTP ser v er se tt in g
NTPNTP enablestring0Off
NTP Server A ddressNTP server addressstringnnn.nnn.nnn.nnn
NTP Server Port NoNTP serv er port numberstringnnnnn
Time Zone
Daylight Saving TimeDaylight saving time setting
DSTDST enablestring0Off
St ar t Dat eTi meS ta rt times tr ingMMDDHHmm
End Dat eTimeEn d times tr ingMMDDHHmm
Device IDDevice IDstringnnn0 to 255
7 End CharacterMessage end charac terbinary
Automatic device detecti on setting
Notification by char ge rate
change
Notification by char ge time
change
Timezone ( time dif ference
from UTC)
string0Off
string0Off
string0Off
s tr ing+HHmm
1Static
1On
1On
1On
1On
1On
1-digit sign (+/-) +
hour/minute string
(HHmm)
1On
↲
CR(0x 0d)
↲
12
Page 16
The charger that received the model parameter information acquisition request sends the model parameter information to the host via Answer.
[1] Get Command
The command format of the model parameter information acquisition request is shown below.
2 Handshake SelectSequence ex ecution method stringO
3 Model IDNot usedstring0000Not used
4 Unit NoNot usedstring00Not us ed
5 Continue SelectMes sage s plit methodstringNCNo split
6 ParameterParameter
0: All connec ted chargers
1: Parent charger
2 or above: Connected child charger ID
0: All char ger ports
1 or above:
CHG3 has 2 charging ports , and the one w ith
the pow er LED is port 1.
* The charging port can be specified only
w hen the charger number is set to other than
0.
Charger NumCharger number to obtainstringnn
Port Number
Charging port number to
obtain
stringn
2-digit decimal number
0~
1-digit decimal number
0~
7 End Charac terMes sage end c haracterbinary
[2] Answer
The Answer command format from the charger is shown below.
[Example] Child charger 1 port 2 gschg000000NC1,2,2,1,0,0,0,36 ↲
[Example] Parent charger all ports gschg000000NC1,1,1,0,2,1,0,0,0,0,0,2,1,0,0,0,18 ↲
[Example] All chargers all ports gschg000000NC4,1,1,0,2,1,0,0,0,0,0,2,1,0,0,0,18,2,1,0,2,1,1,0,0,0,102,2,1,0,0,0,36,
Refer to [2] in Network Parameter Setting Change Request.
Table 2-31 Command Format
↲
Table 2-32 Command Format
1FlashOnly the pow er LED flashes .
2FlipSpare spec ification (not currently used)
3All flashEv en the char ge status LED flashes.
↲
Table 2-33 Command Format
↲
CR(0x 0d)
CR(0x 0d)
CR(0x 0d)
20
Page 24
5 UDP Communications
The information (status change notification) from the charger is sent via UDP protocol.
The communication control flow is the same as in 4.1 Communication Control in the Wireless System IP Control Protocol Specification.
The host registers groups to the multicast address.
No Name Default Setting Remarks
1. IP Address 225.000.000.100 Multicast address
2. Port No 17000
If the state of the wireless system changes, the below State Change Notification will be executed.
<Example> Refer below for a RX parameter setting change notification sequence.
Table 5-1 Communication Control Parameters
Wirele ssSystem
Setting manageme nt
function
Change RX parameter setting
RX Parameter
Notice
IP control
Host
Fig. 5-1 Information Command Process Sequence
The details are the same as in 4.1.3 Communication Errors in the Wireless System IP Control Protocol Specification.
The host can unregister groups at any timing.
21
Page 25
The charge status notification sends data to each port according to the following rules when notification enable is set to 1 (On) in the network parameter
settings.
• The charger status or error status changes.
• The charging port status, error status, or charge status changes.
• The charge rate changes when notification by charge rate change is set to 1 (On) in the network parameter settings (for future use).
• The charge time changes when notification by charge time change is set to 1 (On) in the network parameter settings.
[Example] Child charger 3, port 2 MDnschg000000NC1,4,1,0,1,2,0,0,0,0,0 ↲
[Example] Child charger 4, port 2 MDnschg000000NC1,5,1,0,1, 2,1,0,1,0,150 ↲
[Example] Child charger 2 MDnschg000000NC1,3,0,0,0 ↲
* The status of each charger shown in the examples above is as follows: