Just wanted to mention that your videos are extremely great. Easy to follow, well explained and just overall pretty awesome. Please keep the content coming!
I cannot imagine a more complex way to make a machine timer. It clearly takes a million lines of code to draw a box on the screen. Can't wait to see how complicated it is to actually drive the machine hardware.
I think this is a whole lot simpler for me than writing a bunch more embedded code. No small part of this is the skill set of the person doing the work. Someone who doesn't know C# and WPF would probably have to invest more time learning these tools than writing an embedded solution. Since I know both, I can choose the right balance for me. And for me, this is the simplest approach that will be easily configurable and allow for saving and loading profiles (that have temperatures and timing for different molds).
Thank you, I appreciate you sharing some more details! I had previously started looking into using something like a DWIN/NEXTION HMI/touchscreen. These have tools that are supposed to help you get screens set up and running easier, but in my experience using proprietary software like that usually ends up burning you. I like this option for the cost and control. I'm always concerned about Bluetooth connection, but from looking into TOUCHdro that you mentioned in a comment the connection seems to be very solid. Thank you again for sharing. As a mechanical engineer I have a steep learning curve ahead but this looks very interesting!
I just updated the description for this video with links to three previous videos I did about using a Nextion display and an STM32. That will give you an idea of what's involved.
Very interesting. Thanks for sharing these details. I don't really have any projects to do such developments, but Avalonia certainly looks interesting. So far I did not make the transition from Arduino IDE to PlayformIO, but it looks a lot more user friendly in VSCode than the box standard Arduino IDE.
Platform IO is definitely much nicer than the Arduino 1.x IDE. The Arduino 2.x IDE looks like it might be much better, but I have not used it. As a software engineer, I suspect I would still prefer Platform IO simply because it has the power of VS Code (such as for Git integration).
Oh, man, I haven't heard about Ada in decades. I never learned it, so can't compare it with Rust. All I can say is that Rust is a very new language and is becoming more and more popular. With Microsoft starting to use it in Windows and people starting to use it in Linux, it seems to have a good future.
There are PID libraries, so that part isn't hard. For the thermocouple, I plan to use a thermocouple amplifier that connects via SPI. I have one, but haven't had a chance to hook it up yet.
Interesting. It seems this was only worth it because you are that much quicker programming in C#, compared to what you used before. Using Android for 5 buttons and a DRO looks quite a lot more complicated than it needs to be. Especially since the interface could just as well be programmed the same way, without using images as the background. And using a generic Android tablet, imo doesn't feel necessarily commercial. A Arduino Due could do everything just as well, all on a single board. If you truly want a wireless display you'll need a wireless shield as well.
One of the main reasons for switching is that I have a lot more functionality I want to implement than I've shown or mentioned. I'm going to be making the functionality configurable for different machines and scenarios, which means controls will move around on the screen, change size, etc. I have a very good understanding of what it would take to do this from the micro controller and didn't want to devote that much of my time to make that work. As to not feeling commercial, check out TouchDRO for an example that people love.
@@JohnSL thats what I said. The only reason for switching is you being more comfortable in this environment. While I'm unsure what other features you want to add, unless you want to diy yourself a Heidenhain controller it's still way overkill. On how commercialy viable a tablet version is, I'm unsure about. I always thought infection molding machine owners are more business oriented (contrary to a mill/lathe), where a self sourced tablet may not be as interesting, but I may just have wrong demographics in mind for that.
Ah, got it. I didn't cover the target market in this video (I think I may have in the previous one). This is intended for desktop injection molding machines like the Buster Beagle 3D. So the DIY market, not for industrial machines.
Is this adaptable to g, m code for CNC application, for say, router, mill, lathe use? Fascinating for what I think I’m seeing as applications, though, I’m pretty dumb on this. Shame on you, for having a life and going skiing.😂
I imagine it would be. I know there are open-source g-code systems like grbl that you could probably modify to allow for some integration. On the other hand, there is also LinuxCNC, which is already very capable with a UX.
