When CuteCom is monitoring the serial port for data, Octave reads data properly for the duration of the loop. I thought this was a timing problem, and I was curious to see what was being read from the port directly using CuteCom. The strange behavior starts here, as when I run the command-then-read sequence in Octave by one time everything works, but in a loop the data read in is only the x-axis. The STM device reading the serial commands waits 1ms between bytes it reads in as well, because previously it was able to send many strings for the x-axis before it received the 's' command. This can be worked around by adding a 1ms character delay.

Using GNU Octave and its instrument-control package I can read in all coordinates, but sending the string 'xs' will cause the device to only receive the 'x' byte and it will relay x-axis data continuously.

sending the command 'xs' will return a single 6-byte packet of the x-axis angular rate data (maybe something like '+00021'). Using CuteCom I am able to interact well with the device e.g. It waits until it receives the 'x', 'y', or 'z' commands to send data and then it continues to send data for that coordinate until a stop bit (anything other than 'x', 'y', or 'z', I usually use 's') is sent. The gryoscope is read over SPI onto the microcontroller and then the micro relays the data to the computer. The device is a microcontroller board (STM32F401C Discovery board) with a gryoscope. b) Learn more about how large-scale systems work and thought process of designing a new system.I am having difficulty reading a USB virtual comm port into GNU Octave, and there are some bizarre goings-on that I would like some input on.Ĭurrently I have a USB CDC virtual comm port device that I programmed to respond to commands over serial with the computer. This is a collection of links/documents for the following use cases: a) Prepare for a system design or open-ended rounds. Along with that, there is a recent trend for companies to have an open-ended interview with system design questions, which is at times hard for engineers of all levels if they haven't gotten the opportunity to work on such systems themselves. What this repository aims to achieve, is for software engineers and students to get a rough idea of how the thought process of designing a large scale works and how big companies have managed to solve really hard problems. I do not want to give the impression that it's something that can be learnt in a month. Learning about and implementing large-scale distributed system is not easy. System_design - Preparation links and resources for system design questions

Gnu octave electrical engineering