rosssmyth / fisa

Ferris Instrument Software Architecture

Hi, my name is Ross Smyth. I am an alum of Michigan Technological Univeristy and currently work at Orbion Space Technology doing data analysis and software development. Topics of study I enjoy include the following:

• Software
• Systems Engineering
• Spacecraft engineering
• Digital signal processing
• Communication protocols

Checkout my website here

fisa's Issues

Address parsers status

• USB
• TCPIP
• Serial

I consider optional:

• GPIB
• VXI
• GPIB-VXI
• PXI

Error checking for double colons

The VISA standard indicates that double colons are required in addresses. Because of this the USB parser just skips over the character following the first colon assuming that it is a second. It would be good practice to instead provide an error.
Tasks:

• Check for second colon
  Should this be a guard or in the match body? Doesn't really matter to me I think. Guard may be cleaner.
• Add "MissingColon" error to error enum
• Return the error
• Add UI tests

Determine MSRV

This is pretty low priority and I personally don't care what it is. But I would like to know what it is so other people can know.

Async?

Is async worth implementing? My thought is probably yes. At least feature gated. I'll have to do a survey of async USB and serial libraries as I know TCP libraries exist. For runtime Tokio is probably the way. If not then maybe smol?

Address builder

Should probably make a builder API for making addresses programmatically.

Is it valid for a serial number to have a colon?

Currently the USB parser considers a serial number to be done when either:

1. The str ends
2. A single colon is met

If a serial number can have a single colon then this is invalid.

Other thoughts:

• Theoretically the serial number could have two colons as long as the immediate characters after the colons are not numbers. But this sounds too complex for me to think about.

Book

Writing books is good. For 1.0 writing a book on how to use this library and also a bit about VISA would be good.

Licensing?

I'm a bit unsure on what license I want to use. But I think MPL is a good one.

IO

Once parsers are done the actual IO must be setup. I'll have to give this more thought, but making some traits for interfacing with the IO types is probably the way to go.