Hi,
Thank you for your interest in our software.
Answering your question:
1.) You can make buttons. There are custom button codes from codes 20000-20999, these buttons can call the same macro numbers directly,
so for example button with a code 20000 calls the M20000 macro which is a .txt script file in the profiles/yourprofile_macros folder.
If you create the M20000.txt file and put some script code into it then pressing the button will call and execute this macro.
Currently there is no homing function available in the scripting language, please see the Macro_capability_detailed.htm file in the documentation folder of the UCCNC installation,
it lists and describes the functions. Also you can check the macros in the macros folder to get some idea about the programming syntax.
2.) The screenset is loaded by the UCCNC in the following way:
- When you start the UCCNC, it first loads the profile file.
In the profile file there is a key:
[Screensetsettings]
mainscreenfilename=Defaultscreenset
This defines the name of the screenset file, in this case the name of the file is Defaultscreenset, the extension is always .ssf and this is also a textfile with script inside.
The screenset files directory is the /screens folder.
The screen file has functions for the TAB screens, backgrounds, buttons, labels etc. definitions.
Basicly what is on the screen is all defined in the screenset file.
The functions in the screenset file are yet undocumented though.
3.) Please post that code to let me check.
4.) The toolpath can be rotated with using the mouse, not with keys and also with the buttons on the screen.
Move your mouse pointer to the toolpath viewer. Pressing and holding the left mouse button down and moving the mouse will move the toolpath drawing.
Pressing and holding the right mouse button down and moving the mouse will rotate the toolpath drawing.
Pressing and holding the middle mouse button down and moving the mouse up/down will scale the toolpath drawing.
5.) This question is a bit complex, so let me just give you some ideas.
- The tool center pointer always shows the actual position, so how it moves is always how the machine moves.
- I advice to check the actual feedrate DRO to see the actual feedrate, I mean watching the toolpath I'm sure you cannot really determinate the exact feedrate actually ongoing, better to check the number in the DRO.
- The UCCNC imports the Mach3 accelerations and velocity parameters for the axis correctly and exactly, but you may revise that looking at the config page of the UCCNC.
- If your code is built from lots of segments and if the motion profiler is in exact stop mode then it just can't accelerate up and you can set it to constant velocity mode.
The constant velocity mode in the UCCNC is much more configurable in the UCCNC as in Mach3, so you may also want to tune some parameters on the configuration->general configuration page to make the constant velocity work the best for your machining jobs.