Announcement

Collapse
No announcement yet.

Only sometimes connect the COM port redirector to the xPico

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Only sometimes connect the COM port redirector to the xPico

    Hello,
    The serial interface of my application for home automation is addressed using CPR 4.3.0.1. This works with an XPORT without problems.
    The xPico (FW 1.4.0.0R28, Protocol "Tunnel") can not be used because the CPR may initiate communication with UDP requests.

    --Wireshark--
    No. TimeSource SrcPort Destination DstPort Protocol Length DataInfo
    **4 0.780147 192.168.0.69 43282 192.168.0.210 30718 UDP 60 000100f6 43282 → 30718 Len = 4
    **5 0.780472 192.168.0.69 43282 192.168.0.210 30718 UDP 60 000000f6 43282 → 30718 Len = 4
    **6 0.780692 192.168.0.69 43282 192.168.0.210 43282 UDP 60 0101000000ff0000 43282 → 43282 Len = 8
    **7 4.293377 192.168.0.69 43282 192.168.0.210 30718 UDP 60 000000f6 43282 → 30718 Len = 4
    **8 4.293543 192.168.0.69 43282 192.168.0.210 30718 UDP 60 000000f6 43282 → 30718 Len = 4
    **9 4.293850 192.168.0.69 43282 192.168.0.210 43282 UDP 60 0101000000ff0000 43282 → 43282 Len = 8
    ----

    The xPico does not respond, according to "Diagnostics> IP Sockets" he listen only with interface ap0 and on UDP port 53 and 67.
    Sometimes, however, the CPR skips this UDP header, sends/receives instant TCP data, and then also connects to the xPico.

    How can I get the CPR to work with the xPico?

    Thanks for your help!
    Golter

    ~~~
    Edit:
    Reply/answer of Mariano see:
    forums.lantronix.com/showthread.php?t=1319 in post #3 (my question #2) and post #4 (answer #2).
    Last edited by Golter; 03-19-2017, 02:02 PM. Reason: Answer in other threat
Working...
X