Most recent activity
-
-
Ok, i had not much time for a extensive test. I just set up all pins and connection from the scratch and retry the main features again.
(same network / router configuration like before)
- DHCP still fail
- eth.setIP({ "ip": "192.168.1.2", ... }) works after 2-3 function calls (very strange)
- first eth.getIP() call returns very strange ip settings (e.g. { "ip": "3.192.168.1", ... })
- ping from my Mac Book to the espruino works
- http server 'hello work' doesn't
- http request to my Mac Book apache doesn't work
The result was the same like my first documentation. At the moment, I don't know what I'm doing wrong. After my holidays i give that another with new network and router configuration. Additionally a friend of mine will take a look at my configuration.
I'll keep you up to date
@user47955: which revision do you have?
- DHCP still fail
-
I'm suspicious of above result. In static IP mode, its IP address should be read correctly, but you couldn't do that.
I hope we're not talking past each other. DHCP connection doesn't work. A static ip definition with
eth.setIP({....});
works well. I can ping to the defined ip address. But the server application doesn't work. No response after running a page request or setup a simple http server.Well, i give this issue another try this weekend, but I guess I can not handle an oscilloscope :-) Nevertheless, I try my best to find a way for debugging.
-
-
I've just fired off an e-mail to WIZnet and we'll see if they can think of anything.
@Gordon: do you have an update or feedback from wiznet?
-
-
Here a little example. I clean and reduce a little bit the code. Some var definitions are not needed.
/* Copyright (c) 2014 ToDo */ /* Quick description ToDO */ var C = { ADDRESS : 0x48 // description }; /** * Description */ function TMP102(_i2c) { this.i2c = _i2c; } /** * Description */ TMP102.prototype.getTemperature = function() { var d = this.i2c.readFrom(C.ADDRESS, 2); return (((d[0] << 8) | d[1]) >> 4)*0.0625; }; /** * export */ exports.connect = function (_i2c) { return new TMP102(_i2c); };
-
-
I don't know if this is a big issue for other people, but for me it's a part of user experience. On most project pages you can find in the header of the page the current version or a little eyecatcher. From this view, i guess it would be an improvment, to present the release much more prominent.
And please, this issue has a low priority! Other things are much more important...
So, sorry for the late answer.
I tested some issues.
I check the RDY pin, but after the value was '1', nothing changed. DHCP is still not working. At the moment, i'm not able to set a static ip address at this place (university network), but i will test it at home again.
I test the B2 pin with a LED and it works well. So the connection is definitively ok.
Well, i don't know how i get this module to getting work.
Any other suggestions? Test issues?