Timeline for Arduino Mega 2650 + Matlab/Simulink - Serial decimation
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 31, 2017 at 8:48 | history | tweeted | twitter.com/StackArduino/status/869837887239589888 | ||
| May 30, 2017 at 23:54 | comment | added | kando | @EdgarBonet - Adding a rate transition block before the serial transmit helped the decimation. As stated in Michel's answer, the data otherwise was sent to the serial buffer no matter how long I waited to read it. | |
| May 30, 2017 at 19:35 | comment | added | kando | @EdgarBonet You are correct that using a 3rd party tool obfuscates even more of the things going on under the hood. | |
| May 30, 2017 at 19:34 | comment | added | kando | @EdgarBonet Decimation in the standard sense is easy. I could delay my read requests, such that they only occur every X board cycles. My concern is that if I start a read, and the read requires 10 board cycles to complete, then the variables which I am reading will change 10 times before I finish reading. If this occurs, will these variables be rewritten to the serial queue before I finish reading. If so, this could create racing conditions in which a read is occurring at the same time as a write. | |
| May 30, 2017 at 19:18 | comment | added | Edgar Bonet | Decimation is not a problem, and is quite easy to do if you program the Arduino the "standard" way. The problem is you are programming with a tool that abstracts a lot of things away. You will then have to check whether this tool provides a "decimate" block. | |
| May 30, 2017 at 18:36 | answer | added | Michel Keijzers | timeline score: 1 | |
| May 30, 2017 at 18:32 | history | edited | kando | CC BY-SA 3.0 |
added 345 characters in body
|
| May 30, 2017 at 18:25 | history | asked | kando | CC BY-SA 3.0 |