I have tested this on a netbook with basic Intel graphics and an Intel Atom processor with good results.
The default layout was created on a machine with highres and widescreen, while the controls are self-scaling there are limits... So if you are using low resolution and/or on a 4:3 monitor you may need to stretch things around a little.
MM3 Installed properly and opens as it should :-) Very impressive looking interface!
I know you have worked really hard on this, so I hate to "ask for more", but...is there any chance you could post a "getting started with MM3 guide"? Just some salient points about the various "View Items" would be great. Or, if you would prefer, I could simply post a series of questions about each "View Item" and you could respond in quoted text thus generating an impromptu FAQ Getting Started Guide....
Thanks for sharing MM3, I look forward to figuring it out and using it!
Hello again Brad,
Got MM3 installed on Mill machine PC. And docked,moved, resized to get it in my 15" lcd First thing i might ask is where and how to start configuring MM3 to control machine? Go slow please
Machine Manager has a large and growing feature set and all is undocumented.
I have started compiling some documentation and in time there will be a detailed manual.
The logical place to start was the Configuration Editor and I have just completed the first version of the overview. I will eventually create tutorials for using each tab, but hopefully this will provide an OK start.
There were some minor bug fixes and performance enhancements. Some of the GUI controls were updated for improved scalability and stretching. This should make it more usable on lower resolution displays.
No problem, I hope it gets you, Fish and others a little further along(at least until I get more docs done).
It is very important to remember that Machine Manager is meant to be a general purpose machine automation application/framework. The G-code interpreter is just one of the many components. What this means(especially for people using if for CNC machines) is that there may be a LOT of extra settings that are never used.
I hope the extra settings does not scare too many people away. Unfortunately it seems that capability and complexity go hand and hand so to offer a really flexible system requires that I also offer a complex one.
Good luck, let me know if there are any specific questions/roadblocks that I can address.
You may also notice that there are some Dynomotion Data (Axis, Axis Group, and Interpreter) that is not mentioned in the documentation.
I have tried to maintain the exisitng DynoMotion nomenclature so hopefully the Machine Manager version of the settings are easily recognizable from their counterparts that are found in KMotionEXE, init.c files and the existing DynoMotion documentation.
Do let me know if any are unclear and I will be happy to clarify.
Not to open another can of worms, but one thing that would be nice is if there was a install of MM3 that only has the configuring options needed to run a Basic 3 axis CNC mill.This would help to get machines up and going. And as user gets familiar with MM3 than they could add other options as needed.
But as i said this would more than likely open up another can of worms, with updates and trouble shooting software on your end.
I did make an attempt to get it mostly working for a three axis mill/router setup.
Are you suggesting to hide all the controls except G-Code specific ones? if so it would be pretty easy to save that screen layout and offer it as a separate download.
I guess we would then only need the G-Code Axis Manager, the G-Code Path Viewer, the G-Code Console and the Configuration Editor.
There will still be some very simple scripts to build in for to link the your existing C programs (for things like homing). But they are quite trivial one-liners. All axis and Interpreter initialization is handled in the Configuration Editor(no need for Init.c unless you really want to)