Product : KNOT RB9241i 2nd + BT5&BG77
Label MAC address says :
E01 : 2c c8 1b .. .. A6
W01 : 2c c8 1b .. .. A8
When connecting via E01, it gets a valid IP address via DHCP, but DHCP server reports 2c c8 1b .. .. A7
Scanning with /tools IP from another RouterOS confirms the same MAC
Connecting via Winbox fails either via MAC or IP. Factory reset fails.
Any explanation on what is happening here? Thankyou,
Short update: managed to get KNOT in netinstall mode. I installed routeros-mipsbe-7.2.3b.npk, which worked, then installed the packages:
lte-7.2.3-mipsbe.npk
iot-7.2.3-mipsbe.npk
gps-7.2.3-mipsbe.npk
[obsolete , see next post]
But after all this, there is no USB port to be found, only : Modem and Modbus.
There is one critical error message :
error while running customized default configuration script: interrupted
without further detail
How would you proceed to add the USB port ?
Model : RB924i-2nD-BT5&BG77 Factory firmware
FYI, the port ifor the BG77 used to be USB, but is now called MODEM and on data/infochannel 2
I tried to find this port change from USB to MODEM in the documentation, but I was not able to find that. Either it does not exist, or I did not look well enough.
PPP info : BG77 : LTE Cat-NB1 gives vodafone directly, but a scan takes ages and does not give any result.
The GPS is on port MODEM and data channel 1, init channel 2
GPS data looks fine, but modem gives a lot of “Modem did not respond”, only after reboot is will accept any AT commands.
You can have a quick view on GPS data via /system serial-terminal port=modem channel=1
Next hop : decode HEX from the TG-BT-XX tokens to fetch the temperature only and send over MQTT.
Does anyone have a sample script that extracts this from the hex payload as described in https://help.mikrotik.com/docs/display/UM/MikroTik+Tag+advertisement+formats#heading-MikroTikPDUPayloadstructure ? I would prefer to decode the needed data on the knot instead of relying on the target MQTT handler/pipeline.
@mikrotik, if you have a hex decoder, why not add it to the sample script that you provide at https://help.mikrotik.com/docs/pages/viewpage.action?pageId=63045633#heading-MQTTPublishwithascript ?
Thank you,
The port should be called a “modem”.
Please make sure that the issue is not relevant on the latest stable v7 release.
We have added a new script to the “PDU structure” guide:
https://help.mikrotik.com/docs/display/UM/MikroTik+Tag+advertisement+formats#heading-Scriptfordecoding
The script should decode the payload and print it into the command line interface.
You can alter this script further to structure a message out of the “decoded” values.