Greetings:
I've had a M1KE for just a little under two weeks. I primarily use Allstarlink, and have noticed a few odd things, which I will try to address all at once in this post.
Transmission bouncing:
I very often need to press the PTT a few times, because the M1KE bounces the key on press. In other words, it transmits for maybe a quarter of a second, then acts as if the PTT has been released. This happens with or without PTT latch, and only on Allstarlink, even on nodes that are on the same LAN as the M1KE, with a solid -52 DBM Wi-FI signal. I have noticed that it will bounce occasionally when unkeying, too. In other words, if you unkey the M1KE, the transmission will drop as expected, but then it will send another very short transmission, too short to hear, but it shows up on the Allstarlink node console, and will play a courtesy tone if one is enabled. This happens at the end of maybe one in every ten transmissions.
It also, for whatever reason, sends a quick transmission to a node when first connecting without pressing the PTT, but only sometimes.
Audio fragments at the end of RX:
If a station unkeys from an Allstarlink node, I almost always hear a tiny fragment of what sounds like a buffer being played back twice, about a second apart. So, the transmission ends. A second later, I hear a burst of audio that lasts maybe 100 to 200 ms. Then a second later, I hear that same small burst of audio again. Then the RX tone finally plays 3 seconds after the transmission actually ended.
Delayed audio:
I've noticed that RX audio is about three quarters of a second behind all my other nodes. I suspect this is due to something about the way DSP processing works. I didn't observe any difference after disabling loudness and EQ in settings > speaker FX, however.
Occasional call sign truncation when in node mode:
I've also observed that, when using node mode, for some reason, a "node" of the user's call sign is connected to the registered node specified in the Allstarlink/IAX2 connector. Why this is, I'm not sure, since that isn't necessary for a node connection.
Sometimes, the first character of that call is truncated, which becomes a real problem if the call is a 1X9, for example, N9DYI. All Allstarlink nodes treat any node starting with the number 9 as a ranger, which causes a special courtesy tone to play on Allstarlink nodes after each local transmission. When a call like this gets truncated, it then shows up in app_rpt's alinks variable as a node starting with a 9. So, N9DYI is connected to node 508427, which is connected to node 55553. However, N9DYI is now truncated to 9DYI, which causes all nodes connected to 55553 to assume that 9DYI is a ranger, and thus, anyone who unkeys their node will get 6 beeps followed by the normal courtesy tone if those are enabled on the node.
This only happens in node mode, by the way, and not 100% of the time.
Reconnects:
Most of the time, when I first turn M1KE on if it has been left in an Allstarlink profile, it connects, stays connected for about a minute, then reconnects.
Those are the obvious things I've noticed so far.
Currently running Beta 36, but this behavior has been persistent since V32, the first version I used.
73
N2DYI
