Advanced Search

Constantly forcing index-enable low would explain the issue with G33.1 in the post above:
forum.linuxcnc.org/10-advanced-configura...sues?start=20#282461

Have you tried using spindle synchronized motion (eg g33 or g33.1)?

So I modified the orient.comp such that it has an index enable cmd pin (i/o).

This allows it to start the orientation with indexing, once done, it will disable the automatic indexing.

It can still be activate again by setting the index enable cmd pin high again (eg. via custom M code).

Only software signals can enable the automatic indexing before spindle orient.

In hal i then use:setting this high manually (or via logic: for example put this high after an M3 command has been issued), it will make the system home once and do a spindle orient.



Cheers, 
David

Hi everyone,

Since I haven't made much progress with the inverters and electrical hardware (i try to get the SIEMENS S120 running but its hard with linuxCNC ;( ),

I've been working on a concept for the hand-control-panel in the meantime. I dont like the original one that much, so I'm trying to build a new one and keep it as compact as possible.

I like the idea of it being mounted to the bed carriage, similar to a conventional maschines. I plan to design the lever for forward/reverse operation in a way similar to what was done with VDF. In the neutral position, it will lock in place, and to activate it, you’ll need to push it slightly towards the negative Z direction first. Then, you can move it up for left rotation or down for right rotation. All three positions will have a locking mechanism in the center, as mentioned. This is for safety and prevents unintentional movement when you have your head near the spindle and might get caught on something like your clothing.

For the keys I'm thinking about adding a Stream Deck instead of real switches. So i can programm different functions to the setup in the future. Could be very handy.
   

Best regards,
Tom

Hi all,

Today i did a test using the clothoid algo.

It turns out, when doing a fast clothoid fit, (using deviation as trim dist) this takes around 0.5ms.
Everything is going well.

When using the excact clothoid fit method, it takes time up to ~200ms when it has difficulties to find a fit.
I will find a solution for this later on.

Most off time the clohtoid fits are ok. I have seen cases where the clothoid fit result looks like overfitting.
This could be investegated later on.

Here some 3d clothoid fit examples. Using look ahead = using endvel.
So far i am happy with the results.

 
 
 

Github is updated.

Was kann ich von der alten Konfiguration weiter verwenden, was muss ich anpassen und was muss neu erstellt werden?

Um zurück zur Frage zu kommen würde ich wie schon erwähnt mal probeweise die neue Version auf eine zweite festplatte installieren und deine jetzige Konfiguration mal laden dann kann man auch gleich auf konkrete Fehlermeldungen eingehen.

@scda

The only thing I changed is: uncomment "is_oriented = 0" (otherwise I was not able to run multiple M19 commands in a row).

After digging out my config from back then I notice that I made the same change.

Yes that's the issue with the M19 command. But could probably be changed in a new release ??

thanks for confirming that as I thought I was missing something and yes that could indeed be changed.

What makes me wonder is why  constantly forcing index-enable low does not cause a problem for you.

@andy, seems I have missed your reply:

The point of IO pins is to only write any state to them when you want to set the state, and let other parts of the net be in charge at other times.

Looking at your code for case 0, which is the initial state, you are setting 'index_enable = 0' so this version of the component permanently forces 'orient.index_enable' low until an orient command is issued (ie 'orient.enable' goes true):

 Your code looks like it will always set index_enable true?

No, my version forces homing to index because the mechanism with adding 16 to the p word does not work and 'orient.index-enable' is not written to unless spindle orientation has been called (ie 'orient.enable' is true) because 'index_enable=0' is now inside the if (enable) { statement.

Yes, I'm currently not home, so I dont know the specific name; but I tried the qtvcp_demo0 or something similar and it worked without problems.

Does one of the QtVCP sim screens (QtDragon) load in linuxcnc?

Chris

I have a mixin class that reimplements the paint event. It first paints the normal widget then adds indicator painting.

github.com/LinuxCNC/linuxcnc/blob/master...ts/indicatorMixIn.py

I confirm and see the problem. I'll try to push the fix soon.

*halui_data->so_counts = 0;

should be:

*halui_data->so_counts[spindle] = 0;

Chris,

How are you adding the indicator lights to the upper right corner of the push buttons in QtDragon?



Thanks
JT

I don't know anything about remora sorry.

JT

Yes that's the issue with the M19 command. But could probably be changed in a new release ??
I connect the orient.mode signal to a signal and then manually switch the mode.
An improvement might be to use a custom M command to change the mode (via mux2 or multiselect component)

One thing I might try is to change the orient.comp to have a input for running the index function, that can be controlled easily via hal or M command.

About the brake control:
I found the spindle.xx.locked pin in the documentation which goes high when orient ist done (and low with M5 or a new M19 command) --> it is perfect for controlling the spindle brake !

Oh great so i probably have no issue at all!
My drives only take 32-bit Integer inputs so that is fine.

Thank you!

since the core questions are answered:
I am building an air bearing Diamon Turning Lathe. The goal is to do single point diamond turning of telescope mirrors or similar.
Using ironless linear motors and high resolution glass scales. It is going to get calibrated with an Interferometer so i should get down to 100nm or so of straightness of the axes and linearity of the glass scales.

There will be watercooling of all relevant components down to about 100 millikelvin precision.
I am using Triamec servo drives.

The progress will be documented on my Instagram (Instagram.com/leo.wolf.the.engineer). Please follow if you are interested!