Javascript Disabled Detected

You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

The Netduino forums have been replaced by new forums at community.wildernesslabs.co. This site has been preserved for archival purposes only and the ability to make new accounts or posts has been turned off.

Behavior is different when network cabe is in

Started by JKamil, Aug 03 2011 09:12 AM

Please log in to reply

5 replies to this topic

#1 JKamil

New Member

Members
3 posts

Posted 03 August 2011 - 09:12 AM

Hi, I wrote some netduino plus "driver" for ultrasonic rangefinder. It is rather simple, it uses interruptions, from the 0->1 timestamp to the 1->0 timestamp. It works only when network cable is not plugged in. When the cable is in, the output is allmost allways wrong - it tells that there is something in 150 cm ( instead of 400 cm which is mesure when cable is not plugged in ). Are there some changes in timings/ frequency / latency when the cable is in? Is there some kind of workaronds, as I bought the plus version so I could send measured data over LAN...

Back to top

#2 Stefan W.

Advanced Member

Members
153 posts

Posted 03 August 2011 - 11:40 AM

Hi,

I wrote some netduino plus "driver" for ultrasonic rangefinder. It is rather simple, it uses interruptions, from the 0->1 timestamp to the 1->0 timestamp. It works only when network cable is not plugged in. When the cable is in, the output is allmost allways wrong - it tells that there is something in 150 cm ( instead of 400 cm which is mesure when cable is not plugged in ).

Are there some changes in timings/ frequency / latency when the cable is in?

Is there some kind of workaronds, as I bought the plus version so I could send measured data over LAN...

I recall a post in this forum that the analog inputs behave oddly when the network cable is plugged in ... do you have the input on an analog input port of the netduino plus?

Cheers,
Stefan

I believe that no discovery of fact, however trivial, can be wholly useless to the race, and that no trumpeting of falsehood, however virtuous in intent, can be anything but vicious.
-- H.L. Mencken, "What I Believe"

Back to top

#3 JKamil

New Member

Members
3 posts

Posted 03 August 2011 - 01:06 PM

I recall a post in this forum that the analog inputs behave oddly when the network cable is plugged in ... do you have the input on an analog input port of the netduino plus?

Cheers,
Stefan

No, all four rangefinders are connected to the D0 - D7 ports... So maybe "Interrupts on digital inputs behave oddly when network cable plugged in"

Back to top

#4 Valkyrie-MT

Advanced Member

Members
315 posts

LocationIndiana, USA

Posted 03 August 2011 - 02:43 PM

No, all four rangefinders are connected to the D0 - D7 ports... So maybe "Interrupts on digital inputs behave oddly when network cable plugged in"

What firmware version are you using? If it's an older version, you might have the problem mentioned here.

If that is the problem, the workaround is to avoid using the D2 input. Or just upgrade the firmware.

-Valkyrie-MT

Back to top

#5 Valkyrie-MT

Advanced Member

Members
315 posts

LocationIndiana, USA

Posted 03 August 2011 - 02:44 PM

Duplicate post.

Back to top

#6 JKamil

New Member

Members
3 posts

Posted 03 August 2011 - 03:11 PM

What firmware version are you using? If it's an older version, you might have the problem mentioned
If that is the problem, the workaround is to avoid using the D2 input. Or just upgrade the firmware.

-Valkyrie-MT

Ive tried it in the default 4. something firmware, and later in 4.2. Still the same.