Arduino Easy 2560

[LisaM]

can you upload it here so that we can test it? i want to use this to control my heating system seperate in every room

Link to sources and to image are in this topic....

[frank]

can you upload it here so that we can test it? i want to use this to control my heating system seperate in every room

Link to sources and to image are in this topic....

i found the new version (i was looking and reading with my eyes shut ) and i will test it.

The dht plug in gives errors when i put it in.

Arduino: 1.6.12 (Windows 10), Board:"Arduino/Genuino Mega or Mega 2560, ATmega2560 (Mega 2560)"

xxxxxxxx \ArduinoEasy-master (2)\ArduinoEasy-master\ArduinoEasy\_P005_DHT.ino: In function 'boolean Plugin_005(byte, EventStruct*, String&)':

_P005_DHT:79: error: 'class EthernetServer' has no member named 'arg'

String plugin1 = WebServer.arg(F("plugin_005_dhttype"));

^

exit status 1
'class EthernetServer' has no member named 'arg'

This report would have more information with
"Show verbose output during compilation"
option enabled in File -> Preferences.


so if you can help me with this i will be a step ferther

[LisaM]

i found the new version (i was looking and reading with my eyes shut ) and i will test it.

The dht plug in gives errors when i put it in.

Arduino: 1.6.12 (Windows 10), Board:"Arduino/Genuino Mega or Mega 2560, ATmega2560 (Mega 2560)"

xxxxxxxx \ArduinoEasy-master (2)\ArduinoEasy-master\ArduinoEasy\_P005_DHT.ino: In function 'boolean Plugin_005(byte, EventStruct*, String&)':

_P005_DHT:79: error: 'class EthernetServer' has no member named 'arg'

String plugin1 = WebServer.arg(F("plugin_005_dhttype"));

^

exit status 1
'class EthernetServer' has no member named 'arg'

This report would have more information with
"Show verbose output during compilation"
option enabled in File -> Preferences.


so if you can help me with this i will be a step ferther

You cannot simply copy a ESP8266 plugin to an Arduino plugin, they are fundamentally different! The ESP8266 uses the WifiServer class, while ArduinoEasy is using the EthernetServer class...

For example: The ESP is using the

Code: Select all

WebServer.arg("plugin_001_type")

call, while the Arduino is using the

Code: Select all

WebServerarg(F("plugin_001_type"))

call. You might change the DHT code using this example to see if it works, but no guarantee...

Martinus has shrunk and altered the code a LOT, to make it fit in 256KB. That means that a lot of code has been removed to make it fit in this small thingy called Arduino...

[Martinus]

I've added the DHT plugin on github that compiles without error but can't verify that it actually works...

[frank]

I've added the DHT plugin on github that compiles without error but can't verify that it actually works...

you are the best i will test it

[Martinus]

You cannot simply copy a ESP8266 plugin to an Arduino plugin, they are fundamentally different! The ESP8266 uses the WifiServer class, while ArduinoEasy is using the EthernetServer class...

Funny thing is that the plugin mechanism and many early plugins were initially ported from Arduino AVR to ESP8266. So now we are sort of porting them back...

Martinus has shrunk and altered the code a LOT, to make it fit in 256KB. That means that a lot of code has been removed to make it fit in this small thingy called Arduino...

Well most of the challenge was (and will be) to keep RAM usage within 8k... (where ESP8266 has 80k...)

[LisaM]

You cannot simply copy a ESP8266 plugin to an Arduino plugin, they are fundamentally different! The ESP8266 uses the WifiServer class, while ArduinoEasy is using the EthernetServer class...

Funny thing is that the plugin mechanism and many early plugins were initially ported from Arduino AVR to ESP8266. So now we are sort of porting them back...

Martinus has shrunk and altered the code a LOT, to make it fit in 256KB. That means that a lot of code has been removed to make it fit in this small thingy called Arduino...

Well most of the challenge was (and will be) to keep RAM usage within 8k... (where ESP8266 has 80k...)

You have been busy on the arduino/webserver classes, i'll reload and look on the serial port what exactly is happening when rebooting regarding the config files. Would be nice if i can reboot without crashing the config files.

[frank]

i have tested the dht plug in. The 12c scan does see the dht 12. but in the devices tab there is no reading. The log says dht no reading.

[Martinus]

This P005 plugin is build for DHT one-wire sensors only (DHT11/DHT22).
Maybe P034 will do the job, this one seems to compile without modifications (taken from the R147 ESP Easy source)

