Hello Olli, the gaps could be there because the XDK is prioritizing sending data over acquiring data. Is it a C-Program or something in Mita? If it was a C-Program, a good design would have a data acquisition task triggered by a timer or interrupt which acquires the data and pushes it into a buffer and a second task that is triggered by a certain amount of data present in this buffer.  Depending on the priority selection this enables the scheduler to avoid dead time where a task is waiting for some external interaction to happen. Best regards, Francisco LL. ... View more

Hi Taz0r, I see the documentation coming from Rexroth has an outdated link.  The IoT Gateway builds on top of the SendAccelDataOverUdpAndBle example application provided in the XDK Workbench. Basically in order to work, you should modify the parameters in that example to stream data to your PR21 and then configure the IoT Gateway software.  Best regards, Francisco ... View more

Hi Adooby, there is no simulated environment provided in the XDK Workbench. What is Your concrete use-case? What is the target of your evaluation? Best regards, Francisco ... View more

Hi mainul, the code in this example will wait for new data to be available from the sensors before publishing.  In my configuration, the noise sensor is set to 20kHz ADC sampling with 30samples per RMS output -> 20kHz/30 = 667Hz (RMS) and T_Sampling(RMS) = 1/667Hz = 1.5ms The BMA280 is set to 500Hz sampling frequency -> 2ms Sampling Time. I don't see all your configuration, but along with the sensors, this sampling times will add up an influence the MQTT output data rate, Basically this example was meant to be simple to understand but this simplicity restricts it to be for low  data rates (1s). Other programs that need higher performance are more complex (like the datalogger) and require better understanding of the MEMS interrupt engines and the RTOS inter-task communication system to work out.    Best regards, Francisco Llobet ... View more