EmbeddedRelated.com
Forums
Memfault Beyond the Launch

LED TCP/IP OFF

Started by "S S...@gmail.com [rabbit-semi]" October 27, 2016
Dear All,

I'm use RCM3700 dan DC9.62. I'm ping system and replay, result
pd_havelink() = 1. If connector tcp/ip pull out, result = 0.
I have digital input and use opto for isolation. Digital input connect
to contact of contactor. If contactor on and off repeated, led tcp/ip
off and ping RTO.
In monitor pd_havelink(), result = 1. If connector tcp/ip pull out,
result still = 1.
Can anyone help me to solved my problem ?
Thanks.
Stev.

Posted by: S Sutikno



Stev,

I'm sorry, but I'm not sure I understand what's happening.

It sounds like changes to an optically-isolated input are somehow crashing the Ethernet connection on your RCM3700. Is that correct?

Does the problem happen even if you aren't reading the input? I ask in order to isolate a software cause of the problem -- that a change in the input triggers different code in your program.

You would probably need to share the portion of your schematic related to that input connection.

In your program, if you use pd_powerdown() and pd_powerup(), does the Ethernet interface start working again?

-Tom
On Oct 26, 2016, at 9:04 PM, S Sutikno s...@gmail.com [rabbit-semi] wrote:

> I'm use RCM3700 dan DC9.62. I'm ping system and replay, result
> pd_havelink() = 1. If connector tcp/ip pull out, result = 0.
> I have digital input and use opto for isolation. Digital input connect
> to contact of contactor. If contactor on and off repeated, led tcp/ip
> off and ping RTO.
> In monitor pd_havelink(), result = 1. If connector tcp/ip pull out,
> result still = 1.
> Can anyone help me to solved my problem ?
> Thanks.
> Stev.

Memfault Beyond the Launch