Advanced Search

Sorry, my mistake. It is probe screen 2.9 from verser-git.

But I have similar problem like Marcodi:

So whenever you are inside of the probe screen and you use the keyboard numbers 2-8 4-6 and 3-9. The machine starts moving in the appropriate direction without stopping until it hits a limit switch

Same happens with my machine. And also when using page up and down with the z axis.

I don't fully understand the question, but I think that a material change would be handled by the touch-off process that is normally used to re-align the working coordinates to the workpiece.
This is typically achieved using one of the G10 code variants (G10 L1 / G10 L10 / G10 L2 / G10 L20)

Just to clarify, when you say "Probe screen v2" what are you referring to?

Is this: github.com/LinuxCNC/linuxcnc/tree/master...n-panels/versa-probe

Or some other probe screen?

I think you can leave multiple tools in one pocket in the table.
You call the Tool with a T-number in the G-code, then the system checks the tool table for the pocket, and puts that number on the pocket-number.

(This is useful for using two sides of a lathe tool, for example. You would get different tool-point offsets, but the tool0changer would use the same position for both sub-tools)

I _think_ that the tabs activate once you press "accept changes" at the bottom?

Is this the serial protocol, or the 4-bit gray code?

I think that _some_ Fanuc serial protocols are supported by Hostmot2:
linuxcnc.org/docs/stable/html/man/man9/h...html#Fanuc%20encoder

Yes thats ok
But i can not link joint.2.motor-pos-fb to cia402.2.pos-fb
Because it is already linked :net z-pos-cmd joint.2.motor-pos-cmd cia402.pos-cmd joint.2.motor-pos-fb

Axis and halshow means that move the axis but it dosnt move.

It looks like there is one target (with a magnet?)
Is the problem that the sensor is also detecting the bolt heads?

Can you describe the system in more detail, including what position feedback there is and how the system is driven?

Hi Bernhard,
verstehst du richtig so, RPI + Parallel Hat is das selbe wie PC mit Parport,
die step-signale werden im Raspberry erzeugt und an den GPIO pins ausgegeben.

Nachteil: Jitter und nicht allzu hohe beschleunigungen/geschwindigkeiten möglich.
Vorteil: günstiger

bei Mesa werden die schnellen stepper-impulse im FPGA erzeugt und der Raspbi gibt nur die befehle an die Mesa per Ethernet oder SPI und erhält den aktuellen status zurück

Gruß,
Olli

EDIT: für so ne diadrive reicht der RPI mit Hat völlig aus, die geben 'max. 20 mm/Sek.' an, dafür brauch man keinen FPGA
 

Okay I remember there was a section in the CNC panel for tools and hal stuff so I poked around there and found the specific call-out I need to address the 7i84. I'm starting to get excited as I was able to make something actually happen finally. I controlled an output on the 84 for "coolant" now I just need to add all of the lines for my machine and wire everything. I will likely return with more issues but I will probably make a new topic mostly for tracking my progress.

I have a new section in the error codes where it does say it can see the 7i84. So it must be my call-out for the pins are incorrect. I am referencing a project where the guy had his 84 wired to his 7i77 but I am using the 7i74 to communicate with the 7i84 and 7i73. Is the pin call-out different currently it is "HM2_5i25.0.7i84.0.2.output-10"

I decided I didn't like the looks of the Ethernet cable I was using so I went and grabbed 2 different ones to try. When I plugged it in a new yellow light turned on and when I launched the CNC page it blinked green a few times before giving me the same error pins on 7i84 don't exist.

I saw the question and you have now attached exactly the relevant files. Thanks, I'll be happy to think about it!

OK. Best of luck Rod.

No I didn't get a blinking green light, the 7i77 flickered a few times and went back to red.