[Martinus]

I'm actually on holiday right now and while my wife is reading a book, i'm browsing the ESP forum...
Using a netbook now to remotely control my Windows 10 (XBMC-Kodi) PC stick that's still powered on at home.

Arduino compiles a bit slow there (Atom Z3735 cpu), but still fun to be able to use the Home Cinema TV Stick as a remote emergency development platform...
I could finish some loose ends on ESP Mega development as well.

But no Arduino Mega is active on the Home network right now and even if it was, they have no OTA capability...

[frank]

i am on a holliday also. And running like crazy to test the setup
The p034 did the trick i don´t get it in my domoticz but that is settings i think

[frank]

is it possible that communication with domoticz doesn't work ?

this is wat the log tels me

Welcome to Arduino Easy: Mer Ruimte

0:00:00 : HTTP : connecting to 192.168.1.167 using port 8090
0:00:00 : /json.htm?type=command¶m=udevice&idx=249&svalue=22.50;41.70;0
0:00:00 : HTTP/1.1 401 Unauthorized
0:00:00 : Content-Length: 91
0:00:00 : Content-Type: text/html
0:00:00 : Set-Cookie: SID=none; HttpOnly; path=/; Expires=Thu, 01 Jan 1970 00:00:00 GMT
0:00:00 :
0:00:00 :
401 Unauthorized

0:00:00 : HTTP : closing connection
Log
Powered by www.letscontrolit.com

[Shardan]

Maybe wrong access credentials?
HTTP401 says username and/or password is wrong.

[frank]

i am using the same login and password as my other esp units

[Martinus]

Just checked the source, authentication is not implemented yet...

[frank]

Just checked the source, authentication is not implemented yet...

that explains a lot

[frank]

Just checked the source, authentication is not implemented yet...

if possible could you look at that?

an otherthing is that i have tried 2 dht 12 on the unit and than it doesn't work any more
no readings then

[LisaM]

It crashes after a reboot because it hangs at the portUDP.endpacket call in the syslog function...
Disabling the endpacket (and other portudp calls) means it runs again after a reboot!
Another call at sendSysInfoUDP is also causing problem, at endpacket, disabling it.

*Happy Girl*

[frank]

It crashes after a reboot because it hangs at the portUDP.endpacket call in the syslog function...
Disabling the endpacket (and other portudp calls) means it runs again after a reboot!

*Happy Girl*

great is that a software fix or settings?

[LisaM]

It crashes after a reboot because it hangs at the portUDP.endpacket call in the syslog function...
Disabling the endpacket (and other portudp calls) means it runs again after a reboot!

*Happy Girl*

great is that a software fix or settings?

Software Fix...
Setting: Don't use syslog logging, ntp or SendUDP cmd! It will kill espeasy after reboot...

[frank]

okay
there is a lot to fix in this one. But that is to be expected with a test version

[LisaM]

So, don't use:
- Syslog
- NTP
- SendUDP message

Not until i've figured out why endpacket is crashing...

[Martinus]

Authentication is now added in github, although not tested in any way. It compiles...
Don't forget to add the base64 library to arduino libraries folder

[Martinus]

So, don't use:
- Syslog
- NTP
- SendUDP message

Not until i've figured out why endpacket is crashing...

I remember to have a unit joining the ESP node list using the UDP system messaging so at a certain point during development UDP should have worked.
But i can't remember if NTP or syslog was tested.

The W5100 only has 4 networksockets so it could be challenging to run multiple protocols. We could end in some concurrency issues that we did not encounter on the ESP that has a lot more resources. The W5100 can also be a bit picky when sockets have to change from TCP <-> UDP.

[LisaM]

I remember to have a unit joining the ESP node list using the UDP system messaging so at a certain point during development UDP should have worked.
But i can't remember if NTP or syslog was tested.

The W5100 only has 4 networksockets so it could be challenging to run multiple protocols. We could end in some concurrency issues that we did not encounter on the ESP that has a lot more resources. The W5100 can also be a bit picky when sockets have to change from TCP <-> UDP.

I've figured out why it still wasn't working, while serial monitor showed clear signs of life. It turns out that AFTER a reboot the DNS name is changed to

Code: Select all

WIZnetEFFE08

AND that the mac address changed from

Code: Select all

DE:AD:BE:EF:FE:00

to

Code: Select all

DE:AD:BE:EF:FE:08

