Configuration Options #44
Replies: 8 comments 14 replies
-
|
I personally was leaning towards desktop/mobile app as it's the most flexible. I can easily whip up a POC or a fully fledged version with the changes needed for firmware also |
Beta Was this translation helpful? Give feedback.
-
|
I am not sure what its best but I wonder if we could start with a file based config and then if we get to the point where we want a full drag desktop app we can support that by generating a config file with that desktop app? |
Beta Was this translation helpful? Give feedback.
-
|
Has any progress been made in this area? If not, I've got a surprise for you guys and could use a bit of help cleaning up and debugging. |
Beta Was this translation helpful? Give feedback.
-
|
@mcurtiss1992 Looks nice. I wonder how to use it. |
Beta Was this translation helpful? Give feedback.
-
|
Oh I should also mention I've only got this implemented on the hardware. If you guys like the direction I'm going, I could use help porting that over to the emulator. |
Beta Was this translation helpful? Give feedback.
-
|
Okay I've created a branch for my configurable firmware. Please be kind when looking through it. My C is rusty. It still needs quite a bit of work in terms of stability and sometimes requires manual editing of the json when something gets out of sync or a file is missing, but I don't want to do a bunch more work on it unless it seems like the correct path forward. Anyways this is the branch: https://github.com/mcurtiss1992/OMOTE/tree/configurableFirmware |
Beta Was this translation helpful? Give feedback.
-
|
@KlausMu Oh yes. Sorry I wasn't super clear on this, but it's basically a proof of concept. I wasn't really sure how much trouble the omote would give me as a mini webserver. Turns out a lot. But I was able to work through the big problems. One big problem was serving large json files. It didn't take much to burn up the available memory, but I was able to compensate for that by splitting up the files into smaller files and transmitting the files as blobs rather than entire packages. The frontend would be implemented inside a framework in any kind of "production" version. This is just me proving it can be done. As far as functionality, I've currently got all of this implemented in the gui POC along with rendering on omote side:
@CoretechR Thank you :) If you'd like, I could create a video walking through what's currently possible. I'd also be available to walk through how the omote side works. I had to make quite a few changes to the firmware, but it is built using all the same principles from the original project. The core methods and functionality have all remained the same. You can still hardcode config if you want as well. Oh. You can also turn the webserver on and off. That's in settings (setup mode). |
Beta Was this translation helpful? Give feedback.
-
|
Hey all. Sorry I started the config tool and disappeared. My mother passed away on 4/1, so it has been a very difficult time for me and my family. I intend to pick the config tool back up at some point, but currently just trying to focus on my day job and stability. If you guys would like to progress further on this, I’d be open to meeting with someone that would like to take point on it. |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
So I was looking to start on a simplified configuration option inline with new features to facilitate easier testing and also given the current way is in code.
The options I see
There are pros and cons to each. Some are:
Thoughts.
Beta Was this translation helpful? Give feedback.
All reactions