forum

... reason for this behavior: 1. On SDK 7.16, in case of active use of FLASH memory, the process of defragmentation of the file system may occur and WatchDog may be triggered. With this behavior, problems with sending confirmations to the controller are also possible. 2. In addition to the active ...

... value of sensor stopped changing, device stopped reacting on changing switch state from controller ui. Device is still alive - there is external watchdog that reboots z-uno if it does not ping it within 40s, besides device has physical button to turn off all switches and clicking it acts as expected. ...

This would explain the issues I was seeing when I ported my app from Arduino to Z-uno..my gut feel was that it may be a stack issue and this seems to confirm it as a prime candidate, especially as the issue has gone away on the new release and I noticed in the release note there had been a lot of st...

Arduino boards has AVR microchips installed on it. Z-Uno uses another architecture (i8051). AVR has about 256 bytes of stack and doesn't run another code at the same time. Z-Uno has just about 130bytes of stack and it runs two firmwares in the same time: main firmware that makes all Z-Wave processi...

-

Can I shamefully self-promote a script of mine? https://github.com/petergebruers/Z-Uno-BH1750 In that script I wrote: // Global variables // Z-Uno is a SOC with limited resources compared to e.g a Raspberry Pi // or esp-32. To limit stack usage and parameter passing and data shuffling, // I tend to ...

Arduino boards has AVR microchips installed on it. Z-Uno uses another architecture (i8051). AVR has about 256 bytes of stack and doesn't run another code at the same time. Z-Uno has just about 130bytes of stack and it runs two firmwares in the same time: main firmware that makes all Z-Wave processin...

Arduino have a few times bigger stack and very different memory layout. It is also different in passing pointers and have more registers. Z-Wave chip is based on 8051 arch - much more limited one.

Check this nested call: AcqusitionMotor->ReadForce->ReadResistance->ReadVoltage

Thank you @PoltoS. I've tried enabling the output Log on UART0, but it didn't appeared (I'll check it again) -> EDIT: I didn't know about that codes and the meaing! Thank you! The stack usage shouldn't be that high (the same code runs in all arduino boards I tried). How big is the stack? Any way to ...

We have cheked your sketch. Clearly, it overflows the stack. You can check this in the debug output once enabled in the ArduinoIDE. We suggest to use less float (don't multiply by g and then device back). Try to minimized numbers of nested functions and make more glabal variables and/or make them sm...