[PlanetCNC]

Open transformation dialog (menu Program/Transformation). Enter values. Right click to open context menu and choose "Set As Default".
I will fix settings issue.

[JerryBurks]

Thanks, that works.
Looking good so far!!

[theRat]

The installer doesn't give you the option to choose a different install directory, so it always overwrites the TNGv1 install. Could you either change the directory for the TNGv2 install or at least allow the user to select a different location in the installer. Without this it is not easy to have the two version coexist on the same machine.

Cheers
Simon

[PlanetCNC]

I was sure I did it this way. Seems reasonable. I'll check what went wrong with installation script.

You can also simply rename your TNG installation folder or copy it somewhere else. TNG does not care where it is installed.

[theRat]

I just did a little more testing. If you don't have TNGv1 installed it asks you where to install it, but if you do have TNGv1 installed it doesn't and just uses the directory where TNGv1 was installed and overwrites it.
It is probably because the 2 installers have the same application id so it thinks TNGv2 is just an upgrade and should overwrite what is already installed. Might be best to turn TNGv2 into a new application since as you say a lot of compatibility problems if it goes into the same directory as TNGv1.

[PlanetCNC]

Yes, just figured this out myself. Will fix this.

[JerryBurks]

Questions about the rotary speed calculation with an a-axis indexer....
- Does the speed calculation for all axes use the angle*radius distance for the rotary movement?
- Or does it just use the angle number as mm/sec or in/sec ?
- Or should I better use the G93 inverse time?

Thanks!

P.S.: I think the TNG V2 is a major achievement. Congratulations!

[PlanetCNC]

With rotary axes, when synchronized motion of multiple axes is needed, it is best to use G93.

P.S.: I think the TNG V2 is a major achievement. Congratulations!

Thank you, this is very nice to hear.

[mar_cone]

Hi,
I tried to configure the buttons for custom commands in the toolbars with the procedure explained in the blog but I can only enter the commands in the machine menu but not the custom buttons; In V1 it worked ... has the configuration changed?
PS: no news for how to configure the additional inputs of the ExtIn card?

[PlanetCNC]

TNGv2 buttons file have changed. They have much more options.
ExtIn is still on TODO list.

Until we create new tutorial for buttons I attached one of my test files which may be used as an example.

[mar_cone]

Ok, I'll try to figure it out
Thanks

[mar_cone]

Hi,
Has anyone here found any problems in finding the offset Z with the moving probe? The Z 0.000 is completely wrong for me. It appears that the script does not reset the Z when the tool touches the probe.

[PlanetCNC]

Settings for "Machine/Work Position/Measure Height" command which is used with moving probe are in "Settings/Measure/Offset" section.

Hint:
Is you press CTRL+ALT when you click "Machine/Work Position/Measure Height" you will see script that is behind this command. See screenshot.
(This CTRL+ALT trick can be used with all commands that use scripts)

[mar_cone]

Thanks for the quick response,
Yes, I knew that with that sequence of keys you could see the scripts and mine is the same as yours but as you can see from the short video I published it doesn't work properly;

I attach my settings to the probes

Attachment 430548

[PlanetCNC]

You probably have tool offset set.

[mar_cone]

I don't think I have set the offset ... the check is not active. I enclose the table of the tool used for the video, but the problem is the comparison with any imposed tool.
Attachment 430550
Attachment 430552
I don't know what to check :-(

[PlanetCNC]

Machine/Tool Offset/To ..
will show you current tool offset.

Machine/Coordinate System/To ..
will show you current coordinate system offset.

or you can monitor parameters _tooloff_z and _coordsys_z.

To ignore these offsets you can change script line G92.1 line to:
#<off> = #<_probe_z>
o<chk> if[#<_tooloff> NE 0]
#<off> = [#<off> - #<_tooloff_z>]
o<chk> endif
#<off> = [#<off> - #<_coordsys_z>]
G92.1 Z[#<off> - #<_workoff_size>]

I will make this modification in future release.

[mar_cone]

I discovered the problem! I solved.
I don't know why in the Coordinate System in use a value equal to the error of the reading on the probe was set in Z. I reset that value and it's all right.
I'm sorry for wasting your time
Thanks

[JerryBurks]

A few suggestions for the next version. Not a big deal but it would help:
- turn off spindle automatically when stopping in the middle of a program run. I know I can add M5 to the "stop" script in the settings but why keep the spindle running?
- freeze the jog potentiometer input when the jog starts or make it optional like in the old software. The jog becomes a bit rough when there is noise on the pot input.
- I don't find the pocket wizards anymore. I believe V1 still had them and they are quite convenient specifically to surface a work piece.

[PlanetCNC]

1. What about those who want to keep it running? Everybody has different needs that is why scripts are implemented. They allow you to customize behavior of software for your own needs.
2. Never had this issues and nobody ever reported this problem.
3. It is called "Generator" now. These scripts are in UserGen folder and they appear in menu File/Generate. I will make some examples.