This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

LM3S6965: PC Software Utility Or Locator unable to locte device in the network

Part Number: LM3S6965

We have been using LM3S series for Serial to Ethernet devices. We also have developed one utility which shows how many devices are present in the network along with IP address & Mac Address. Now the problem is that Locator utility unable to detect device in same connected network .

We have used "socket API" in software to detect gateway in network .If supposed to use "UDP client API" on same laptop by using Locator utility then gateway device able to detect in same network.

This issue observed on one of laptop only .It is not observed on other Computors.

 

We are unable to find root cause

 

Please do needful.

 

 

  • Hi,
    I'm not very clear with your question. Sorry I need to ask for some clarification.

    1. I suppose the locator utility is run off the PC on the same network with the same subnet mask, correct?
    2. Do you have two different locator utilities with one written using socket API and another written using UDP client API? I'm not clear as to the relationship between the socket API, UDP client API and the locator utility.
    3. When one of the laptops is not able to find the devices on the network, which utility (the socket API locator or the UDP client API locator) is being run?
    4. How many laptops that run the same locator utility are able to find devices on the network?
    5. There is a finder utility that is part of the TivaWare. Can you run this utility on the laptop that does not work? This utility can be found at <TivaWare_Installation>/tools/bin/finder.exe
    6. Can you compare the WireShark captures between the laptop that does not work and the laptop(s) that work?
  • OMG Charles - C'est  très excellente!

    Even w/out (crediting) 'KISS' - your use of such, 'Systematic, Step by Step, Individually Confirming'  (i.e. 'KISS" method) proves certain to yield the Best & Fastest Diagnostic Results - for your poster.

    Perhaps one day - a more enlightened e2e - may (allow) 'KISS' - and its overwhelming advantages - which will SO BENEFIT your client users...

  • Dear Charles, Locator is our customized toll based on Finder utility provided by TI

    Pls find answers

    1. I suppose the locator utility is run off the PC on the same network with the same subnet mask, correct?

    Yes


    2. Do you have two different locator utilities with one written using socket API and another written using UDP client API? I'm not clear as to the relationship between the socket API, UDP client API and the locator utility.

    No. However after problem, we have made utility which tries both way to resolve this issue


    3. When one of the laptops is not able to find the devices on the network, which utility (the socket API locator or the UDP client API locator) is being run?

    Socket based


    4. How many laptops that run the same locator utility are able to find devices on the network?

    We tried many but found problems on two to three Laptops

    5. There is a finder utility that is part of the TivaWare. Can you run this utility on the laptop that does not work? This utility can be found at <TivaWare_Installation>/tools/bin/finder.exe

    Sorry, We had not tried this. I will let you know by next week

    Best Regards

    Harshal L