causing my DHCP server to handout a NEW ip address so the old one didn't work anymore despite static dhcp ip address settings.
On the new address the ArduinoEasy is working just fine...

I can set NTP to on AND reboot without any problems, so only the syslog is causing problems. I'm using the Synology Syslog, maybe that might be the problem also.

[frank]

it works like a charm now great

[frank]

after a few minutes the 2560 stops working so it is not verry stable

[LisaM]

after a few minutes the 2560 stops working so it is not verry stable

Serial log?

[frank]

i wil test ferther today to see where it stops. First thing i saw was that the sd card was not clean so i formated it and did a clean install. know waiting what happens

[frank]

this are the last entry in the log before crash

0:00:00 : HTTP : closing connection
0:00:00 : DHT12: Temperature: 21.50
0:00:00 : DHT12: Humidity: 61.10
0:00:00 : HTTP : connecting to 192.168.1.167 using port 8090
0:00:00 : /json.htm?type=command&param=udevice&idx=249&svalue=21.50;61.10;0

[frank]

i think it is a wiring problem
The unit is stable now i took the relay board of

[LisaM]

i think it is a wiring problem
The unit is stable now i took the relay board of

Maybe your power supply is not stable enough to feed both arduino/ethernet shield+relay board?

[frank]

i think it is a wiring problem
The unit is stable now i took the relay board of

Maybe your power supply is not stable enough to feed both arduino/ethernet shield+relay board?

the power supply is stable it looks like 1 input on the 8 relay board is faulty i took it of and it looks stable even with 6 relays on

[frank]

it is stable for over een hour now

[LisaM]

Mine has be running non-stop for over a day now, with 3 devices created (and working) and a dual-relay attached (with leds attached to prove functioning). Even multiple reboots didn't create a problem, as long as you don't use syslog it's working just fine. After the first reboot, it get's a different mac-address and therefor a different ip-address, but if you're aware of it then it is not a problem.
I find it very usable for fixed ethernet connections and gearing up for deployment in my gate motor control which has an ethernet line but no wifi, for Wifi i prefer the ESP8266.

[frank]

mutipel dht 12 messes the system up. Is there a solution for that?
I hope that i am not asking for to much

[LisaM]

mutipel dht 12 messes the system up. Is there a solution for that?
I hope that i am not asking for to much

8-relay board, multiple dht-12's, you're asking a lot from an experiment...
I suspect that you're using it because the 2560 has so many gpio's. But the 2560 is SEVERLY limited in both flash as ram memory and not really suitable for complex setup's using ESPEasy. If you have Wifi, i would consider using NodeMCU with BME280's (using I2C) and a IO extension board for the 8-relay...

[frank]

mutipel dht 12 messes the system up. Is there a solution for that?
I hope that i am not asking for to much

8-relay board, multiple dht-12's, you're asking a lot from an experiment...
I suspect that you're using it because the 2560 has so many gpio's. But the 2560 is SEVERLY limited in both flash as ram memory and not really suitable for complex setup's using ESPEasy. If you have Wifi, i would consider using NodeMCU with BME280's (using I2C) and a IO extension board for the 8-relay...

i want to use it to control the Radiators in my home and measure the tempertures in the rooms. I use several esp 8266 e12 dev kits for several things. The number of outputs and the wired connection is what interested me in this project this in combination with the easy software. The other option is an separet esp for the DHT12 and the 2560 for the outputs

[Martinus]

mutipel dht 12 messes the system up. Is there a solution for that?
I hope that i am not asking for to much

DHT12 uses the I2C bus and has only one fixed I2C address. Therefore it is limited to one by design.
A DHT11 or DHT22 should work with more than one device

[frank]

mutipel dht 12 messes the system up. Is there a solution for that?
I hope that i am not asking for to much

DHT12 uses the I2C bus and has only one fixed I2C address. Therefore it is limited to one by design.
A DHT11 or DHT22 should work with more than one device

thx martius. Ik zal wat andere opnemers moeten regelen.

[LisaM]

mutipel dht 12 messes the system up. Is there a solution for that?
I hope that i am not asking for to much

DHT12 uses the I2C bus and has only one fixed I2C address. Therefore it is limited to one by design.
A DHT11 or DHT22 should work with more than one device

thx martius. Ik zal wat andere opnemers moeten regelen.

https://nl.aliexpress.com/item/1PCS-GY- ... 0.0.haYjri

[Shardan]

