Advanced Search

meister:

my json file

and sorry about the frequecy I write wrong: when command is :G53 G01 F60 X100output pules frequency is about 1.28khz
because my scale is 1280, when F60 (1mm/s), output frequency is 1280 * 1 = 1.28Khz
the stepdir.velocity is show about 0.5mm/s


Tim

Great work! When I first tried lcec_configgen, the output was useless, common on multiaxis drives. But recently I tested it after some changes made by Grandixximo and he now has an inbuilt driver for the OL drive so its even easier than this xml you used. And yes, it think it will work for the open loop version too. He should see this and might be able to extend the OL driver to support this too

Looks OK

Might be worth disconnecting the analog hal pins in hal and just setting them
manually (connected and unconnected to the drive) to see whats going on.
 

Yes. I am connecting to the two honda connectors labeled J10 and J5 on this diagram. 

Please let me know if you see any mistakes in this. 
Machine side       ->      Mesa 7i83
Pin 1, PRDY1X    ->      TB2, Pin 1, ENA0-
Pin 2, ENBL1X     ->      TB2, Pin 1, ENA0-
Pin 3, OVL1X       ->      No Connection Currently
Pin 4, VRDY1X    ->      No Connection Currently
Pin 6, TSAX         ->      TB2, Pin 16, AOUT3
Pin 7, VCMDX     ->      TB2, Pin 4, AOUT0
Pin 13, 0G           ->      No Connection Currently 
Pin 14, PRDY2X  ->      TB2, Pin 2, ENA0+
Pin 15, ENBL2X  ->      TB2, Pin 2, ENA0+
Pin 16, OVL2X    ->      No Connection Currently
Pin 17, VRDY2X ->      No Connection Currently
Pin 19, TSAX      ->      TB2, Pin 15, AGND
Pin 20, ECX        ->      TB2, Pin 3, AGND


Machine side       ->      Mesa 7i85
Pin 1, 0V         ->      TB3, Pin 3, GND
Pin 2, 0V         ->      TB3, Pin 3, GND
Pin 3, 0V         ->      TB3, Pin 3, GND
Pin 4, +5V       ->      TB3, Pin 6, +5V
Pin 5, +5V       ->      TB3, Pin 6, +5V
Pin 6, +5V       ->      TB3, Pin 6, +5V
Pin 8, OH1X    ->      No Connection Currently 
Pin 9, OH2X    ->      No Connection Currently
Pin 14, PCZX   ->      TB3, Pin 7, IDX0
Pin 15, *PCZX  ->      TB3, Pin 8, /IDX0
Pin 16, PCAX   ->      TB3, Pin 1, QA0
Pin 17, *PCAX  ->      TB3, Pin 2, /QA0
Pin 18, PCBX   ->      TB3, Pin 4, QB0
Pin 19, *PCBX  ->      TB3, Pin 5, /QB0

   

The only parameters that affect the frequency are
* stepdir0.velocity
* stepdir0.velocity-scale
* stepdir0.velocity-offset
and the FPGA clock frequency

Could you please attach your .json file?

Huge update everyone! My Gentoo image now ships with LinuxCNC preinstalled, many bugs were fixed, and a lot of packages were added. The image size grew by quite a bit but this functions more as a complete Linux system with some extra applications such as GIMP and Krita. Browser has been switched to Konqueror and 4K videos on YouTube play excellent on my old GPU.

github.com/NTULINUX/gentoo_backup/releases/tag/v0.4-alpha

Same instructions as before, still no RTAI support but I'll get there eventually. The issue before was that I was trying to stay under the 2GB file limit on Github, but now since I split the tar into 2 files, this gives me more range. It is now ~3.3GB in total for the download, and the minimum space requirement has been bumped as well (16GB minimum for the root filesystem)

This ships with the following packages, list not complete:

FileZilla
GIMP
Krita
Inkscape
FlexGUI
mesaflash
halviewer
LinuxCNC
Hexchat
Konqueror
NetworkManager (with applet)
XFCE
LXQt
guvcview (camera)
Kate
Geany
btop
htop

For qtpyvcp/probe basic:

Dear meister:
 
I used MDI command to move x axis for a example. The velocity is 60mm/min, and used halshow to watch pin:rio.stepdir0.velocity
the value is about 0.5mm/s, but the motor run in right speed,and I probe the x axis's pules signal used a oscilloscope
and it show the freqency is about 12.78khz, my scale is 1280 in .ini file
if I use stepdir to drive a servo motor to run a spindle, I net the spindle rps to some one stepdir.velocity then spindle run in a wrong speed
whitch parameter I set wrong?

Tim
 

Do you have a document for the actual driver pinout?

 

It's a joystick, and those have been analog for the last 20 years or so, last digital joystick i had was 30 years ago.
In short, you are looking at the wrong thing, search for joystick, not for analog joystick, or xbox controller or PS2/3/4/5 controller, there are some here on the forum.
html.duckduckgo.com/html?q=linuxcnc%20joystick

forum.linuxcnc.org/10-advanced-configura...ning-detailed-how-to

forum.linuxcnc.org/27-driver-boards/3559...ethernet-mesa-boards

What is the best way to verify the ground? Measure the resistance from the machine frame to the drive frame and mesa boards frame?

The machine was originally setup with a virtual tach using a f/v converter inside the Fanuc controller. Here is a diagram of the original setup. 


Thank you again for the help!

This might be the point where I can give my software-expertise to this project

I wrote some software which simulates the spindle control behavior based on the files uploaded here 17.5.2026. I have very little understanding of actual linuxcnc, so take everything with a grain of salt. The simulator is quite crude and it's translated in python, as I do not have access to a physical LinuxCNC machine for now. I'll need some confirmation that it somehow resembles the actual behavior of the Schaublin now before I dig in further. It does look like that the pid works "ok'ish" on low gear, only a minor overshoot, but it's way off on high gear. There's some possibility that the simulator could be useful when developing a state of the art control. I would also say that no extra hardware is needed, many things can be deducted from the spindle speed, cvt end switches and the motor hz.

The thingy is now there, I did not spend too much time on it, it's also mainly vibe-coded. The translation of the .comp logic is in spindle_supervisor_model.py lines 161:582

github.com/heff3/schaublin-cvt-simulator

Easiest way to get it working is to use "uv", it's a modern python virtual environment manager (does not break your machine). AI will help with this one, but on mac the most convenient way is with "brew install uv". Brew is the most common package manager for osx.

After cloning the repository, one should be able to:
uv run python spindle_realtime_simulator.py

q - quits the application (or the usual ctrl+c)
space - starts the motor
k / j - tunes the target spindle rpm


The simulator behaves better once it has run awhile with a few toggles on/off, dunno if the real lathe behaves the same?

ALERT: The real lathe might have insufficient max rpm limit now. For example if one targets 2000rpm, the pid might overshoot it quite a lot.

The trajectory of what gcode file of the maximum size can be visualized with acceptable performance? Or I’ll ask differently: how many segments are the maximum?

I was making a similar interface and ran into browser limitations in terms of memory, etc.

No response.
So, is what I am trying to do possible.
I want to jog the machine in X-Y-Z using an analog joystick with gmoccapy as the frontend with the jog speed dynamic based on the joystick position.

Anticipate only allowing jogging when in the jog menu of gmoccapay.

Also of note when I am jogging using the jog buttons in gmoccapy and move the joystick the jogging stops. Is there a conflict between gmoccapy and the analog controls. 

Hi Rod. Since the back gear is only switched when stationary, there is no need for such feedback. logging the command is enough. Sanity check once the spindle turns and you can see the overall ratio.