Net_Ethernet_Intern_doDHCPLeaseTime() problem

[phil31]

Hi

just 10 days more and no reply ..
this thread is just open since 2 months ..
this problem is just open by several users since several YEARS ..
and never any real reply or solution .. "we tested, it's work" ...

great .. perfect support and help ...
if you have a problem to blink a LED, yes ask for support .. but for real problem ... light a candle !

the Ethernet library is used by several thousand users and you never really fixed it or update it with real improvement !
while Microchip is regularly update its library.. (i'm convince the ME one is a port of Microchip)

we really don't care about customers here .. amazing ..

[petar.suknjaja]

Hi,
Testing the code I have found out that there is a problem with DHCPLeaseTime().
I've tried to troubleshoot it but I haven't made any progress finding the source of the problem.
Due to its complex nature,this issue has been forwarded to team who developed this library.
Kind regards,
Petar

[phil31]

"lol"....

this code is your official sample ..
then what did you test when you affirm long time ago that there is no problem ??

then now, the official development team "take it in account" .. T0 start to provide a solution ...

tired to fight with ME teams !
don't need help to design my products, i need help to solve your faulty products !

same for a bug OPENED AND CONFIRMED since several years with the mikroprog device ! ..
several YEARS and never corrected !!!

regards

[petar.suknjaja]

Hi,

I'm not confirming the bug, I'm just confirming the fact that I couldn't get the lease time same as you.
Maybe it's something trivial, maybe bug, or something with network configuration, we will see.

I've forwarded this issue to the team who wrote the library.
As soon as I get some information, I will post it here.

Also, thank you phil31 for your suggestions and critiques, we will learn from it and continue growing in the future.

If anyone else also has the problem with lease time with Network Ethernet Internal library, I encourage you to post it here.

Kind regards,
Petar

[phil31]

So Team ..

just 9 weeks after my question, no real news or progress ?
as you know, you tested your official example ! which one you say since several years that there is no problem !.?
as you know, this problem is open since several YEARS by other users .. just check the forum !
in fact that is all the library which have problems, but you refuse to accept it and to update it.
as you continue to close these library codes (which are certainly , coming from Microchip libs ... they are free open .. ), we are totally blocked !

i'm tired to continue to write such message, but without do that, i'm convince that you will never do anything and wait that this thread go to 2de or 3th page of the forum !

regards

[petar.suknjaja]

Hi,

As I said in previous post, I've forwarded this issue to be reviewed by the team who wrote the library.
And when I get some information, I'll share it with you.


Kind regards,
Petar

[phil31]

Petar

the problem now is "when i get" ...
i know too much how this is going .. if no one up the thread, it goes to the trap

"when I get some information" ==> that mean, if no reply from your dev team, then the thread is dead and we (users) will never receive any real answer, as even ...

we can fin a lot of example in your forum where this end like this ..

[petar.suknjaja]

Hi phil31,

I totally understand you, and in a way I understand how you feel.
The team that worked on this library will review this issue and let us know if it's bug, or maybe there are some prerequisites needed to be met before the routine could renew IP.
I agree with you that this took some time, but this is on their queue list and it won't take much time until we get response from them.

Kind regards,
Petar

[phil31]

near 3 months later, even no answer !!
that is really a shame, a poor consideration about your customers

" it won't take much time until we get response from them"
let me laugh ! i'm pretty sure that next month, no more answer !
as this bug, or problem as you call it, is open since several years !

what did i say to my customers ?
that i'm using a compiler that is a toy and not a professional tool ?
yes surely, that is simply the true

[phil31]

Hello,

well only 2 months after submit the problem to the team ..
and more than 4 months after open this thread
and more than YEARS from the original thread open
(viewtopic.php?f=176&t=39083&p=277858&hi ... ew#p277792)

even no answer ! ...

[phil31]

Hello

5 months now after open the problem, even no real answer from the team ..

how can we name this kind of "support" ?

[phil31]

Well users of libstock ETH library ..
after a lot of waste time and complain, i just receive a fix for this issue !

contact Filip if you need it

regards

[phil31]

Hi all..

just 1 more year !! and the official library is not update ..
if you use this lib from libstock ... your DHCP release will not work !

[markkoh]

I encounter the same DHCP issue when working with ENC28J60 chip.

After reading all your comments and post... I realize I did not enable my global interrupt bit, therefore my SPI_Ethernet_UserTimerSec reg counter isn't inc every seconds... and since SPI_Ethernet_initDCHP depends on SPI_Ethernet_UserTimerSec value to timeout, thus my routine hang while trying to perform a DHCP init!

I hope this finding can resolve your frustration with DHCP init.