Hello.
I'm currently working on version 2025.04.12.
However, in my test environment, I'm having the problem that I can no longer show and hide window panes using a button. I also no longer have the option to touch an individual edge.
Hello.
I'm currently working on version 2025.04.12.
However, in my test environment, I'm having the problem that I can no longer show and hide window panes using a button. I also no longer have the option to touch an individual edge.
2025.04.12.version introduced "Screens" for panel management. Check Demo profile for example how to use them.
I' m not sure what do you mean with "option to touch an individual edge". There was an inconsistency in measuring routine in previous versions which was fixed for this one. "Inside Edge" and "Outside Edge" are now used instead of ambiguous "Find Edge"
Yes, I've now found the new ones inside and outside Edge.
I also looked at the demo with the screens. But without a computer science degree, I won't understand it.
What's even more annoying is that not a single script works anymore.
So I emptied the script folder. But even then, the original homing doesn't work. The GUI says, "Limit switches are active."
Screen files are really simple and you don't need any degree. Demo profile provides all examples needed.
Some commands were renamed to be compliant with coding standards.. For example "startcode" was renamed to "start_code".
And commands for dialogs are greatly improved.
You can not start homing if you have active limit switch. Release switch any you'll be able to home.
Tutorial for screens is in the making.
Homing funktioniert perfekt mit der alten Version. Es funktioniert einfach nicht mit dem neuen.
I use a Normally Open switch on X and X, which is active within the limits. As soon as it goes out of the limits or reaches the reference point, it goes off again, and the controller knows that the end has been reached.
On Z, I have a Normally Close switch that goes off when the reference point is reached.
That worked for years. Now it no longer works with the current version.
Can you post a screenshot of the IO panel for these limit switch inputs?
You can post directly to the [email protected]
I've now spent time making the videos. I noticed that I've already connected two additional switches, but haven't configured them. The older version ignored them. The newer version doesn't, hence the GUI announcement.
Next problem
When I perform gantry squaring, Y is then behind the limit points. When I then try to move Y or homing from that position, the GUI again says limit switches are active.
The previous firmware version contained a bug where limit switches weren’t checked before homing (and similar movements). In the new release this has been corrected, which is why you’re seeing a warning.
In your case the warning simply indicates an unconfigured switch. However, if that were a real limit switch the machine could crash without proper safeguards. Please configure your limit switches correctly—once that’s done, homing will work as expected.
I used this code to display the PWM setting for my minimum quantity lubrication.Code:expr "res = _hw_output_freq0 / 457" "MMS-Level ml/min:"
Now the display always stays at 0
No you did not
never worked because there was never parameter named _hw_output_freq0.Code:expr "res = _hw_output_freq0 / 457" "MMS-Level ml/min:"
There was parameter _hw_output_freq1 but in version 2023-05-15 this parameter became "indexed" (pipe character)
You are also missing format specifier which was always needed and probably defaulted to 0.
So if you want to read PWM frequency of output pin 1 you should use
So none of this has anything to do with latest version.Code:expr: "res = _hw_output_freq|1 / 457" 2 "MMS-Level ml/min:"
Let me know if you have any other issues. I'm glad to help.
I've been working on the screens a bit now.
I'm facing four problems.
1. I have a button for "Edit Code"
that loads the code into the corresponding tab on the default screen.
If I've created an area for edit code in a custom screen, it doesn't load it there.
2. In the custom screen, there's no way to pass the code back after editing so that it can be run.
3. A defined background for 3D in the screen file has no effect.
4. The background for tabs like output, edit code, log, etc. defaults to the color set in the settings. In the custom screen, it's a different color.
I'll fix this in next bugfix, Probably before Monday..
Button of rights are hidden by mistake and I failed to notice it.
EDIT
I've fixed it. Those dialogs are not supposed to have ok/close buttons by I also hide apply which is actually needed here.
Let me know if there is something else.
With pleasure. Once you've gotten to grips with it, completely new possibilities for a GUI open up. I always enjoyed the fact that everything is on one screen in TNGv2. However, if you want to use a touch display, you have completely different requirements for the GUI. The ability to work with additional screens is very convenient for me.
Is it also possible to divide the screen into columns and rows?
So far, I only see columns, and for each column, the defined areas below each other, like in the text file.
Would it also be possible to divide the screen into top and bottom sections, in which you would then have, for example, four columns at the top and only one at the bottom, but across the entire width?
Screen is divided into 5 columns (two left, mid and two right) but you don't have to use all 5.
Each column has theoretically unlimited number of panels stacked.
Rows are not possible unless you consider that those stacked panels are rows.
Splitting screens into top/bottom is not possible but it is good idea. I will consider it for next release.
I have another question.
How can I limit an area?
For the width, for example, I can do this with minwidth="200" maxwidth="200".
How do I do it with the height? I've tried minheight and maxheight, of course, but that doesn't seem to work.
And is it possible to hide scrollbars?
Hello.
I now have version 2025.05.02.
The OK button is now available for Edit. I don't understand why they don't just put a check mark there like with the settings. But that shouldn't be my concern.
The problem is that when I load code and then click the Edit button or select Edit in the menu, the code loads into a separate window.
Something else I noticed:
Menu="default"
StatusBar="default"
Doesn't work. Or I don't understand it.
The menu and the status bar are always there, even if they're set to "Hide" in the settings.