Advanced Search

I added an attachment and a ring around the jog button I am talking about. So what you are saying is that I don't have to make a Hal pin connection from that jog button with a red ring, with a pin from the motion component, to make the jog button move a stepper motor?

In my mind I'm thinking something like 

• net x.axis.jog gmoccapy.jog.axis.jog-x-plus => hm2_[MESA](BOARD).0.stepgen.00.velocity-cmd
• net x.axis.jog gmoccapy.jog.axis.jog-x-plus => joint.0.motor-pos-cmd

I know this statement makes no sense, but it describes what I'm thinking. Shouldn't the jog button give an position or velocity command/output that describes where the axis should go, or cause the Mesa board to produce step pulses?

gmoccapy provides this button so the user can connect a signal (eg from an external button) for jogging.

Question 1+2) It was not obvious to me that the G-code interpreter communicates with the motion component, without connecting them via hal pins. But I think I now understand how the joint-pin from motion component get it's position or velocity command/output from;)


Question 3) How do you connect Gmoccapy jog button to linuxcnc motion component, to make a stepper motor move then?

What I don't understand is how a "gmoccapy.jog.axis.jog-x-plus (bit IN)", is an input pin. Shouldn't it be an output pin? Because you "press" a button, which then sends an output?

Lots of work to get it done correctly. Look at the challenge many people face just trying to install the debs.

About other error ... running  dpkg-checkbuilddeps command discover a list of unistalled libs (why if LMDE 6 have on package manager linuxcnc and linuxcnc-ethercat ???? .... mistery of life).

The package installer only installs the runtime dependencies.
Since you are _building_ LinuxCNC you need the build dependencies.

Thank you all for the suggestions!

@cornholio: I did try with both smb and nfs shares, and the problem of refreshing is the same. Changes made on the machine are relfected on the server and other computers on the network instantly, but the reverse isn't. Even the folder up buttons don't work in the GUI, both on the debian file explorer and the Probebasic file explorer. (i think it tries to go up a directory on the server, which it isn't allowed to do). Pressing F5 works in the debian file explorer. 

@mecanix: I have tried many modification to smb.conf, including the ones you suggest. Except, I never tried to have it set as a public folder like you do. I have rwe permissions on everyone except guests who don't have access. I was mounting the share using credentials. Again, I could see and upload files to it so i think permissions are working, It just wouldn't update automatically, just making the day to day workflow pretty tidious. Either a debian bug or lack of feature, or an issue with cache settings, or CIFS notification protocol.

The refreshing issue is identical on the second test device RPi5, running rpios. So I don't think it has anything to do with the linuxcnc real time kernel.

Eventually, I ended up doing an overkill set up, which is now avoiding the problem: I let the folder as an SMB share on the server (so i can access it from the multiple devices I use (the PC being the main one) and installed SYNCTHING in a docker container on the server as well as on the CNC computer. It does watch both folders for changes and updates them accordingly. It is making local copies on both devices, which not only allows the folders to be updated instantly and automatically in both the debian and Probe basic file explorers, but let's me load the gcode from the machine's storage and not through the network, which is a plus. Also, if one of the devices is offline, the changes are just queued and nothing hangs like windows was if the smb folder was mounted but the device disconnected (which sometimes it was doing, freezing the file explorer for several minutes before giving up on the share and marking it "disconnected", aaaah windows).

Anyways, thanks a lot, I wish i had an actual fix to document here for future users, but I only have this overkill workaround.

Sounds like a EMI / grounding issue.

(the first error means that the card did not respond to a request)

Is the serial connection differential?

If so is there enough noise to exceed the common mode range of the serial interface?
(7I96S RS-422/485 port common mode range is -7 to +12V)

You might try  a common mode choke (large ferrite bead) on the serial cable

 

1. The GUI does not send motion commands, though through the GUI, the user
may ask LinuxCNC motion component to jog, or pass to MDI commands to the Gcode
interpreter.  The GUI does display the motion that the motion component generates.

2. LinuxCNCs Gcode interpreter communicates with the motion component. The GUI
is just a command and display interface it does no direct motion control.

3. The GUI communicates the jog request to LinuxCNC motion component via hal pins

4. Which physical pins connect to Stepgen 00 is determined by the firmware (Normally
this mapping matches the hardware for example Stepgen 00 connects to the 7I95s
STEP 0 and DIR 0 pins)

5. Not sure about this question but All step/dir pins are always driven and there is no sensing of pins
(DIR- and STEP- are just inverted copies of DIR_ and STEP+)

6. Its not obvious so there are tools to generate the hal/ini files like MesaCT

To understand the inner workings a good approach would be to study a working
hal file in addition to the manual pages of the various components used:

man motion
man hostmot2
man pid

github restart correctly after 30min ... all solved.

About other error ... running  dpkg-checkbuilddeps command discover a list of unistalled libs (why if LMDE 6 have on package manager linuxcnc and linuxcnc-ethercat ???? .... mistery of life).

Any how now I have all lib needed istalled and visible from my c++ heather file. Hope it works now as aspect.

Thaks to all ....

Hello people, I am currently using a custom board which is connected to my 7i96s via the serial interface.  When I switch on the drives, I often get errors like the one in the picture below: the connection to the additional card has been lost. I don't know what to do next. I use the latest version of LinuxCNC 2.9.3 as the operating system

Hello,
I'm currently trying to retrofit a mill and a lathe. I want to avoid being dependant on copying&pasting others' configurations, but rather understand the fundamentals myself so I can tailor the retrofit to my needs. I've read the documentation, several forum posts and watched Youtube tutorials these last few days, but I don't get how everything ties together. 

I am not sure if I've understood it correctly, but here is how I think Linuxcnc works conceptually. Let's use a 7i95T mesa board connected to a closed loop stepper motor, and how a position/velocity command from GUI makes the stepper motor move as an example.(I've also attached the full HAL file I'm using as a reference). 
Step1) Gmoccapy GUI sends a position/velocity command ->
Step2) The joint.0.motor-pos-cmd sends the command as output, to pid.0.command which takes the command as an input ->
Step3) At pid.0.command the command input gets correction through feedback internally(by PID-component and the correlated feedback pins), and the pid.0.output sends the command as output.
Step4) hm2_[MESA](BOARD).0.stepgen.00.velocity.cmd receive the command as input, which then makes the physical pin/terminal of 7i95T(Terminal block 3, Step 0, pin 1 to pin 6) output the command as step/dir pulses to stepper driver.

