ximidar/flotilla

3D Printing server interconnected over a NATS server

flotilla's Issues

expand status to collect temperature output

Flotilla Status needs to collect temperature data and share it over nats

Create tool for flashing MCU

Expand the Serial Node to flash the mcu. Use the open source program that I can't think of the name of yet

Create meta processor that will process every file and get information out

In the FileManager create a process that will grab meta data out of each file. It should read the entire file and calculate stats for each file. This metadata will then be attached to each file.

Create Build and Test system

Create a docker build system that also runs tests.

• Run all tests before building anything
• Add all built binaries into a bin folder.
• Create a github webhook to post binaries and run builds after every commit.
• Put all tests in their corresponding repository and package. Leave only the code that cannot be apart of a different repository(commonTestTools, Flotilla System Test, ect)
  • Fix any code or import statements that need fixing
• Create tests for any untested code

Create Node for Web Interface

Create a Webpage that can control the printer.

Expand Fake printer to accept more commands

right now our fake printer will only provide output for ok. expand it so it can accept temperature change commands and movement commands. look into other commands to expand use and work on it.

[GUI] Exploring WASM

Explore using WASM as a way to access the flotilla API

Create Wire Frame for basic interface web and touch

whiteboard out an interface for web and touch since they are both using vue maybe we can share vue objects between them

Add a way to use CLI tools on a completely different computer

Add a feature that will look on the local network for a Flotilla instance to connect to. Make it so you can use the cli tool from any other computer.

[GUI] Write leveling wizard

Write a way to set the z-offset so the machine can print correctly. No need to make it fancy. Just a basic tool will do for now

Make all repos pass the Go Report Card

Most of our repos are abysmal with the Go Report Card. Update all repos to pass the report card

Golint Issue

Recently I have started using a Golinter. This linter doesn't think that the style I use to write code is good for Go. We should try to follow the linter's style guide. This issue is here to tell @Ximidar to reformat all the code to fix all of the linter's issues.

Fill buffer with user input

Prioritize user input over the currently playing file. When a user inputs a line play it as fast as possible. Also figure out how to transition user input when playing vs not playing.

Write Docker Compose script that will bring up multiple containers with all the different nodes running.

Write a Docker Compose that will bring up a testing environment to help write the GUI

investigate using rust for the serial monitor

Go doesn't really have a great serial package, It works, but I'd rather have the tools that C++ had. But I'm using this project to learn new things. Rust is a language I'd love to start using. I don't know how well it can connect to NATS, but it probably has better Serial Tools than go.

Create Dry Mode

Add a dry mode option to flotilla so I can play any gcode I want and it will not turn on the heaters.

Add webcam support

Create a program that will collect webcam data and share it

Build Node for Touch interface

Build a node that will handle a desktop touch interface. Explore Flutter. But in Reality we will probably be using the community version of QT and C++

Create Node for Executing all Nodes

Create a Common Node that will fire off all Flotilla nodes in a single executable. This node will also collect the stdout of all Nodes and consider it logging. This node will be responsible for proper startup / shutdown of server.

Investigate webasm for holding a slicer

I have never been one for building websites, but it seems to me like we could compile the cura engine to webasm. We could then create a slicer that can use the browser and user processor and ram to slice an stl. It could be a static site sitting in an S3 bucket.

[GUI] Write status screen

Write Status Screen

write the status screen for the GUI. This status screen should include the following:

• Temperature Graphs
• Motor Control
• Temperature Control
• Print Status
• Pause / Resume / Cancel

That will do for a start.

For extra you can find a cool way to display Flotilla on the main screen while nothing is happening

Extend File support to show plugged in usb sticks

detect USB plug ins and attempt to mount them and show them in the available files

Add serial monitor to cli

Add a simple serial monitor to the cli tool. This would just dump the Sent and Received data directly to the console.

investigate issues with the serial monitor

When disconnecting and connecting the serial is off by a few characters. investigate

Server does not pause

I recently added a pause button and it seems like after changing the status the system will not pause. It just keeps playing the file. Alter the FFS and the status setter so they set the status correctly and they do not get locked.

[GUI] Brainstorm other wizards

Think of other wizards to write and put them here. Outside input is also welcome if anyone is listening.

[FR] Create Node for Configuration

We need a node that will keep track of configuration variables for the rest of the nodes.

Create authenticated access to NATS

Figure out a way to enable SSL for NATS and Server. Then also figure out some sort of API key / User login to use the NATS / Server routes.

Create a way for multiple websockets to be open

Currently the webserver can only have one websocket open. Please expand the API to allow for multiple connections and multiple websockets open.

Update NatsConnect to only take in certain options. Supply the rest

NatsConnect is supposed to make connecting to the NATS server easier and provide a painless way to take care of the NATS connection that can be coded into every node. So far I have only written a dumb reconnection routine for nats. I should recode it to follow nats.Options instead.

It should follow this flow.

1. Create a NatsConnect Object
2. Allow the coder to change the options to their hearts content
3. Provide a Connect function that will return the nats.Conn object and an error
4. Take care of any conn errors by using nats.Options callbacks.

Create UI Plan

Problem

Currently our UI is suffering from not being planned out. I am simply adding in functionality and the result is a bad mess. I need to create a plan for the UI, even just a document with terrible screens showing the outline of each page. This UI plan doesn't need to be extremely detailed, we just need to start defining the basic look of the website.