Advanced Search

Maybe take another look at halui.joint.N.analog in the manual... looks like it's a jog-speed multiplier, not an absolute speed command.

And I didnt see where you set the jog speed pin to a particular value.  If my suspicion is correct, you're effectively multiplying the analog value x zero.

Try setting halui.joint.N.jog-speed to some value (same with axis) and see if that does it.
 

That is what I have been looking up and where I got most of that config from.

I would have thought that once I got one or both of halui.joint.0.analog halui.axis.x.analog going from -1 to +1 that would be enough.

I have not actually seen a statement in the manual stating this.
I am assuming there is something else I am not setting.

There are a lot of pins relating to analog and jog and it is difficult to understand the interactions between them

Dear meister:

In simulation mode the velocity is 1,  the result is correct



Tim
 
 

very strange

i can only test in simulation at the moment, can you try it also in simulation mode please !?!

bin/rio-generator -S carrot.json

meister:

I redownload rio in a new folder, and used new gui rio-flow to config again

 
 

PCB is build by myself, it used a 12Mhz oscillator


Tim

 

Some time ago I purchased a Stmbl V5  drive, but never used it. Means it is new, unused.
I would ask 120€ including shipping to Germany or Austria- current price for a ready Stmbl V5 is ~220+ shipping from what I remember
So if one would need this to play around with contact me via email please  This email address is being protected from spambots. You need JavaScript enabled to view it.

 

hmm, i see the 1.0 velocity

Which version are you using?

# git status

 

I'm curious to see how the machine performs.

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