XMODEM: The first packet is sent out twice by using the xmodem sending function. Still not fixed

• Auswertung: (Anonym)
• Verantwortlicher: (Keine)
• Typ: Fehler
• Status: Geschlossen
• Komponente: Tera Term
• Meilenstein: Tera Term 4.107
• Priorität: 5 - Mittel
• Schweregrad: 5 - Mittel
• Lösung: Gefixt
• Datei: Keine

Details Antworten

Xmodem send the first packet twice if more the one NAK was received before the transfer begins. Some tickets describes this issue. Looks like in the receive buffer a left NAK is inside.

Ticket-Verlauf (3/7 Historien)

2014-04-24 21:16 Aktualisiert von: None

• New Ticket "XMODEM: The first packet is sent out twice by using the xmodem sending function. Still not fixed" created

2014-04-27 19:59 Aktualisiert von: (del#24082)

• Komponente Update from (Keine) to Tera Term
• Verantwortlicher Update from (Keine) to yutakapon

Kommentar Antworten

I can not investigate your problem because your phenomenon can not be reproduced in my environment. Please retrieve the XMODEM.log file by using the XmodemLog is ON in the teraterm.ini file.

Thanks.

2014-06-01 23:16 Aktualisiert von: (del#24082)

• Priorität Update from 7 to 5 - Mittel

2014-09-08 19:12 Aktualisiert von: None

Kommentar Antworten

Here is the XMODEM LOG from TeraTerm with some comments.

---

<<< 15 (The Xmodem Receiver is started and waiting for Xmodem sender and sends 0x15 each second... Important now: In this case 4 times 0x15 was send before the first packet is transmitted, but only the first 0x15 in the sender input buffer is read and used....) .

>>> 01 01 FE 00 7F 00 10 01 0B 04 00 A1 0B 04 00 A9 ................ 0B 04 00 19 0C 04 00 21 0C 04 00 29 0C 04 00 52 .......!...)...R 3A E7 EF 00 00 00 00 00 00 00 00 00 00 00 00 71 :..............q 4F 05 00 31 0C 04 00 00 00 00 00 75 50 05 00 B1 O..1.......uP... 50 05 00 39 0C 04 00 39 0C 04 00 39 0C 04 00 39 P..9...9...9...9 0C 04 00 39 0C 04 00 41 56 04 00 E9 57 04 00 91 ...9...AV...W... 59 04 00 6D 5B 04 00 71 67 04 00 F9 6D 04 00 39 Y..m[..qg...m..9 0C 04 00 85 72 04 00 39 0C 04 00 31 66 04 00 D1 ....r..9...1f... 66 04 00 81 f...

<<< 15 15 15 ( The first packet was send now an the answer from the RECEIVER is checked. !! BUT NOW THE second 0x15 is read and the sender is thinking the packet was wrong transmitted. The correct answer 0x06 is really transmittet but it is behind the 0x15 bytes in the input buffer!!. The Answers from NOW are ALWAYS one packet to late. That means a 0x15 answer from e.g. packet #15 is read after sending packet #16. And now the sender is thinking packet #16 was wrong and sends it again, and again, and again. But the receiver still is waiting for the packet #15. ...

For Testing you must have a Xmodem receiver who is waiting for file receiving AND is sending SOME 0x15 to the Teraterm BEFORE the xmodem transfer is started because you first have to select a file to send in Teraterm. Depending how long you need to find the file more or less 0x15 will be received while you search the file. The second 0x15 is interpreted as answer for the first packet.

I Hope that helps. I have no more idea to explaine that issue. Its hard to understand until it makes CLICK in the brain :-))

>>> 01 01 FE 00 7F 00 10 01 0B 04 00 A1 0B 04 00 A9 ................ 0B 04 00 19 0C 04 00 21 0C 04 00 29 0C 04 00 52 .......!...)...R 3A E7 EF 00 00 00 00 00 00 00 00 00 00 00 00 71 :..............q 4F 05 00 31 0C 04 00 00 00 00 00 75 50 05 00 B1 O..1.......uP... 50 05 00 39 0C 04 00 39 0C 04 00 39 0C 04 00 39 P..9...9...9...9 0C 04 00 39 0C 04 00 41 56 04 00 E9 57 04 00 91 ...9...AV...W... 59 04 00 6D 5B 04 00 71 67 04 00 F9 6D 04 00 39 Y..m[..qg...m..9 0C 04 00 85 72 04 00 39 0C 04 00 31 66 04 00 D1 ....r..9...1f... 66 04 00 81 f...

<<< 06 .

>>> 01 02 FD 39 0C 04 00 39 0C 04 00 39 0C 04 00 39 ...9...9...9...9 0C 04 00 39 0C 04 00 39 0C 04 00 39 0C 04 00 39 ...9...9...9...9 0C 04 00 39 0C 04 00 39 0C 04 00 39 0C 04 00 39 ...9...9...9...9 0C 04 00 39 0C 04 00 39 0C 04 00 39 0C 04 00 39 ...9...9...9...9 0C 04 00 39 0C 04 00 39 0C 04 00 39 0C 04 00 A8 ...9...9...9.... 45 06 00 00 00 00 10 AC 06 00 00 9C 45 06 00 00 E...........E... C0 07 20 0C 00 00 00 B0 06 00 10 68 5C 00 00 0C .. ........h\... C0 07 20 00 15 00 00 FF FF FF FF FF FF FF FF FF .. ............. FF FF FF 80 ....

<<< 06 .

>>> 01 03 FC FF FF FF FF FF FF FF FF FF FF FF FF FF ................ FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................ FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................ FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................ FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................ FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................ FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................ FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................ FF FF FF 80 ....

<<< 06 .

2015-11-07 21:04 Aktualisiert von: (del#24082)

• Verantwortlicher Update from yutakapon to (Keine)

2021-12-30 02:14 Aktualisiert von: zmatsuo

Kommentar Antworten

Received patch (ticket #43221) and adapted patch (r9654).

The xmodem problem has been fixed.

2021-12-30 02:14 Aktualisiert von: zmatsuo

• Status Update from Offen to Geschlossen
• Lösung Update from Keine to Gefixt
• Meilenstein Update from (Keine) to Tera Term 4.107