• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 83 subscribers
  • Views 500 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TMDSPLCKIT-V3: One board/module in kit does is not recognized as PLC device

PaulSchoenke
Genius 3290 points

Hello:

We had purchased the TI PLC kit some time ago for evaluation, but it had been set aside for other project priorities and we’re evaluating the technology again now.  The kit does not seem to be working completely anymore, and I am looking for some support.

The TI kit is P/N TMDSPLCKIT-V3.  One of the modules seems to work okay.  The other gets recognized on USB, drivers get installed, etc. (just like the working one), but when I run the Zero Config app, it does not recognize it as a PLC device.

I have attached a screen capture of the error window that pops up in the case of the bad TI board.

Despite what the message says, the board is connected to COM18 (which is how that board bonded with my PC on the initial plug-in).

Can you help out?  Any feedback or input is welcomed and appreciated!

Thanks again!

Paul

  • 0
    Prodigy 70 points

    Hi Paul,

    If there is no response on the COMM port selected, the Zero Configuration GUI will display a timeout error. To resolve this you can unplug USB cable and plug it again. If the error continues try by changing COMM port selection. Power cycling will also help to get rid of this issue.

    Thanks,

    Shincy

  • 0
    TI__Intellectual 2095 points

    Paul, 

    It may help to download the latest GUI/PLC firmware from www.ti.com/plc. To flash a new firmware on the control card, please refer to user guide in doc directory. To install the new GUI, please first un-install your existing GUI. 

    Thanks. 

    Wonsoo

  • 0 in reply to Wonsoo Kim
    Genius 3290 points

    Hello Wonsoo:

    We've updated the software/firmware, and the problem is unchanged.

    I downloaded the code from the TI site in December, so it is all fairly fresh.  No amount of power-cycling and re-plugging the USB cable changes the behavior.

    The fact that one unit works and one does not makes me believe that I do have a hardware problem.

    Is there anything else we can look at here?

    Thanks again!

    Paul

  • 0 in reply to PaulSchoenke
    Genius 3290 points

    Another update:

    I installed the 6.0.1.0 download, and then plugged in my TI dev kit boxes.  Each was detected on plug-in, drivers were installed automatigally (i.e. I was not asked to direct the driver installer to a directory), and each appeared as a com port as before, one as COM18, the other as COM20.  When I ran the Zero-Config GUI, the same hardware box (COM20) was detected (as it was with the earlier install), while the other (COM18) was not detected (same as with the earlier install).

    What is next?

    thanks again!

    Paul

  • 0 in reply to PaulSchoenke
    TI__Intellectual 2095 points

    Hi Paul, 

    There are two things to check:

    1. The jumper setting on the faulty board (compared to the working one)

    2. Try with SCI-A instead of USB port (SCI-B). To use SCI-A, you will need to have NULL-modem cable (crossed line serial cable). If SCI-A works,  that means that your board has been configured as SCI-A for some reasons. You can change it to SCI-B from the GUI and then you can also use SCI-B.

    Please, let me know if you have any update. 

    Thanks. 

    Wonsoo