Advanced Search

Hi,

Here we go. They worked perfectly before for me. I could screw cut at 1200 rpm easily.
Any help is appreciated. Just need to know what pin to what pin. I currently have BOB +5v to LM393 vcc. BOB gnd to LM393 gnd. and D0 to pin 10. Lights come on, lights blink when slots are recognisded, but nothing in Linuxcnc, both halscope and hal port test

exactly i compiled over linux mint 22 with kernel 6.10.2-rt14 .... rip install using master branch, configure --with-realtime=uspace --enable-non-distributable=yes ..... and all work perfect. During make process I see clarely that "make" check with success python3.12 .... and at end all work well.

First to configure I check debian dependancy, install a long list of library ... (debhelper (>= 12) dh-python docbook-xsl asciidoc imagemagick asciidoc-dblatex intltool libgpiod-dev libxmu-dev netpbm po4a xvfb dblatex (>= 0.2.12) dvipng fonts-dejavu graphviz groff inkscape source-highlight texlive-extra-utils texlive-font-utils texlive-fonts-recommended texlive-lang-cyrillic texlive-lang-european texlive-lang-french texlive-lang-german texlive-lang-polish texlive-lang-spanish texlive-latex-recommended w3c-linkchecker xsltproc texlive-xetex). The only problem was libjpeg8-dev conflict version .... so I leave out from my system. Not needed. After can Install.

Just try latency-histogram --nobase -sbinsize 1000 with 6 glxgear and 4 youtube video dance music + ethercat line active over etherlab 1.6 ..... after 6hout sdev(us) was 2.8 and min/max from -66 to 78 .... quite good for servo. Now need to manage bios and add some condition on grub .... think latency become a little bit better than now.

Now only doubt is how to install a rip-version of linuxcnc-ethercat ..... never done. ....   I try.

Thanks to all for effort.
regards

Pictures of the LM393 board?

Nope, not me, i am not sure i have access to that part of the server.

Hi all. Thanks for all the advice given over the many years. I have scrapped my recently purchased 1000ppr encoder (some good advice given here) and gone back to my old DIY 60 slot disc. It worked perfectly for screw cutting before. BUT!!!! I have lost my wiring diagram and serious need help. Its a 60 slot disc with a LM393 opto sensor. This was working perfectly before but I cannot remember how I wired it. (good example of why documentation and drawings are IMPORTANT). So, I have the Chinese BOB and the pins are 10 for index, 11 for A and 12 for B. The LM393's are powered via the 5V and GND from the board. Then A0 from the LM393 to the pin. But......it needs something to the input pin ground and I cannot remember how I got this working before. I am almost complete with this lathe and this is the last step. Any help is much appreciated

Seems that 'carousel.comp' has not changed from 2.9.2 to 2.9.3:
github.com/LinuxCNC/linuxcnc/compare/v2.9.2...v2.9.3

I _think_ it's normal for 'iocontrol.0.tool-changed' to stay true.
Question: Does 'iocontrol.0.tool-change' go false?

issue has been identified, i believe, within FlexGUI, and an issue generated on that Git.

part of my problem was i was running incompatible operations. i was using MDI buttons to simulate auto operations. so i instead hand-wrote a crude Gcode program that selected a tool, started the spindle, did some moves with it. selected another tool, did some moves with that. and again, selected a third tool, and did some more moves. then stopped the spindle and ended program.
in case anybody is interested in how crude the code was: github.com/travis-farmer/linuxcnc/blob/m...r/gcode/atc-test.ngc i don't suggest running it, unless you have the clearance to do so...

what i found, is that both Axis and FlexGUI ran the program flawlessly... that is to say it did exactly as coded, but not exactly as i wanted...
there was no hang of the GUI, so my theory that it has to do with the python c.wait_complete() hanging the code, is probably correct. but will it interfere with my normal operations? not if i do them as intended.

the real issue being that my routine took longer than the c.wait_complete() timout, and the GUI aborted the routine.

so long story longer, i made my recomendations to JT in the Git issue, based on my suspicions, research, and new tests.

Whomever fixed it, Thank you very much! Tom?

  Is this the way my postgui Hal should look like? 

On the probing page,  the parameter boxes,  there is a new feed entry for traverse feedrate, make sure all of those have been entered and updated using the update probe parameters button

 

Lcvette wrote:

Add and update the probing parameter entries
 

Forgive my ignorance, but what exactly are you referring to?

Looking through some more pins , for that first tool change where it works through m code , iocontrol.0.tool-change triggers , it goes to the desired tool then iocontrol.0.tool-changed triggers and stays triggered , then I am no longer able to do any m6 tool changes

If I unlink this pin and manually clear it I am able to do another tool change , then manually set and clear I can do another and so on.

It seems to be that the iocontrol.0.tool-changed is no longer clearing itself.

Add and update the probing parameter entries

Lcvette wrote:

Remove the comment # for

HALUI = halui

In the ini
 

Thank you very much, that worked.

Now I have another problem that I didn't have before.... when I use the probe routine, and touch the 3D probe on the material, it stops and says error:
"Can't do g1
 with zero forward speed"

Yes , I also forgot I have this in gmoccapy_postgui.hal.

 

looking in halshow everything related to carousel seems to be functioning fine using my tool change jog buttons, its as if ive lost communication between gmoccapy and carousel , but only after the forst tool selection.