💬 Building an Ethernet Gateway
-
@gohan yes I understand perfectly I am a developer and have over 30 years coding experience in about 20 languages. What I find difficult is that there is no detail or documentation on library resource usage so one cannot predetermine the resource requirements when a library or piece of hardware is used. In this great site we have a statement at the top (first sentance) of the Ethernet Gateway page that states "You can build an Ethernet gateway using almost any Arduino model." Well this is not exactly true because if you want to enable some of the library features (ie: signing, and lets face it you should have this enabled if you have any locks or garage doors etc) you will run out of memory in the general models. I am not complaining I just think something so simple should be documented to help other uses look at the right equipment from the outset. In fact all that needs to be written in the first sentence is something as simple as "You can build and Ethernet gateway using almost any Ardunio model however as the Ethernet library uses more resources it would be best to look at a micro controller with greater than 2kb or ram so we recommend a Mega 2560 or similar if you intend to enabled signing or whitelist support."
@itbeyond or if you add external libraries, or if you use debug, or if you change radio, or if, in the future, any of the used libraries increase in size, but not if, in the future, one or more of the included libraries result in smaller flash or ram usage because then it might work. Or if the Arduino IDE changes the compiler flags, thereby affecting the size - either up or down, or if gcc is in a future release changed so code size is affected.
As a programmer, I'm sure you understand that the number of variations increase exponentially, and most of the variables are not under control of the MySensors library.
I agree that a message or table would be nice. I just don't see how it would be feasible to construct and maintain it.
-
@gohan yes I understand perfectly I am a developer and have over 30 years coding experience in about 20 languages. What I find difficult is that there is no detail or documentation on library resource usage so one cannot predetermine the resource requirements when a library or piece of hardware is used. In this great site we have a statement at the top (first sentance) of the Ethernet Gateway page that states "You can build an Ethernet gateway using almost any Arduino model." Well this is not exactly true because if you want to enable some of the library features (ie: signing, and lets face it you should have this enabled if you have any locks or garage doors etc) you will run out of memory in the general models. I am not complaining I just think something so simple should be documented to help other uses look at the right equipment from the outset. In fact all that needs to be written in the first sentence is something as simple as "You can build and Ethernet gateway using almost any Ardunio model however as the Ethernet library uses more resources it would be best to look at a micro controller with greater than 2kb or ram so we recommend a Mega 2560 or similar if you intend to enabled signing or whitelist support."
@itbeyond said in 💬 Building an Ethernet Gateway:
"You can build an Ethernet gateway using almost any Arduino model."
I believe that "almost" is the right word, since in fact the basic Ethernet gateway can run on many devices but as the requirements increase you need to step up the HW, I don't see it as a big problem: just as you need more IO pins then a standard UNO you go to a Mega2560.
-
I give up - at least if someone is thinking of building this gateway and wanting to use security they can hopefully read this thread before they start and will look at a higher level controller before they purchase the hardware. I am only trying to help others with what to me is still a simple and easy fix alas I must have upset the apple cart.
There is no big problem at all, just that it is really simple to know right now, with technology available today, if you need an Ethernet gateway and signing then use a Mega 2560 or better for the Ethernet Gateway controller to ensure you have the ram. @mfalkvidd - You state variations increase exponentially and most not under library control however using the MySensors Library and building the hardware shown and documented on this page using the sketch provided (completely under control of MySensors) you will need a Mega 2560 or better if you intend to enable signing (also under control of the Library). Do not get me wrong I really love the whole MySensors thing and have over 30 devices up and running and have enjoyed the whole learning thing however simple requirements (IMHO) like this should be detailed.
Hopefully this post will help the next person, it certainly would have help me and I am sure I am not the only one.
-
I give up - at least if someone is thinking of building this gateway and wanting to use security they can hopefully read this thread before they start and will look at a higher level controller before they purchase the hardware. I am only trying to help others with what to me is still a simple and easy fix alas I must have upset the apple cart.
There is no big problem at all, just that it is really simple to know right now, with technology available today, if you need an Ethernet gateway and signing then use a Mega 2560 or better for the Ethernet Gateway controller to ensure you have the ram. @mfalkvidd - You state variations increase exponentially and most not under library control however using the MySensors Library and building the hardware shown and documented on this page using the sketch provided (completely under control of MySensors) you will need a Mega 2560 or better if you intend to enable signing (also under control of the Library). Do not get me wrong I really love the whole MySensors thing and have over 30 devices up and running and have enjoyed the whole learning thing however simple requirements (IMHO) like this should be detailed.
Hopefully this post will help the next person, it certainly would have help me and I am sure I am not the only one.
@itbeyond signing is a completely optional feature of the library. One part of a great many optional features. It is a delicate tradeoff of providing detailed instruction and keeping documentation at a level where users actually care about reading it.
-
Hallo,
I`m running this ethernet-gateway with w5100 shield on uno.
In the log of iobroker I always see this message again and again:
mysensors.0 2018-01-26 11:10:58.942 error Error for "192.168.178.133": Error: read ECONNRESET
mysensors.0 2018-01-26 11:10:55.105 info Received INTERNAL message: I_GATEWAY_READY: Gateway startup complete.
mysensors.0 2018-01-26 11:10:55.103 warn ID not found. Inclusion mode OFF: {"id":"0","childId":"255","type":"presentation","ack":false,"payload":"2.1.1","subType":"S_ARDUINO_RELAY"}
mysensors.0 2018-01-26 11:10:55.094 info Connected 192.168.178.133:49153
mysensors.0 2018-01-26 11:10:54.897 error Error for "192.168.178.133": Error: read ECONNRESET
I cannot find a solution in the forum of iobroker and also nothing about it in this forum.
By the way: In the list of objects in iobroker there is always a child id 255 without any state or value.
Is it an issue ?
Perhaps of iobroker?
Any solution? -
Here the log from debug:
0;255;3;0;9;MCO:BGN:INIT GW,CP=RNNGA--,VER=2.1.1
0;255;3;0;9;TSM:INIT
0;255;3;0;9;TSF:WUR:MS=0
0;255;3;0;9;TSM:INIT:TSP OK
0;255;3;0;9;TSM:INIT:GW MODE
0;255;3;0;9;TSM:READY:ID=0,PAR=0,DIS=0
0;255;3;0;9;MCO:REG:NOT NEEDED
IP: 192.168.178.133
0;255;3;0;9;Eth: connect
0;255;3;0;9;MCO:BGN:STP
Can`t find any error.
From here only reading nodes. -
Hello, all. Nuuubeee here, though been doing MUCH reading/studying. I had previously (before stumbling upon this site) decided to go with MRF69HWs. I see that the code can be un-commented for this radio, but having difficulty with pinouts and mismatching pin anmes: the RFMs (appear) to have no corresponding pins to the NRFs CE and CSN pins. The MRF uses NSS and D100 pins, not labeled as such on the NRF. Same use with different labels? I've poked around looking for hints and tips about wiring the MRFs to work with the W5100, though so far, haven't found what (I think ) I need.
Thanx!
-
Hello, all. Nuuubeee here, though been doing MUCH reading/studying. I had previously (before stumbling upon this site) decided to go with MRF69HWs. I see that the code can be un-commented for this radio, but having difficulty with pinouts and mismatching pin anmes: the RFMs (appear) to have no corresponding pins to the NRFs CE and CSN pins. The MRF uses NSS and D100 pins, not labeled as such on the NRF. Same use with different labels? I've poked around looking for hints and tips about wiring the MRFs to work with the W5100, though so far, haven't found what (I think ) I need.
Thanx!
-
Have seen and studied that, though at the top of this page it mentions some necessary changes for use with the W5100:
"The W5100 ethernet module has problems sharing SPI with radio. To solve this, we put the radio on a couple of other pins and use so called soft-spi. That's why you have to wire the radio a little differently here than on the usual sensors. "
I assume that for this reason the link you replied with would not work. Some times I get into trouble assuming things; if those connections work for the gateway, I guess I'm good to go (and just didn't realize it).
Thanx -
I did look a little closer to the page you referenced and noticed your pin "color coding" was identical between the two radios, even though those two pin names were different. Would it be safe to interpolate those same "color codes" between the radio and the Arduino (using Pro Mini) even though the pin names are different?
-
I did look a little closer to the page you referenced and noticed your pin "color coding" was identical between the two radios, even though those two pin names were different. Would it be safe to interpolate those same "color codes" between the radio and the Arduino (using Pro Mini) even though the pin names are different?
Thanks for clarifying @flyyboyy
The following are used for SPI:
NSS (also called SÌ…SÌ…, SSEL, CS, CÌ…SÌ…, CE, nSS, /SS, SS# according to wikipedia)
SCK
MOSI
MISOand yes, I think they use the same colors on the nrf and rfm instructions. But I am not sure about CE vs CSN on the nrf24.
I have updated the table for w5100 to include the NSS naming.
-
I created a case for this gateway.
https://www.thingiverse.com/thing:2923130 -
OK, who's up for a WHOLE LOTTA handholding? Dang, guess I'm getting denser the older I get.
Is this page the place to solicit help, or should I start a new topic in the forum? I searched there for answers to my yet-unstated questions but found nothing. Guess I am the only one that doesn't get it. . .
TIA for any takersflyy
-
By the way, the questions at this point relate directly to the Ethernet Gateway -- that's why I was asking if this page was the proper place to ask
@flyyboyy here or in a new thread doesn't matter that much - as long as you don't post the same thing in multiple places.
https://forum.mysensors.org/category/5/troubleshooting is a good category for troubleshooting
The post at the top of that page lists the most common problems, how to troubleshoot them, and what information is usually required to help so you can get help as quick as possible.