mutipel dht 12 messes the system up. Is there a solution for that?
I hope that i am not asking for to much

DHT12 uses the I2C bus and has only one fixed I2C address. Therefore it is limited to one by design.
A DHT11 or DHT22 should work with more than one device

The DHT11/22 are no 1wire devices. They call their protocoll 1wire too but it is not the 1wire as dallas et al defined it.
I doubt if it is possible to chain them. The datasheet does not mention anything about it.


Sadly the usual i²c based temp/humidity sensors (SI7012, BME280, DHT12) do not have an address pin to change the
i²c address. The other sensors (DHT11/22, SHT1X) don't have any addressing possibility.
The only way out for multi-Sensor at this time might be to use DHT11/22 on different GPIO's.

Regards
Shardan

[Shardan]

oops - double post, sorry

[LisaM]

Sadly the usual i²c based temp/humidity sensors (SI7012, BME280, DHT12) do not have an address pin to change the
i²c address. The other sensors (DHT11/22, SHT1X) don't have any addressing possibility.

BMP/E280 do have I2C address jumper!: https://forum.arduino.cc/index.php?topic=404946.0

[Shardan]

You're right.
Two sensors are possibe on 0x76 and 0x77.
I'd prefer to get a bigger breakout then with a SDO pin availlable.
Cutting the tiny PCB and soldering can be a mess.

Anyways, more then two adresses is not possible.
The bigger problem will be the I²C bus. Without some additional electronics
it might run into problems if cabling is extended to long lines.
I²C was designed as a "inside one box" bus for TV sets, DVD players and such.
(Inter-integrated Circuit). So it is not designed for long cablings. Usually it can be extended to 0,5 or 1 m,
sometimes a bit more. If longer cabling is needed you need bus extender chips. HDMI cables do this.

So i wonder what sense make two humidity sensors with 1m distance?
Maybe on the two sides of a wall if drilling the cable directly through the wall?
A DHT22 is reported to work nicely with a 15m Cat5 cable.

[LisaM]

So i wonder what sense make two humidity sensors with 1m distance?

It doesn't make sense at all. It makes sense to attach a humidity sensor, a lumi sensor and other types of i2c sensors to the same two wires to use only 2 gpio's for a lot of different sensors. That saves gpio's so you attach stuff like the mh-z19 co2 sensor and a pir to it to make a densely packed sensor array...

[Martinus]

The only way out for multi-Sensor at this time might be to use DHT11/22 on different GPIO's.

And that's exactly what i meant while mentioning these types. It should work as long as each sensor has it's own gpio.

[frank]

i am verry happy with the progres of the last few days. Lisa and Martinus thx verry much for your help. I hope that the mega 2560 branch will ferther develop

[LisaM]

I hope that the mega 2560 branch will ferther develop

Don't get your hopes up, there is very little reason to spent a lot of time on this branch. The Arduino platform is outdated, even the DUE has only 512KB of flash memory and it's CPU still slow. The Arduino platform is growing WAY to slow...

It makes much more sense to focus on the development of the MEGA branch since the ESP8266 platform is still growing fast (with standard 8MB of flash memory on an ESP-01 module in Ali as latest record) and the ESP32 is becoming more mature. The Wemos D1 has 16MB of flash, at which point it becomes possible to run interpreters like MicroPython on a ESP8266.

I was looking at that, to run ESPEasy as python instead of C++. That would make it possible to create rules using (micro) python. Another option is to have a hybrid: ESPEasy in cpp and the rules in python.
With ESPEasy-python whole new possibilities would open up...

[frank]

I hope that the mega 2560 branch will ferther develop

Don't get your hopes up, there is very little reason to spent a lot of time on this branch. The Arduino platform is outdated, even the DUE has only 512KB of flash memory and it's CPU still slow. The Arduino platform is growing WAY to slow...

It makes much more sense to focus on the development of the MEGA branch since the ESP8266 platform is still growing fast (with standard 8MB of flash memory on an ESP-01 module in Ali as latest record) and the ESP32 is becoming more mature. The Wemos D1 has 16MB of flash, at which point it becomes possible to run interpreters like MicroPython on a ESP8266.

I was looking at that, to run ESPEasy as python instead of C++. That would make it possible to create rules using (micro) python. Another option is to have a hybrid: ESPEasy in cpp and the rules in python.
With ESPEasy-python whole new possibilities would open up...

I understand that and that the focus will en must be in that direcion because it is the most inportant. But i hope that this stays a little fun side project