Search found 48 matches
Re: SPI
I have found 2 problems with the current SPI implementation (2.0.6 and 2.0.7): The lowest frequency that I was able to make working was 1MHz (1000000). For lower frequencies no frame was generated. I tried with 100kHz, 500kHz and 800kHz. The CS/SS line is not generated automatically. It needs to be ...
- 18 Dec 2016 12:24
- Forum: Z-Uno
- Topic: Error in <string.h>: Typedef redefinition with different typ
- Replies: 2
- Views: 3796
Re: Error in <string.h>: Typedef redefinition with different
Well, I found the second place where size_t is defined:
File 'ArduinoTypes.h':
File 'string.h':
File 'ArduinoTypes.h':
Code: Select all
typedef unsigned short size_t;
Code: Select all
typedef unsigned int size_t;
- 18 Dec 2016 12:10
- Forum: Z-Uno
- Topic: Error in <string.h>: Typedef redefinition with different typ
- Replies: 2
- Views: 3796
Error in <string.h>: Typedef redefinition with different typ
The include file 'string.h' that is provided with the Z-Uno (version 2.0.6 and 2.0.7) contains the following type definition: typedef unsigned int size_t; After including <string.h> into my program the compilation generates the following error: error:typedef redefinition with different types ('unsig...
- 11 Dec 2016 19:09
- Forum: Discussions in English
- Topic: Z-Way 2.2.4 not supporting HTTP POST requests -> Resolved
- Replies: 7
- Views: 10105
Z-Way 2.2.4 not supporting HTTP POST requests -> Resolved
From an third party application I am using the Z-Way JS API to access my Razberry device ($Url/JS/Run/...). More precisely, until revision 2.2.0 of the Z-Way server I was using HTTP POST requests, which worked fine. After upgrading to the Z-Way server version 2.2.4 the HTTP POST requests were not ac...
- 22 Nov 2016 22:37
- Forum: Z-Uno
- Topic: Interrupts example
- Replies: 14
- Views: 15809
Re: Interrupts example
Any idea when the new firmware revision will be available that supports user interrupt routines?
- 06 Jan 2015 21:59
- Forum: RaZberry
- Topic: Error on API after upgrade to 1.7
- Replies: 29
- Views: 28848
Re: Error on API after upgrade to 1.7 - resolved with 2.0
The HTTP response time issue of the z-Way server 1.7 seems be resolved with revision 2.0 (2.0.1-rc6). After running the z-Way server multiple days no HTTP timeout error could be observed. Here is an update of the z-Way response time distribution, including now also the results from Z-Way 2.0. The re...
- 26 Dec 2014 19:35
- Forum: Discussions in English
- Topic: JS API response difference between z-Way 1.x and 2.x
- Replies: 6
- Views: 6020
Re: JS API response difference between z-Way 1.x and 2.x
Good question! Once it is fully validated that my system works with z-Way 2.x there should be nothing that blocks my from switching definitively to the new version. But for the moment I have still some issues with the alarm command that behaves differently between 1.x and 2.x. I encountered also HTT...
- 26 Dec 2014 11:26
- Forum: Discussions in English
- Topic: JS API response difference between z-Way 1.x and 2.x
- Replies: 6
- Views: 6020
Re: JS API response difference between z-Way 1.x and 2.x
Sorry for not being sufficiently precise in my description; But yes, I am using /JS/Run as this is described in the Z-Way Developer Documentation (version 2, sections 1.3.3 and 3). The URL to call the function is therefore: http://192.168.1.21:8083/JS/Run/Get_TestArray1() Please reconsider the way t...
- 24 Dec 2014 18:24
- Forum: Discussions in English
- Topic: JS API response difference between z-Way 1.x and 2.x
- Replies: 6
- Views: 6020
JS API response difference between z-Way 1.x and 2.x
Hello, Javascript functions accessed via the JS API may return different responses with z-Way 1.x and 2.x. While the z-Way 1.x JS API recognizes correctly that a function result is an array, the z-Way 2.x JS API has sometimes some troubles, as the following examples are showing. Custom functions acc...
- 24 Sep 2014 22:59
- Forum: RaZberry
- Topic: RaZBerry High CPU Usage
- Replies: 19
- Views: 22824
Re: RaZBerry High CPU Usage
Just found this thread discusses some problems that are also discussed in thread viewtopic.php?f=3422&t=20397&start=20#p52396. Both threads mention HTTP request timeouts, high CPU loads, etc.