slac_simulator.1 7.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189
  1. .TH slac_simulator 1 "Oct 2021" "plc-utils-2.1.19" "Qualcomm Atheros Powerline Toolkit"
  2. .SH NAME
  3. slac_simulator - Qualcomm Atheros Plug-in Electric Vehicle Emulator
  4. .SH SYNOPSIS
  5. .BR slac_simulator
  6. .RI [ options ]
  7. .SH DESCRIPTION
  8. Emulate the PEV part of the HomePlug AV Signal Level Attentuation Characterization (SLAC) protocol where a \fBPEV\fR is a "\fBPlug-in Electric Vehicle\fR" and an \fBEVSE\fR is an "\fBElectric Vehicle Supply Equipment\fR" or charging station.
  9. This program will remain active until it detects and connects to an available EVSE-HLE on the powerline network.
  10. It has a different state machines for each stage of SLAC and move to diferent states based on received slac or HAR messages.
  11. This utility provides an option to specify the charge time.
  12. Once connected to EVSE-HLE, it charges a virtual vehicle for specified time then disconnects and terminates.
  13. This program has the capability to identify the device in bootloader mode and could write firmware and parameters to PEV as referenced in option \fB-N\fr and \fB-P\fr
  14. See the \fIHomePlug Green PHY Specification Release Version 1.1\fR for more information on this protocol.
  15. .PP
  16. Signal Level Attenuation Characterization (SLAC) enables a station to measure the signal level of its transmission at other stations in the network.
  17. It is designed for automotive applications where there are multiple plug-in vehicle (PEVs) and electric vehicle supply equipment (EVSE) on the network.
  18. The PEV signal level is measured at multiple EVSEs to determine which EVSE the PEV is actually plugged into.
  19. The process leading to this determination is called "\fBGreen PHY PEV-EVSE Association\fB" (GreenPPEA).
  20. .PP
  21. This program is part of the Qualcomm Atheros Powerline Toolkit.
  22. See the \fBplc\fR man page for an overview and installation instructions.
  23. .SH OPTIONS
  24. .TP
  25. .RB - c
  26. Print the PEV-HLE configuration profile on stdout.
  27. The configuration profile specifies program defaults in a format that you, as a user, can edit and save.
  28. Use options \fB-p\fR and \fB-s\fR to read named profiles and sections.
  29. .TP
  30. .RB - d
  31. Print the contents of the PEV-HLE session variable on stdout.
  32. The session variable is an program data structure that stores information passed between the PEV-HLE and EVSE-HLE during SLAC association.
  33. This option is used to inspect and veriify information relevant to the process.
  34. If the program was compiled with variable SLAC_DEBUG defined then this option also prints MME message fields before messages are sent or after they are received.
  35. Interested parties can follow along in the source code.
  36. .TP
  37. .RB - F
  38. Write previously downloaded MAC and PIB to NVRAM using VS_MOD_NVM.
  39. .TP
  40. .RB - i
  41. Select the host Ethernet interface.
  42. All requests are sent via this host interface and only reponses received via this host interface are recognized.
  43. The default interface is \fBeth1\fR because most people use \fBeth0\fR as their principle network connection; however, if environment string "PLC" is defined then it takes precedence over the default interface.
  44. This option then takes precedence over either default.
  45. .TP
  46. -\flT \fIloop\fR
  47. Number of times to run slac in loop.
  48. Values range from 0 through UINT_MAX.
  49. The default the loop runs for a single time.
  50. .TP
  51. -\fBN \fIfilename\fR
  52. Use this file to download firmware when requested by the local device.
  53. The file must exist and have a valid NVM file format or it will be rejected.
  54. No assumptions are made based on filename and no filename conventions are enforced.
  55. .TP
  56. -\fBP \fIfilename\fR
  57. Use this file to download parameters when requested by the local device.
  58. The file must exist and have a valid PIB file format or it will be rejected.
  59. No assumptions are made based on filename and no filename conventions are enforced.
  60. .TP
  61. .RB - q
  62. Enter quiet mode.
  63. Progress messages are suppressed.
  64. .TP
  65. -\fBr \fIprofile\fR
  66. The PEV-HLE configuration profile name.
  67. The program will supply default values for missing profile elements.
  68. See the example profile shown below.
  69. The default profile name is "\fBpev.ini\fR".
  70. .TP
  71. -\fBs \fIsection\fR
  72. The configuration profile section name.
  73. The program will supply default values for missing configuration profile elements.
  74. See the example profile shown below.
  75. The default section name is "\fBdefault\fR".
  76. .TP
  77. -\fBS\fIfilename\fR
  78. Use this file to download the softloader when requested by the local device.
  79. The file must exist and have a valid NVM file format or it will be rejected.
  80. No assumptions are made based on filename and no filename conventions are enforced.
  81. .TP
  82. -\fBT \fIseconds\fR
  83. Charging time in seconds.
  84. Values range from 0 through UINT_MAX.
  85. The default is \fB3\fR seconds.
  86. .TP
  87. .RB - v
  88. Enter verbose mode.
  89. All Etherenet frames sent or received by the program are displayed on stdout.
  90. .TP
  91. -\fB?\fR, --\fBhelp\fR
  92. Print program help summary on stdout.
  93. This option takes precedence over other options on the command line.
  94. .TP
  95. -\fB!\fR, --\fBversion\fR
  96. Print program version information on stdout.
  97. This option takes precedence over other options on the command line.
  98. Use this option when sending screen dumps to Atheros Technical Support so that they know exactly which version of the Linux Toolkit you are using.
  99. .SH PROFILES
  100. The default configuration profile for this program is "\fBpev.ini\fR".
  101. The default profile section is "\fBdefault\fR".
  102. Users may create addition profiles and reference them with option \fB-p\fr or add additional sections to an existing profiles and reference them with option \fB-s\fR.
  103. .TP
  104. .B Attenuation Theshold
  105. The average attenuation above which the PEV will not connect to an EVSE.
  106. The default value is \fB10\fRdb.
  107. .TP
  108. .B MSound Pause
  109. The time in milliseconds between each MSound sent by the PEV-HLE to the EVSE-HLE.
  110. Sending MSounds too frequently overloads the EVSE-PLC.
  111. Sending them too infrequently wastes time.
  112. This value is derived and does not appear in the HPGP specification.
  113. The default pause is \fB10\fR milliseconds.
  114. .TP
  115. .B Vehicle Identifier
  116. Vehicle identification.
  117. The 17-byte Vehicle Identification Number to be placed in CM_MNBC_SOUND.IND.SenderID.
  118. This value is not used but is can be changed here so that the field is easy to spot within network message traces.
  119. .TP
  120. .B Network Membership Key
  121. The 16-byte Network Memberhip Key (NMK) for the PEV-PLC device.
  122. This program uses CM_SET_KEY to sets the PEV-PLC NMK to this value after disconnecting.
  123. The default value is the key for Network Password "\fBHomePlugAV\fR".
  124. .TP
  125. .B Network Identifier
  126. The 7-byte Network Identifier (NID) for the PEV-PLC device.
  127. This program uses CM_SET_KEY to sets the PEV-PLC NID to this value after disconnecting.
  128. The default value is the same as that for Network Password "\fBHomePlugAV\fR".
  129. .SH REFERENCES
  130. See the \fIQualcomm Atheros AR7420, QCA6410 IEEE 1901, HomePlug AV and QCA7000 HomePlug Green PHY PLC Chipset Programmer''s Guide\fR or the \fIHomePlug Green PHY Specification Release Version 1.1\fR for more information on this protocol.
  131. .SH EXAMPLES
  132. The following example starts a PEV session on interface \fBeth0\fR and waits for the EVSE to respond. The slac association with EVSE happens 3 times in a loop.
  133. .PP
  134. # pev -ieth0 -l3
  135. .PP
  136. The default PEV-HLE configuration profile, "\fBpev.ini\fR", looks something like this but it can be changed using a normal text editor.
  137. Use option \fB-P\fR to produce a template profile, if one is needed.
  138. This program always do NMK randomization to PEV. So, mentioning NMK and NID in the profiles is not needed.
  139. .PP
  140. # file: pev.ini
  141. # ====================================================================
  142. # PEV-HLE initialization;
  143. # --------------------------------------------------------------------
  144. [default]
  145. attenuation threshold = 10
  146. msound pause = 10
  147. vehicle identifier = AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
  148. network membership key = 50D3E4933F855B7040784DF815AA8DB7
  149. network identifier = B0F2E695666B03
  150. .SH SEE ALSO
  151. .BR plc ( 1 ),
  152. .BR evse ( 1 )
  153. .SH CREDITS
  154. Kalaivani Somasundaram <kalaivan@qti.qualcomm.com>