Re: R6k and Ethernet current

"seecwriter" <seecwriter-/[email protected]>
Newsgroups gmane.comp.hardware.rabbit-semiconductor
Message-ID <[email protected]>
Paul,

Thank you for that information. 

I contacted Digi tech support and told them the problem. They replied,
"I checked with engineering and was told this is normal operation for
rabbit 6000 products."

I then told them that a former Rabbit employee said it was a known 
bug and was supposed to be fixed with the release of the RCM6600W.
They replied with, "I checked with software and they don't know of a
library that fixes this issue. They did suggest that the re-spin of
the 6000 chip addresses this issue."

I then asked they thought the re-spin would take place. I'm waiting
for an answer.

Hopefully the battery-killer clock on the R6k will be fixed with the
re-spin too.


Steve

--- In [email protected], "Paul " <lackofbrilliance@...> wrote:
>
> Hi Steve,
> 
> I was a long time Z-World/Rabbit software engineer and the engineering manager responsible for Rabbit development for the last three years prior to Digi's last round of layoffs.  This is a known problem that, if memory serves, was scheduled to be fixed with the Dynamic C release to support the RCM6600W.  You should contact Digi technical support to see if you can get a copy of the library that fixes this problem.  
> 
> - Paul
> 
> 
> --- In [email protected], "seecwriter" <seecwriter@> wrote:
> >
> > For the RCM67XX module, we've noticed an anomaly with current draw
> > when using Ethernet.
> > 
> > When the Ethernet port is connected to a LAN, the total current draw
> > for the computer section (motherboard + RCM67XX) is a steady 350ma.
> > However, if the Ethernet port is not connected, the current fluctuates
> > between 350ma and 500ma. We've traced the increase in current to the
> > call of pd_havelink() that occurs at about a 500ms rate. That 150ma of 
> > extra current seems like a huge increase just to check for a LAN 
> > connection. This pulsing current is affecting our ADC and DAC readings 
> > and settings.
> > 
> > This occurs on all of our modules. Anyone else notice this and/or have
> > any ideas on what to do about it? Adding extra bypass caps hasn't 
> > helped. 
> > 
> > Steve
> >
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.