Output / indication of presence of CV mode on the toolpath

[cncdrive]

I don't have time to make videos, sorry. And I'm also not good at making videos.
But as I said it is simple as 1x1.

Try to switch the THC on, do M3 to turn the switch on. And ofcourse set the antidive threshold % to other than 100%.
Because there are no inputs in demo mode you could use the virtual THC inputs, assign hotkeys for them in the hotkeys menu, to the virtual THC up/down and arcon signals.
Then you could emulate the inputs with 3 buttons.
No make a g-code file which make some G1 movements with known feedrate.
Make direction changes in the g-code, e.g. with G1 which moves left and right and left and right etc.
Then try to control the THC up/down with the assigned hotkeys.
You will notice that the Z down will be blocked when the feedrate drops on the direction changes.

Have a nice day!

[beefy]

I tried everything mentioned and nothing worked (i.e. in Demo mode).

Anti-dive LED did not come on when feedrate went below anti-dive threshold %. Had XY acceleration values set very low so you can actually see the controlled point speeding up and slowing down.

Trigger inputs (arc Ok, THC up, THC down) all set up and activated associated LEDs, but do not change Z dro during simulated (demo mode) cutting.

I'm guessing you will have to try a real world test instead of demo. You would not have to do actual cutting as you cut artificially give an Arc OK input via a switch.

[stivemaster]

Hello, very strange Mr. Balazs! You don't have time to make a video, you don't even have time to take a screenshot of the forum here, you don't have time to update your installation instructions.
In all the topics I found in your forum (about 25 !!!) also no one had time to do this. What's worse is that after reading them one is left with the impression that such a feature does not exist at all or at least not works as you claim.
I think you should know that if you have achieved something after purposeful work and do not document it, do not describe and demonstrate it - it is as if it does not exist! And you make your work meaningless yourself, which is really unfortunate.
In addition, I think that this is one of the most valuable features of UCCNC-Plasma and if it really works - I ASK SOMEONE HAVING TIME to describe the setting with which it is started. Please also add details from which version of the program , this feature starts working as well as whether there are any differences if run in demo mode, etc.

Have a nice day !

[beefy]

Stivemaster,

just like in the past, I tried to help you.

But just like always you end up complaining. Did you say a simple word of thanks, no. Have you tried a real life test like I suggested and come back with results, no.

The first thing you do is bitch and moan AGAIN. You've done it on the Sheetcam forum and you've done it here more than once.

Why don't you just move to Linuxcnc as a member has suggested to you in the past. You are free to learn as much as you want with that system, and get as deep as you want into the coding, and make it do exactly as you please. Then if something doesn't work you can blame yourself.

With UCCNC the demo version does not have an actual controller working with it. As a result it seems that sometimes demo mode does not do what we expect and you have to do a "real life" test with a motion controller connected and set up. I thought with your amazing capabilities designing your own super PID THC, that would be easy for you, but unfortunately you seem to moan a lot quicker than test and try.

[stivemaster]

Sir, I'm not honored to know you, but you're obviously not very polite.
I want to draw your attention to the fact that I especially care not to be rude!
Besides, I want to pay attention to one more thing - I don't know about you, but I don't write in this forum for fun, but for work!
And when it comes to work and business relationships, I don't know what role posts like yours play.
Since it obviously matters whether the program is in demo mode, shouldn't that have been written? I asked explicitly for that!

Once again please behave correctly! You can make your unpleasant remarks only if what we are talking about is described in the instructions and I did not follow it, then I ask a question here!
And to the people who allow you such posts - let them think about what the signal is for future customers - buy our controllers but if you can't run them because of something we haven't described and write in our forum, we will send someone to scold you for to stop writing?!?

[cncdrive]

Stivemaster,
We trying to do our best to make everything documented, but it is very hard because the software has lots of features.
Making videos of all features would require ages. We think that it is more important to develop the software than to make videos.
With this I'm not saying that videos are useless just that I see coding features more important than doing videos and also I'm much better in coding than videoing.
Fortunately users are clever in figuring things out.
And honestly speaking I have no idea how to better describe you how this feature works and how to use it than how I already did.

