• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 79 subscribers
  • Views 845 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.

MSP430 eZ430-RF2500-SEH the end device can not connected to the access point

Denis Petrov
Prodigy 40 points
Other Parts Discussed in Thread: SIMPLICITI

Hello. I work with MSP430 eZ430-RF2500-SEH. I downloaded the code on the access point and on end device. Thereafter, the end device is not connected to an access point. On the access point is flashing green LED on the end device  both LEDs flash simultaneously. The program eZ430-RF2500 SEH sensor monitor shows that the bubble is not flashing, and nothing is displayed. How can I fix it?

  • 0
    TI__Guru**** 218467 points

    Denis,

    Have you closely followed all directions as prescribed by section 4 of the eZ430-RF2500-SEH Solar Energy Harvesting Development Tool User's Guide?

    Perhaps it would also be helpful to reference the FAQ page in Appendix 1, with careful attention to removing J8 and keeping the solar cell under a bright light prior to attempting to join the network.

    Regards,

    Ryan

  • 0 in reply to Ryan Brown1
    Prodigy 40 points

    Yes, I'm doing what says in this document . The final product is connected to an access point. Оnly in version eZ430-RF2500-SEH Sensor Monitor 2.5 bubble flashes, but the final product does not appear. I tried in version eZ430-RF2500-SEH Sensor Monitor 2.5 1.0.6. Here all works. I understand that this example for the old version.

  • 0 in reply to Denis Petrov
    TI__Guru**** 218467 points
    So with regards to the SimpliciTI Compliant Protocol Stack, you've found that version 1.0.6 correctly runs the eZ430-RF2500-SEH Sensor Monitor 2.5 demo whereas the current version (1.1.1) does not? If so I will file a bug report with our software team to have the issue investigated.

    Regards,
    Ryan

**Attention** This is a public forum