If you like BoxMatrix then please contribute Supportdata, Supportdata2, Firmware and/or Hardware (get in touch).
My metamonk@yahoo.com is not reachable by me since years. Please use hippie2000@webnmail.de instead.
Property:alw lifetest example
BoxMatrix >> Shell-Commands >> alw_lifetest_example | @ BoxMatrix - IRC-Chat - Translate: de es fr it nl pl |
News | Selectors | Models | Accessories | Components | Environment | Config | Commands | System | Webif | Software | Develop | Lexicon | Community | Project | Media |
Startup-Scr | Hotplug-Scr | BusyBox-Cmds | Bash-Cmds | AVM-Cmds | Chipset-Cmds | Linux-Cmds | Shared-Libs | Kernel-Mods | Research |
AVM-Command
Command: | alw_lifetest_example - type Exec | Wiki | Freetz | IPPF | whmf | AVM | Web |
Location: | Shell-Commands >> AVM-Commands - Origin: AVM | ||||||
Path: | Release: /usr/bin Lab+Rel: /usr/bin | ||||||
Properties: | Size: 9.4k - 13.6k - Firmware: 7.63 - 7.90 | ||||||
Function: | ZigBee lifetest packet capturing example. |
Goto: Dependencies - Model-Matrix - Symbols - SMW-Browser
Details
alw_lifetest_example is a ZigBee lifetest packet capturing example.
It is not used by the system and likely an internal tool used for lifetest during Production-Test.
It uses 4 functions of libalwudsmsg.so (6670 fw 7.90):
- alw_uds_reconnect_socket
- alw_uds_send_message
- alw_uds_wait_specific_msg_with_reconnect
- alw_uds_msg_log_function
The first 3 are for communication with the ZigBee Network Co-Processor, the last one starts the capturing.
The console output may look like this:
alw_lifetest: [<string>:<num>] CLI will be terminated Stack is started, proceeding with lifetest Lifetest capture started. Waiting for indication... Lifetest ended with state: success Captured packets: <num>, avg. RSSI: <num>, avg. LQI: <num>
Where the capture is stored (if at all) is unknown. Since alw_lifetest_example does not provide a help function
this may be passed in arguments. Maybe there's no dump at all and the result is just the success in receiving the indication.
However, this tool does not seem to be of any use for developers, it's even called an example, a proof of concept.
The real Production-Test of this function seems to happen in psupportd, its source shows it includes test_zigbee_life.c
.
Dependencies
Daily updated index of all dependencies of this command. Last update: 2024-11-14 07:42 GMT.
A *
in the Mod
column marks info from Supportdata-Probes, which will always stay incomplete.
Relation | Typ | Object | Mod | Firmware | Info | Origin |
---|---|---|---|---|---|---|
Depends on | lib | libalwudsmsg.so | 4 | 7.63 - 7.90 | ZigBee protocol messaging library | AVM |
Depends on | lib | libc.so | 4 | 7.63 - 7.90 | Standard C library | Linux |
Depends on | lib | libminneapolis.so | 4 | 7.63 - 7.90 | Minneapolis datastore encoder / decoder | AVM |
3 dependencies for this command |
Model-Matrix
Daily updated index of the presence, path and size of this command for each model. Last update: 2024-11-15 05:53 GMT.
Showing all models using this command. Click any column header (click-wait-click) to sort the list by the respective data.
The (main/scrpn/boot/arm/prx/atom/rtl)
label in the Model
column shows which CPU is meant for Multi-Linux models.
Note that this list is merged from Firmware-Probes of all known AVM firmware for a model, including Recovery.exe and Labor-Files.
Model | Firmware | Path | Size |
---|---|---|---|
FRITZ!Box 5690 Pro (main) | 7.90 | /usr/bin | 9.4k |
FRITZ!Box 6670 Cable (atom) | 7.90 | /usr/bin | 13.6k |
FRITZ!Box 7690 | 7.90 | /usr/bin | 9.4k |
FRITZ!Smart Gateway | 7.63 | /usr/bin | 9.4k |
4 models use this command |
Symbols
Daily updated index of all symbols of this command. Last update: 2024-11-14 07:42 GMT.
Firmware | Symbol |
---|---|
0 symbols for this command |