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 zb coordinator.log
| BoxMatrix >> Configuration >> alw_zb_coordinator.log | @ 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 |
| Static-Config | Bin-Files | Audio-Files | Crypto-Files | Vartar-Items | TFFS-Config | Temp-Files | Data-Dirs | Inet-Providers | VoIP-Providers | Firmware | Research |
Temp-File
| Temp-File: | alw_zb_coordinator.log - type Log | Wiki | Freetz | IPPF | whmf | AVM | Web |
| Location: | Configuration >> Temp-Files - Origin: AVM | ||||||
| Path: | /var/tmp | ||||||
| Properties: | Firmware: 7.50 - 7.61 | ||||||
| Function: | ZigBee Coordinator log of alw_zb_gw_app | ||||||
Goto: Examples - Dependencies - Model-Matrix - Missing Supportdata - SMW-Browser
Details
alw_zb_coordinator.log is the ZigBee Coordinator log of alw_zb_gw_app.
This file is printed in supportdata.aha if the creation of supportdata.lrwpan fails.
The Coordinator is the master of a ZigBee network and the only one which can form the network topology.
It also chooses the RF channel to use. There can only be one Coordinator (per channel) in a ZigBee network.
ZigBee stack:
- Lexicon: ZigBee, LR-WPAN
- Firmware: zncp-0.2.0.bin, zncp-1.0.0.bin, zncp-1.0.1.bin, zncp-1.0.2.bin
- Firmware: zncp-1.1.1.bin, zncp-1.2.0.bin, zncp-1.2.1.bin
- Devices: ttyACM0, ttyACM1, ttyLRWPAN_NCP, ttyLRWPAN_PTEST
- Sockets: alw_gw_uds.sock
- Sinks: aflrwpan_gw_app
- Commands: alw_zb_gw_app, alw_zb_gw_cli, alw_flash_util, alw_zb_gw_stop
- Commands: supportdata.aha, zb_pcap_dump
- Libraries: liblrwpan.so, libahamodaflrwpan.so, libalwptest.so
- Libraries: libalwncpdfu.so, libalwswdutil.so, libalwudsmsg.so
- Libraries: libcodsu.so, libudev.so, libusb.so, libgpiod.so
- Config: lrwpan.cfg, 95-lrwpan_usb.rules, 95-aflrwpan_usb.rules, alw_zb_gw_app.service
- UI-Modules: lrwpan
- Logs: alw_runtime.log, alw_zb_coordinator.log, alw_gw_crashlog.json
- Temp: supportdata.lrwpan
- Procfs: lrwpan
Examples
fsgw fw 7.57:
root@fritz:/var/mod/root# cat /var/tmp/alw_zb_coordinator.log 0 1970-01-01 01:00:37 0.000 zb_init_ncp.c:141 [INFO1] FFD build 1 1970-01-01 01:00:37 0.000 zb_init_ncp.c:145 [INFO1] sizes: g_zb 13800 sched 1412 bpool 9984 addr 1612 2 1970-01-01 01:00:37 0.000 zb_init_ncp.c:147 [INFO1] zcl 572 3 1970-01-01 01:00:37 0.000 zb_init_ncp.c:156 [INFO1] nvram 144 4 1970-01-01 01:00:37 0.000 zb_init_ncp.c:162 [INFO1] err_ind 4 5 1970-01-01 01:00:37 0.000 zb_init_ncp.c:169 [INFO1] scheduler q size 64 6 1970-01-01 01:00:37 0.000 zb_init_ncp.c:175 [INFO1] ZB_IOBUF_POOL_SIZE 60 7 1970-01-01 01:00:37 0.001 zb_osif_serial.c:110 [ERROR] Using /dev/ttyLRWPAN_NCP as serial interface 8 1970-01-01 01:00:37 0.012 zb_osif_serial.c:206 [ERROR] Using 115200 as baudrate 9 1970-01-01 01:00:40 3.186 alw_zb_coordinator.c:1341 [APP1] Zigbee stack initialized 10 1970-01-01 01:00:40 3.186 zdo_commissioning_bdb.c:352 [INFO1] dev type 0, joined 1, ext_pan_id 1, authenticated 1, tclk_valid 0 11 1970-01-01 01:00:40 3.228 zdo_commissioning_bdb.c:507 [INFO1] COMMISSIONING_STOP: app signal 6 comm status 0 12 1970-01-01 01:00:40 3.228 ncp_host_hl_adapter_zdo.c:1561 [ERROR] > zb_zdo_startup_complete_int param 3 status 0 signal 6 13 1970-01-01 01:00:40 3.228 alw_zb_coordinator.c:1377 [APP1] Device reboot okay 14 1970-01-01 01:00:40 3.229 zdo_commissioning_bdb.c:507 [INFO1] COMMISSIONING_STOP: app signal 10 comm status 0 15 1970-01-01 01:00:40 3.229 ncp_host_hl_adapter_zdo.c:1561 [ERROR] > zb_zdo_startup_complete_int param 4 status 0 signal 10 16 1970-01-01 01:00:40 3.229 alw_zb_coordinator.c:1402 [APP1] Steering done 17 1970-01-01 01:00:40 3.229 alw_zb_coordinator.c:446 [APP1] ZBOSS reported NCP FW version: 1.0.2 (raw 65538) 18 1970-01-01 01:00:40 3.278 aps_group_table.c:93 [ERROR] add group ret: 0
Dependencies
Daily updated index of all dependencies of this temp file. Last update: 2024-04-16 06:30 GMT.
A * in the Mod column marks info from Supportdata-Probes, which will always stay incomplete.
A ** in the Mod column marks info from Supportdata2 probes, which by their nature will stay way more incomplete.
A - in the Mod column marks manual research, the Firmware then shows where the item occurs, not the Relation.
| Relation | Typ | Object | Mod | Firmware | Info | Origin |
|---|---|---|---|---|---|---|
| 0 dependencies for this temp file | ||||||
Model-Matrix
Daily updated index of the presence, path and size of this temp file for each model. Last update: 2024-04-16 06:28 GMT.
Showing all models using this temp file. Click any column header (click-wait-click) to sort the list by the respective data.
The (main/scrpn/boot/arm/prx/atom) label in the Model column shows which CPU is meant for models with multiple Linux instances.
Note that this list comes from Supportdata-Probes, which can have arbitrary settings and come from different firmware versions.
It doesn't say much if a model is not listed here. It may be a missing supportdata file or just a disabled feature.
| Model | Firmware | Path | Size |
|---|---|---|---|
| FRITZ!Box 6670 Cable (atom) | 7.59 - 7.61 | /var/tmp | 1.9k - 10.1k |
| FRITZ!Smart Gateway | 7.50 - 7.57 | /var/tmp | 1.7k - 4.2k |
| 2 models use this temp file | |||
Missing Supportdata
The data in this article is incomplete due to missing Supportdata-Probes for the models listed below.
If you own any of these models and would like to help then please get in touch.
