[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-users] Re transmission try no response
From: |
Fred39 |
Subject: |
[lwip-users] Re transmission try no response |
Date: |
Wed, 6 Jun 2012 06:50:05 -0700 (PDT) |
Hi LWIP Users
I finaly got the lwip stack working on my device. The problem was that i
didnt set memory options well ,too less memory.
My application using the modbus tcp protocol and after a while I get an
Retransmission try (4 Times) from my PC to the device and than my device
stops to response to the pc. This happends when in various times sometimes
after 1 hour sometimes after 10 min and sometimes after 30seconds.
Can this still be an configuration error of the stack? Still to less memory?
My device drive end up in a can_send loop of the ethernet driver.
Here a trace from wireshark
152950 8727.023524 192.168.1.1 192.168.1.222 Modbus/TCP 66
query [ 1
pkt(s)]: trans: 90; unit: 0, func: 6: Write single register.
152951 8727.325545 192.168.1.1 192.168.1.222 Modbus/TCP 66
[TCP
Retransmission] query [ 1 pkt(s)]: trans: 90; unit: 0, func: 6:
Write single register.
152952 8727.922536 192.168.1.1 192.168.1.222 Modbus/TCP 66
[TCP
Retransmission] query [ 1 pkt(s)]: trans: 90; unit: 0, func: 6:
Write single register.
152954 8728.066608 192.168.1.1 192.168.1.222 TCP 54 51651 >
asa-appl-proto
[FIN, ACK] Seq=1081 Ack=1069 Win=63172 Len=0
152956 8729.129649 192.168.1.1 192.168.1.222 Modbus/TCP 66
[TCP
Retransmission] query [ 1 pkt(s)]: trans: 90; unit: 0, func: 6:
Write single register.
Any Suggestions?
Regards
Fred
--
View this message in context:
http://old.nabble.com/Retransmission-try-no-response-tp33970148p33970148.html
Sent from the lwip-users mailing list archive at Nabble.com.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [lwip-users] Re transmission try no response,
Fred39 <=