Advanced Search

To get the Logitech Dual Action F310 controller to work as a Pendant for the Scorbot-ER-3 using LinuxCNC 2.9.2, after making previous changes mentioned earlier in this forum, do the following:

Open the "scorbot-er-3.hal" file in the /linuxcnc/configs/by_machine.scorbot-er-3/ folder and add these 2 lines (after the "loadrt differential" line);
loadusr -W hal_input -KRAL Logitech
loadrt mux16 names=jogspeed

then add (after the "addf differential.0 servo-thread" line):
addf jogspeed servo-thread

save and close the file.

next open the pyvcp.hal file and add the following (at the bottom):

#******************************
# connect miscellaneous signals
#******************************

# ---HALUI signals---

net axis-select-x halui.axis.x.select
net jog-x-pos halui.axis.x.plus
net jog-x-neg halui.axis.x.minus
net jog-x-analog halui.axis.x.analog
net x-is-homed halui.joint.0.is-homed
net axis-select-y halui.axis.y.select
net jog-y-pos halui.axis.y.plus
net jog-y-neg halui.axis.y.minus
net jog-y-analog halui.axis.y.analog
net y-is-homed halui.joint.1.is-homed
net axis-select-z halui.axis.z.select
net jog-z-pos halui.axis.z.plus
net jog-z-neg halui.axis.z.minus
net jog-z-analog halui.axis.z.analog
net z-is-homed halui.joint.2.is-homed
net axis-select-a halui.axis.a.select
net jog-a-pos halui.axis.a.plus
net jog-a-neg halui.axis.a.minus
net jog-a-analog halui.axis.a.analog
net a-is-homed halui.joint.3.is-homed
net axis-select-b halui.axis.b.select
net jog-b-pos halui.axis.b.plus
net jog-b-neg halui.axis.b.minus
net jog-b-analog halui.axis.b.analog
net b-is-homed halui.joint.4.is-homed
net jog-selected-pos halui.axis.selected.plus
net jog-selected-neg halui.axis.selected.minus
net spindle-manual-cw halui.spindle.0.forward
net spindle-manual-ccw halui.spindle.0.reverse
net spindle-manual-stop halui.spindle.0.stop
net machine-is-on halui.machine.is-on
net jog-speed halui.axis.jog-speed
net MDI-mode halui.mode.is-mdi


# ---USB device jog button signals---

# connect selectable mpg jog speeds
net jog-speed-a => jogspeed.sel0
net jog-speed-b => jogspeed.sel1
net jog-speed <= jogspeed.out-f
setp jogspeed.in00 150.000000
setp jogspeed.in01 300.000000
setp jogspeed.in02 600.000000
setp jogspeed.in03 1200.000000
net jog-speed-a <= input.0.btn-base
net jog-speed-b <= input.0.btn-base2
net jog-x-pos input.0.abs-hat0x-is-pos
net jog-x-neg input.0.abs-hat0x-is-neg
net jog-y-pos input.0.abs-hat0y-is-neg
net jog-y-neg input.0.abs-hat0y-is-pos
net jog-z-pos input.0.abs-rz-is-neg
net jog-z-neg input.0.abs-rz-is-pos
net jog-a-pos input.0.abs-y-is-neg
net jog-a-neg input.0.abs-y-is-pos
net jog-b-pos input.0.abs-x-is-pos
net jog-b-neg input.0.abs-x-is-neg
net Pgm-run <= halui.program.run <= input.0.btn-thumb
net Pgm-stop <= halui.program.stop <= input.0.btn-thumb2
net Pgm-pause <= halui.program.pause <= input.0.btn-top
net Pgm-resume <= halui.program.resume <= input.0.btn-trigger
net Pgm-step <= halui.program.step <= input.0.btn-base4
net Estop-activate <= halui.estop.activate <= input.0.btn-base3

save the file.

