Advanced Search

You mean you cannot enter MDI commands in that entry? (sorry the image is from an older gmoccapy version) 

die fehlermeldung sagt dir doch genau was los ist... dir fehlen diese 2 ordner in deinem config ordner.... erstelle diese und fertig

yes.

Amateur hobbyist on a 3-axis mill with RPi4 B in a single person shop.

I have just got LC 2.9.1 Gmoccapy working after using AXIS for a couple of years with just mouse and keyboard (on LC 2.8.4).
My interest is to regain MDI queuing and Run-from-Here that were lost in AXIS 2.9.1.

But, on my current system, when on-screen jogging is enabled by selecting "Keyboard Shortcuts" on the Systems Page, I cannot enter MDI commands from the keyboard.

Is it possible to setup Gmoccapy to allow both on-screen jogging and keyboard entry ?

John.

now we have modifier's for all pin's:seems more complicated at first glance, but is much more flexible

 

I have Synaptic Package Manager installed. Looking forward to those files. Thanks for the help.

I just went through this a few days ago with my Pi 5.

I left a post on another thread about consider adding the RaspberryPi.com and Raspian.org entries to the appropriate lists so that the APT infrastructure works out of the box with the prebuilt Debian distributions from LinuxCNC.

I wasn't taking notes so I might have missed a step but you definitely need to add entries to the /etc/apt/sources.list and drop PGP signature files into /usr/share/keyrings.

I updated the files on my Pi but it will be tomorrow until I can get to it on the net. I'll try to upload those files and you can just drop them in. Then I would immediately install either gdebi or synaptic which are both great package managers.

Hi everyone.
Ưhile working with linuxcnc ethercat, I have some questions, hope to receive advice or comments from everyone.

1. Normally, we often use limit switches to determine "home position". 

2. My idea is to use the servo motor position in "absolute mode" as "home position". That means, for example, in the xyz robot, I mark a fixed point on each axis, then move the axes to that point (this point will be the "home position"). Next, I read the absolute encoder values ​​from the ethercat servo command on the 3 axes, and get the value of "home position". So how can I implement the above idea?
Thank you very much.

Please feel free to correct me if I have gotten anything wrong here. This post is for future me, and whomever else may benefit from it. I will likely edit this if there are corrections.

I put together a circuit on a breadboard, for testing. I still have to set this all up in LinuxCNC, but at least I have a physical thing to work with. The white wire is GND, orange is switch position 1, blue 2, green 3, & red 4. I will use this for selecting axes: Off, X, Y, Z, and a similar thing on another switch to select x1, x0.1, x0.01, x0.001, although microns are probably a pipe dream on this machine.

Orange (1) has no conductivity to bit 0 or bit 1; 0:0
Blue (2) has conductivity to bit 0 and bit 1; 1:1
Green (3) has no conductivity to bit 0, but does to bit 1; 0:1
Red (4) has conductivity to bit 0, but not bit 1; 1:0

Now I have to figure out Mux8 for a mode switch. That's eight inputs for three rotary switches, so that leaves eight inputs left on P2, of which two are going to an MPG. Plus all of the P1 inputs.

The thing that updates every millisecond is CommandedPosition, linuxcnc calculates a new position value every millisecond which goes to the MCU on the card. How many steps does the step generator need to make to go to that new position?
There is the scaling parameter 320 steps/mm. Say it needs to go 0.1 mm in one millisecond which is awfully fast but just an example. 0.1 *320 = 32 steps to make during that millisecond.
Another way could be to calculate number of steps to move in hal, in linuxcnc. It is not done that way. The new position, commanded positition, in machine units, is fed to the stepper driver, be it Ethercat, parallel port or Mesa card.
If you change the microstep setting on the driver itself you need to change stepspermm accordingly.

 

Hi,

Firstly just want to state, Probe-Basic looks fantastic. Credit to you guys. Way over my head, but looking forwards to getting is working.

I am slowly going through the process of building up a CNC from a mill and started my journey on Gmoccapy. I have MESA 7i96S, 7i85S and a 7i73. It took me quite a while to get it configured to run and now making progress, however, I feel Probe-Basic is on the charge and wanted to shift across to this.

I will be using xyz at this point. Have installed Debian from the Linux install iso.

My question as a newby, is what is the best approach to move across and make sure that the config that I have been able to develop is retained at east in a way that can be realistically used to help configure Probe Basic. I am happy to blow away the environment and recommence, just don't want to loos e something that can help resolve a future problem from a current working solution. What is the best approach to this.

NOTE: I did try to just process through he install, but errors occurred in the get apt code so I stopped there. I think it may be to do with root security.

I still don't understand, what do I use the lcec.0.D1.stepspermm pins for?

Do you have
home_sequence = -2
for both Y joints set in the ini file?
Or -1 or -3....

I'm not sure how MesaCT determines card resources.

Is this PWM setup for interfacing with PWM motor drives
and using encoder feedback?

If so, a 7I97T configuration would be close
(with perhaps some PWM frequency/mode changes)
 

I'm running the LinuxCNC OS provided on the LinuxCNC Downloads page:  Downloads

• LinuxCNC 2.9.2  Raspberry Pi 5 OS based on Debian Bookworm  Raspberry Pi 5 Uspace compatible with Mesa Ethernet boards. Note that SPI is not currently supported with the Pi5.

I used rpi-imager to burn the OS onto the micro SD card for my Raspberry Pi 5.  So far the OS is working fine.  I just can't get probe basic to install.