---

Question 1) Is my thought process above correct?

Question 2) How does the GUI like Gmoccapy send position/velocity commands through G-code to a joint/axis when there is no HAL-pins connecting them. Is this done internally? Shouldn't there be a Gmoccapy-pin connected to a Joint-pin from the motion component?

Question 3) How can a jog button make a joint/axis move, when the gmoccapy-jog is a bit input, and joint-pos-cmd is a float output? I.e connecting through net command: gmoccapy.jog.axis.jog-x-plus (bit IN)     to      joint.N.motor-pos-cmd (OUT FLOAT)? Is Linuxcnc internally just registering True/false from Jog button, and then sending the joint/axis the position/velocity command based on INI settings? 

Question 4) How does hm2_[MESA](BOARD).0.stepgen.00.velocity.cmd know which physical pin on the Mesa Board is will send step pulses to? Is this done by the Mesa Firmware when doing the MesaCT config?

Question 5) How does hm2_[MESA](BOARD).0.stepgen.00.velocity.cmd know which "physical pin/terminal" on the Mesa board it should send step pulses to, when it doesn't know if I have wired the 7i95T to the stepper driver with differential signal, or single ended with either common anode or common cathode?

Question 6) I have a difficulty knowing which HAL-pin need what input/output, without looking at other peoples config and decipher/copying them. I feel like this is the biggest part I'm missing from understanding Linuxcnc. I am not sure if I'm using the documentation the right way, because I don't find it intuitive at all. For instance, How should I know that Joint.0.motor-pos-cmd is the HAL-pin that makes a stepper motor move, and that it sends a specific output which hm2_[MESA](BOARD).0.stepgen.00.pos.cmd needs? And that pid.0.output could also be used instead of Joint.0.motor-pos-cmd to control the stepper motor? Maybe I'm just too stupid to connect everything just by reading the description provided by the component documentation. 

Any tips or explanations that could help my understanding of Linuxcnc are appreciated.

Disclaimer: I have no background in Linuxcnc, electronics, programming or anything CNC related. Apologies if I'm asking the obvious.
 

git pull
Magic. What I type stays.
My board has arrived in the UK and is expected tomorrow so the learning curve can only get steeper now but I can move forward.
Thanks.

M6 is one of the built-in Mcodes that can be 'remapped', Depending on the complexity of the customiziation it can be as easy as an ngc file or as complex as a python script:

linuxcnc.org/docs/2.9/html/remap/remap.h...lated_codes_t_m6_m61

[edit]

If you only require minimal changes to then start with section 5.6 in the document above.

Yes, exactly what I'm looking for. Then if I need to change M6 let say, how can I do that?

loadrt oneshot names=oneshot.GUI-ERROR
addf oneshot.GUI-ERROR        servo-thread
setp oneshot.GUI-ERROR.width           2
setp oneshot.GUI-ERROR.retriggerable   0
net GUI-error            axisui.error                 oneshot.GUI-ERROR.in
net BORRAR-ERROR-GUI     oneshot.GUI-ERROR.out-not    axisui.notifications-clear-error

Work for me.