开云体育

I have programmed my first message into the qmx+, but when I play it back on the air, it appends lots of extra characters at the end. The characters do not appear in the message memory when you view or edit it.

I had this also, just deleted and re-entered the message and that fixed it. Weird.

Is there a straightforward way to delete a message? Any special characters one has to put at the end of a message to prevent this?

?

I had a similar experience. After deleting and re-recording the messages, it has not re-appeared.?

--

73, Dan? NM3A

How do you delete a message?

I figured out how to delete the entire message. Then, I re-entered the message but I am still getting gibberish sent at the end of the message that I did not enter.

The gibberish is K0****AS?

This renders the message function to be useless.?

I hope no one is listening to the CQ I'm sending.?

Buying a pre-assembled unit, I was hoping not to be doing debugging. Oh well.?

Maybe you can try to connect QMX(+) to a computer and enter/clean messages in putty, it's easier and you get visibility of the whole message buffer.

OK, I'll have to find out what software goes with the QMX. So far, seems buggier than an Amish church meeting.?

Hi Braden

Putty is the favoured terminal software, works on Windows and Linux.

73

Roger

8P6RX

Get

Thank you very much! I've never heard of it, but I am not a techie so that's not surprising.?

I also got gibberish characters.? I am a little nervous about broadcasting them again, and can't figure out how to play back the message without transmitting.? When I try it in practice mode, I can't hear anything on the message.?

?

Is there a way to play it back without transmitting?

I got the gibberish as well.? Now I am nervous about broadcasting it.?

?

Is there any way to play back the message without transmitting?? When I try it in practice mode, it won't play?

Dummy load maybe?

I assume you could use the practice mode, and you wouldn't be transmitting.

Jon, also, a couple of things I discovered playing around with this:

1. I deleted Message 1 and re-entered it, but I still got gibberish;

2. I discovered that Message 2 did not add gibberish on the end, as Message 1 consistently does.?

Ghost in the machine.?

By the way, I should clarify that when you look at Message 1 in text form, the gibberish characters do not appear. They only appear as the message is being sent on the air, and they are sent. The couple of times I dared to send Message 1 yesterday, I got the same characters added on at the end, which are: K0****AS

Best regards to all and 73!

Braden,

I agree this is a bug.?

I also had this problem when I first entered and edited messages.

I found a way to fix it from the QMX front panel:

1 - enter the message menu, and select the message to edit it.

2 - using the vol knob, move the cursor to the end of the message, then use the 'backward triangle' char to delete all

3 - fill all of the characters of the message buffer with spaces, by pressing the 'select' button at least 32 times

4 - exit the menu to save the message of spaces.

5 - select the message again, and put in the 'enter' character (looks like a keyboard enter icon) in the first character of the message.

6 - the last three steps got the internals sync'd again, and won't send any extra characters or spaces.

?

I think what is happening is that when using the 'enter' or 'backward triangle' character to delete any unwanted characters, the firmware is only putting in some marker at that position, rather than clearing the buffer.? Then it honors that marker when showing you the message text (either on the front panel or in the terminal message editor), and you can't see the rest of the message buffer.? Then sending the (newly edited) message, that marker is not honored by the firmware for sending the message, and it sends all non-empty characters entered into the buffer and not individually deleted.? And sometimes some of the extra characters are corrupted, causing '*' to be sent.

?

So when a message memory is corrupted that way, you have to clear it out, either by the above procedure, or by using the terminal memory editor.? In the terminal memory editor, you still can't see the extra characters, but if you edit a character in the message, it seems to clear everything out and leave it correct as you see it.

?

BTW, while 'putty' is what most use, it is not necessarily easiest - any terminal emulator app will do (like the old Windows Hyperterm or whatever).? I use TeraTerm, which is also free and friendlier to use (in my opinion) and if you search messages in this group, I recently wrote some details on how to set it up.

Stan KC7XE

?

Stan, thank you for such a detailed dissection of this problem! I'll have to try the fix you described, today, at least the fix that doesn't involve a terminal, as I don't have the extra time (or desire) to become part of some worldwide de-bugging team.

?

In the meantime I have been dealing with this by using Message 2, which doesn't seem to have the problem.?

?

Do you happen to know if there's a list of recognized bugs to be fixed, so we can make sure this one's on it? (I'm assuming if it isn't on the list, it should be).?

Thanks again!

On Fri, Apr 4, 2025 at 05:53 AM, Braden Glett wrote:

Do you happen to know if there's a list of recognized bugs to be fixed,

Hans regularly reads messages posted here, and puts the bugs on his list.? As far as I know such a list is not published.?