Beefy, Yes, it's possible that the feature does not work in demo mode, honestly I do not remember if it was implemented in demo mode, I thought it was, but it seems it was not if it does not work for you. This feature was developed and implemented years ago and my memory is limited, so I thought it works in demo mode too.
But it is 100% sure that it works in non demo mode, we have tested it on our plasma cutter at that time.

[stivemaster]

Hi Balazs, well then, I will wait for the controller I ordered. I want to configure it here on the workstation in the office, not to stop a working machine on a client to try.
Just to clarify something by uploading a screenshot - since I do not use your codes from M205 to M212, but only M10.1 and M11.1 for our controller I want to ask again - should some of these cells be checked?

[beefy]

Beefy, Yes, it's possible that the feature does not work in demo mode, honestly I do not remember if it was implemented in demo mode, I thought it was, but it seems it was not if it does not work for you. This feature was developed and implemented years ago and my memory is limited, so I thought it works in demo mode too.
But it is 100% sure that it works in non demo mode, we have tested it on our plasma cutter at that time.

Hi Balazs,

I've got no doubt it WILL work in non demo mode. Come to think of it I'm pretty sure I had the anti-dive output going to my Neuron THC before I designed and installed my own THC, and I'd tested the anti-dive output. But that was some time ago.
Because I've noticed in the past some things don't work the same in demo mode, I thought I'd try and help Stivemaster (won't be making that mistake again) and test about what he was talking about in demo mode.
So I tested then gave him the advice to try in non-demo mode.
To be honest it would be a huge accomplishment if everything worked exactly in demo mode as it did in non-demo mode, considering there is no motion controller attached.
I don't expect everything to be perfect, and some things simply have to be tested in non-demo with everything hooked up. I still remember the early days of testing UCCNC when I had my $10 logic analyser hooked up to a UC400ETH, and had a microcontroller injecting signals for checking all sorts of timing

[cncdrive]

Stivemaster,

Enable THC control checkbox enables the THC signals to control the Z axis. Checking this checkbox is the same as if you turing the THC on with the THC on button on the THC screenset main screen. If the THC control is enabled only then will the THC up/down signals control the Z axis.

Control THC even if not in THC mode if checked then the controller will not wait for the ArcOK input signal, it will control the Z axis anyways.
Usually this is better if not checked, because then the controller will not wait for the plasma arc to build up, but will start the movements.
It should be checked if there is no arcOK output from the plasma or THC controller, then there is no other choice then to tick this checkbox.

Enable THC anti dive, this checkbox should be checked to enable the anti dive feature, the feature which this topic is about, if it is not checked then the antidive feature is turned off.

Beefy,

Yes, I remember that you tested the antidive output, that you posted about it that it was needed for your THC controller, but it was a long time ago, so I don't remember the exact details.

[stivemaster]

Hi Balazs, I got my controller and I can now simulate the operation of a machine here on the workstation in the office. I made some files with Sheetzam and released them, but I notice the following problems:
First - Anti diving does not work at all values ​​less than 100%. So far I think I made it work at 100%.
The other is more embarrassing - immediately after a move on X where he works, he stops working on Y. What could be the reason for this?
I tried of course with different speeds and accelerations in the axis settings, as well as with the G code in the files. The same thing is repeated - works on X and does not work on Y. Only on a file on which the contour is Spline, it works in all directions, but there always moves the two axes together.
One more thing - for me it is strange why, since it is clear that a small element follows and the machine cannot accelerate to its end, Anti-diving turns on - that is, the small arcs in the corners?
At the end of the line, it switches off when it slows down. Then it switches on for a moment at the beginning of the small arc and at the end and switches off again. In my opinion, the road planner should keep it off until he really accelerates to the next straight line, not when trying to accelerate on the small element.

Have a nice day !