Advanced Search

In [EMCMOT] section of your ini file you need to remove this line:

The ini file parser takes the first match when looking for a keyword hence the next line with the 'unlock_joints_mask' is not taking effect.

MPG - initial attempts



is used original connection of MPG wheel to Encoder 4, configuration only with PNCconfig and manual editing of one component in HAL file based on the solution in this post :
162.243.45.186/39-pncconf/51627-mpg-issue-on-mesa-7i77

net joint-select-a     (b,c)


to

net axis-select-x    (y,z)

I need to change the scale and maximum speed settings.

It's a shame that the MPG configuration error in PNCCONFG hasn't been fixed - it would be possible for beginners (like me) to configure MESA 7i95T (and others...) using only PNCCONFG without manual editing
 

Bonjour , 
je voudrais mettre le freins sur l 'axe rotatif A, j'ai mis le fichier ini a jours mais je pense que j 'ai quelque chose qui manque , pouvez vous m 'aider?

I have expanded rio so that you can also create rpi5-gpio and parport configs.




it's not direct mixable with the FPGA configs

Hab mal rio aufgebohrt, so das man auch rpi5 gpio configs generieren kann

Hey and thanks for your reply!
I experimented with version 2.9.6 for a bit, but I can not find the fault that causes my problems. It just does not make sense that my config functions perfectly when running 2.9.4 and then goes broken after updating to 2.9.5/6.
I also noticed that calling MDI commands does not work. I have a command that zeroes my z-axis, which I can activate via a pyvcp button. This does not work anymore.
I am a bit relieved that I am not the only one having issues after updating, but I would love to find a solution to all of this!
As for now, I will stick to 2.9.4..

FOUND IT!

After 3 years since I bought the MPG, finally found the cause and solution of the issue of not being recognized on some (or all in my case) USB ports. It probably also solve if somebody got connection problems.

The main issue is that the XHC WHB04b receptor needs quite a lot of power (comparing to other USBs) to maintain a stable connection, and not all USB ports does provide such high current. So if the connection is not stable because the power issure, the kernel does not detect it. This can also happen on windows, but the windows specific drivers solve it on some cases. My computer is an industrial mini PC with external 12V PSU, so all USBs get their 5V from the main board. On desktop computers, front forts have usually lower power than rear ones, causing the issue.

There are a couple of really easy and cheap solutions:
-Use an USB HUB with external 5V power supply
-Use a Y cable (2 male, 1 female USB) either with both male USB connectors to the computer or the power only connector to a 5V PSU.

If your test machine has no external e-stop circuit you shouild simply connect the e-stop out signal to the estop in signal in your hal file. Something like this:

net estop-out <= iocontrol.0.user-enable-out
net estop-in => iocontrol.0.emc-enable-in

Then the e-stop buttons on the userinterface will work. and you will need to toggle them when starting Linuxcnc.

I don't think you would need to change anything in your servo drive. The only changes should be how it is seen and commanded inside Linuxcnc.

How is your servo currently commanded? I presume it is by step/dir commands in position mode? That would not have to change, you would simply have to change what signals are commanding the Mesa hardware stepgen so that they are commanded by the spindle commands instead of the joint that it is currently commanded by.

For weeks, I've been working on my own CNC machine and have made good progress, but I need help with some small details from experts.The machine is a MicroCarve MV3 with 3x 23-305-DS8A steppers in bipolar parallel mode, connected to a TB6600, which is connected to a Raspberry Pi 4. I don’t have a stop button yet.I’ve managed to wire the motors and Pi to test the axes with a Python script. I also created a minimalist INI and HAL file and started TkLinuxCNC. However, I can’t move the motors because the software shows an E-stop, and despite my efforts, I can’t get the machine to move.I access the Pi via VNC without a connected monitor. The image used is rpi-4-debian-bookworm-6.1.54-rt15-arm64-ext4-2023-11-17-1731.img.xz, updated to LinuxCNC 2.9.6.Friends, I need help. I’ve spent many hours on this and am close to getting the machine running.My test script works; HAL and INI files are attached.Thanks,
Dragan