I can't fully explain what we are doing as that would break very restrictive NDAs, but suffice to say the ONLY thing i can do is 'print' the data. Printing it in CSV is very effecive as I can pass it to other software without alteration, e.g. MathCAD and Python. I can also read it as it flies up the ...

I am not being aggressive, just exact. That is just the way engineers are.

There is no built in limitation in the windows drivers other than the types of UART supported (i.e. the 16C550 and its friends). Strictly, the rate limitation is down the the serial chips internal buffer size, the maximum ...

Clearly you don't want to fix your software and this really is your problem. It is a pity as it otherwise would fit our purposes.

You are wrong about hardware limitations and wrong about the windows API and even wrong about the definition of baud.

To cover the last point first, Baud is the same as ...

Hightest number I found that works is 1, I did not try any others.

High numbers are caused by Windows rubbish management of USB-Serial interfaces that means the next available com port is incrememted each time a new USB device appears on each USB port. 5 different usb devices pluged into 5 ...

In labview you can wrap each block in an interator (called a 'for' or 'while', but that's just a name). I can't find anything simplar in FlowStone.

The iterator becomes a container for the schematic within the iteration wrapper, and the ports externally are either mapped to indexes of that loop or ...

I should have included, the logging needs an option for non-verbose.

Currently the received data is also logged which creates too much clutter in the log and in my case also causes a crash.

Surely there is no need to log received data if the data is also available on the output pin?

1:
It is a pain to keep visiting the toolbox for every widget.

Taking a leaf out of Labview, how about having it such that clicking on a port and dragging creates a pre-connected constant or readout entity of that type depending on if it is an input or outpur? Arrays would produce multi-line ...

I am evaluating FlowStone and once i worked out how to use it I ran into some fundamental problems:

Firstly, COM ports with large enumerations don't work.
If I set the device to COM22 it fails, if I set the device to COM1 it works.

More of a problem, COM ports are simply broken.
If I set the baud ...