CW message auto tx broken in 1.02w

[mautas]

I'm trying out the CW auto tx function in 1.02w. It doesn't work, just shows a 0 in the display and exits. I don't know if this is not yet implemented in this version (a note in the definition header would have saved me and other people some time) or if it was working but it was seriously broken in this version.

[threeme3]

Yes it should work. Please try to do a factory reset by holding the encoder button while powering it up, and try again.

[mautas]

It doesn't, I checked out the code and all it does when it enters the CW message Tx loop is print a 0 in the screen and then exits the loop. I tried to understand the code (ie. why does it leave the loop so fast) but its kind of hard to understand how it works. ᐧ El mié, 1 de dic. de 2021 a la(s) 08:55, threeme3 ***@***.***) escribió:

…

Yes it should work. Please try to do a factory reset by holding the encoder button while powering it up, and try again. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#58 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHJROKTEQ7EIRHROXVCPZUDUOYEMPANCNFSM5IACDW7Q> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[threeme3]

Ok, the CW message will stop as soon a button or a dit/dah I sent. Maybe there is RF feedback on one of these inputs, interrupting the CW Message process.