Special note: The Pendant will not work until you home the Scorbot-ER-3. After Homing the coordinates will change to cartesian coordinates (X,Y,Z,A,. After you make these changes the pendant will work as follows:

The left joy stick controls X, and Y axis.
The right joy stick controls the Z axis.
The D-Pad controls the rotation and turning of the gripper A, and B axis.
The bottom finger triggers control the rate of movement;
nothing 150
left only 300
right only 600
both 1200

Last is the buttons:
Button 9 is estop, if pressed you have to use the keyboard to reset
Button 2 is run G-Code
Button 4 is pause program, press Button 1 to Resume
Button 3 Stop program if if press Button 2 it goes back to beginning and starts
over again
Button 10 you must first press Button 4 this will run the code one line at a time
Button 1 Resume (after Button 4, or Button 10)

I have not yet figured out how to open and close the gripper through the G-Code file or the Logitech F310 Pendant. Only the GUI interface (+ -) works for the gripper.
I hope someone smarter then me can help to figure this out, and add a replay.
Thank You all

I've been automating a small Mill.
I keep running into problems and people here have helped - thank you.
Mesa 7i95t et al.
I've got to the point where I can click the home icons on my Gmoccapy screen and it homes all three axes.
Then I move the head onto the middle of the bed with the on screen jog buttons and load a piece of program
that is basically just a set to G54 mode and do a G0 X20 rapid flip 20mm positive on the model hence the bed should move left.
Once I have that it's just relearning g code time.
But nothing happens.
I add a growing number of lines to set things up.
Still nothing. It gets to that line, highlights it and just sits there probably waiting for something or feeding at 0 so it will never end.
I've spent most of the day trying new ideas.
This is where I've got to. What do I try next? What do I take out? What obvious thing have I missed?
What do I have to do to make it move?
Is it my code? My configuration? Is it offended at my accent? Does it just hate me? (it feels a bit like that)

G1 changed back to G0, I was trying G1 as a test and it didn't help

So, es läuft jetzt, vielen Dank Aciera, ist genauso wie ich es haben wollte, alle 2 min einen Intervall ohne viel drumherum.

Die Verknüpfungen haben mir das Leben noch etwas schwer gemacht, den interval.enable habe ich mit machine-is-enabled verknüpft, ging problemlos.

Beim interval.out kam immer der Fehler, dass der Pin nicht vorhanden ist, letztendlich habe ich Hilfe von Sven die Verknüpfungen in die Postgui_call_list geschrieben, damit ging das dann auch.

In LinuxCNC 2.8x läuft das ganze wenn man in der Interval.py aus python3 python macht.


Grüsse
Steffen


 

Yeah, that's what I though, the direction signal going to 0 at every step is dubious at best. Especially looking at your older posts which clearly show a logic analyser graph with the expected step dir behavior.

I made a short video so we can all better understand what's happening, would you mind taking a look ?

(Keep in mind, these are differential signal, the dir pulse is not going in the other direction between step pulse, it's just going to the mid point, 0v)

Thanks, that works perfectly!

Yes it seems I have mistakenly used qtpy instead of PyQt6, and so needs qtpy installed. I'll align with flexgui on QT6.

Are you sure the blue trace is the Dir pin. It should only change from high to low on a direction change. I doubt you are changing direction every step pulse.

The LinuxCNC component does not control the setup and hold times. This is done in the firmware.

hi
will this version from your repository control an real machine with ethercat servos?
it already works with linuxcnc 2.9.3, its a cutting machine with XYA axis, A is tangential to the path. today it has very jerky moves as linuxcnc doesnt blend rotary axis. i would like to test the blend features you developed. in the previous videos there was an tool direction that i could use to control the tangencial axis, is this avaliable in this version?

Strange enough is the value of #5070 probe fail/succeed passes each time with a one(1) succeed.

#5070 returns '1' if the probe succeeds which seems to be case. Looking at the 3 screenshots indicates that the actual probing works fine as the resulting 'calculated offset' values are very close.

Seems to me that the problem is somewhere after the actual probing has taken place.

[edit]
I wonder from where in the code this comes from:
'Return to original tool-tip position using new z-offset: ...'

Looking at the oscilloscope I found out that my timing is wrong.
There isn't any Dir Hold or Dir Setup in my signal as is required by my drivers.
(Yellow: Step pin  Blue: Dir pin)

Following Scott's post I edited and uploaded my config.txt
Unfortunately, looking at the scope, there still isn't any Dir Hold or Dir Setup in my signal !


I made sure my config was updating properly by changing the timing and looking at the scope, which it does.
I made sure the dir signal was wired correctly to the scope by moving the axis back and forth, which it is.
I reinstalled remora ethernet component by downloading the repo and doing sudo halcompile --install remora-eth-3.0.c inside Remora-RT1052-cpp-main/LinuxCNC/components/Remora-eth/

Is there a bug, did I overlook something ?

The limit will likely be the rate at which steps can be generated by the parallel port

If you set the stepgen velocity with RPM and you have 800 steps/turn the step scale should
be 800/60 = 13.3333.  With a 55 usec base period and 800 steps per turn, this limits you to 1350 RPM

You can run this command to set the CPU governor to performance (max clock speed always):

`echo performance | sudo tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor > /dev/null`

NOTE: The governor resets after each reboot.

Open your PC and unplug/remove everything you can; removing unnecessary hardware can help quite a bit.

Blacklist kernel modules of unneeded hardware.
(physically remove as much hardware as you can first)

Find currently loaded modules with `lsmod`
List connected devices with `lspci -v`
Blacklist modules by adding a file to the folder /etc/modprobe.d that is named [module-to-blacklist].conf that contains the text "blacklist [module-to-blacklist]"

BLACKLISTING KERNEL MODULES CAN BREAK YOUR SYSTEM; BE CAUTIOUS

wiki.debian.org/KernelModuleBlacklisting

I tried to install "linuxcnc-uspace" and I got dependency errors.
The "linuxcnc" package has no installation candidate on both Ubuntu and Debian (even the version of Debian supplied with the LinuxCNC ISO).

The offical ISO image does work, however.

I have no clue of how generate G-Code.
I have never used a cnc machine before.
I'll worry about that once the machine works.

I also need to buy a ton of grease nipples for the linear rail bearings because many of the existing ones are clogged and broken.
Somehow, they are impossible to unclog.
(No clue)

You can put the .deb files on a flash drive and install them as you usually would with `sudo dpkg -i <all .deb files go here>`

For example:

1.) Download all the .debs from this sticky:

forum.linuxcnc.org/9-installing-linuxcnc...ng-rtai-debs-for-2-9 (the 5.4.279 ones)

2.) Put them on a flash drive on one machine that has access to the internet (any machine, doesn't need LinuxCNC)

3.) On the LinuxCNC machine, run:

4.) Now plug the flash drive into your LinuxCNC machine that doesn't have internet access

5.) Make a directory in your home folder (/home/<your user>) called RTAI on the LinuxCNC machine

6.) Use the graphical file manager to copy the files off the flash drive into your newly created RTAI folder

7.) In a terminal, go to that directory:

8.) Run:

9.) Reboot and select the RTAI kernel via the GRUB menu (this is the menu that has a list of kernels you can choose from at boot. It launches right after the BIOS is done.)

10.) Run the latency test or latency histogram.

I think I'm using Axis as my GUI.
I am using LinuxCNC version 2.9.3.

BTW, right now, the system does not actually work.
I am just testing it.
The old stepper drivers broke (I think).

I am still waiting fir the new one to arrvie from China from Ebay.