Advanced Search

I am trying to configure the spindle as a C-axis, but I am having a problem and cannot find a solution.
Could someone please take a look at my configuration and the video and give me some advice?
I was not able to post this in the original lathe thread.





#########################
# AXIS C JOINT 2
#########################

setp  pid.c.Pgain     [JOINT_2](P)
setp  pid.c.Igain     [JOINT_2](I)
setp  pid.c.Dgain     [JOINT_2](D)
setp  pid.c.bias      [JOINT_2](BIAS)
setp  pid.c.FF0       [JOINT_2](FF0)
setp  pid.c.FF1       [JOINT_2](FF1)
setp  pid.c.FF2       [JOINT_2](FF2)
setp  pid.c.deadband  [JOINT_2](DEADBAND)
setp  pid.c.maxoutput [JOINT_2](MAX_OUTPUT)
setp  pid.c.error-previous-target true

net c-index-enable    =>  pid.c.index-enable
net c-enable          =>  pid.c.enable
net c-pos-cmd         =>  pid.c.command
net c-spindle-pos-fb  =>  pid.c.feedback
net c-output          <=  pid.c.output 

# ---PWM Generator signals/setup---

268 net c-output            =>  hm2_7i98.0.pwmgen.00.value
269 net c-pos-cmd           <=  joint.2.motor-pos-cmd
270 net c-enable            <=  joint.2.amp-enable-out
271 # enable _all_ sserial pwmgens
272 #net c-enable            =>  hm2_7i92.0.7i77.0.1.analogen

276 net c-spindle-pos-fb    <=  hm2_7i98.0.encoder.02.position
277 net c-spindle-vel-fb    <=  hm2_7i98.0.encoder.02.velocity
278 net c-spindle-pos-fb    =>  joint.2.motor-pos-fb
279 #net c-index-enable     joint.0.index-enable <=> hm2_7i92.0.encoder.06.index-enable
280 net c-pos-rawcounts     <=  hm2_7i98.0.encoder.02.rawcounts

282 # ---setup home / limit switch signals---

284 net c-home-sw           =>  joint.2.home-sw-in
285 net c-neg-limit         =>  joint.2.neg-lim-sw-in
286 net c-pos-limit         =>  joint.2.pos-lim-sw-in


[AXIS_C]
MAX_VELOCITY     = 360
MAX_ACCELERATION = 500
MIN_LIMIT        = -900.0
MAX_LIMIT        = 900.0

[JOINT_2]
TYPE             = ANGULAR
HOME             = 0.0
FERROR           = 1000.0
MIN_FERROR       = 500.0
MAX_VELOCITY     = 360
MAX_ACCELERATION = 500

P        = 0.0000001
I        = 0.
D        = 0.
FF0      = 0.98
FF1      = 0
FF2      = 0
BIAS     = 0
DEADBAND = 0.1
MAX_OUTPUT = 10

ENCODER_SCALE    = -40
OUTPUT_SCALE     = 10
OUTPUT_MIN_LIMIT = -10
OUTPUT_MAX_LIMIT = 10

MIN_LIMIT = -1000
MAX_LIMIT = 1000

HOME_OFFSET   = 0.0
HOME_SEQUENCE = 1

Well Ive spent all day trying other installs or live versions and no dice. Cant get any to run live as they just hang at a blank cursor screen. Cant even get anything installed due to a "bad archive mirror" error.

Tried latest regular Debian and got that installed and then followed directions to install linuxcnc and got it up enough to latency test aaaaaand 4,550,000ns....

What causes this so I have some idea what to avoid in the future? What in the hardware would cause this?

We did some tests last year comparing IP network access vs raw packets
with Mesa HostMot2 and the statistical improvement of peak latency  was
minimal so decided it was not worth the effort.

There no issue with root access and LinuxCNC as direct hardware access
requires this and the blocking of normal network traffic on the real time
Ethernet channel also requires root priviledges.
 

thank you for the information Rod. mine has an hpr 130 torch on it and it uses technical gases while cutting, it is dual shielded. the probing happnens from the outer shield on wich the copper consumable touches the table and completes the loop with the ground cable. the wire for probing is connected to the outer shield itself, i can send a picture tomorrow if needed. i'll order two THCAD boards. how would i proceed to connect the one used for probing to the Mesa 7i97T? is it the same as voltage sensing? connected to an encoder input?

Try now

The point is that for most configurations you don't deal with pin numbers at all,
just channel numbers, which is also consistent with the hal file function naming.

For GPIO (which is not much used on newer systems) it would be helpful if
pncconf listed the pin numbers at least for parallel port BOBs

What is the point of this config page? This has to be the least intuitive config thing I have ever seen.

If this is:

forum.linuxcnc.org/18-computer/58339-socket-raw-eth

I get a 401 error if not logged in and a 403 error when logged in,
so I don't think it's a  user issue.

As Tommy alludes to Grub errors are usually because you have secure boot enabled. Turn that off in the BIOS. Trixie is batter with secure boot but still better to disable it.

In BIOS:
disable "secure boot"
enable CSM
try switching from Legacy to UEFI and vice versa.

Are you using VPN?
Try disabling it.
-
Forbidden errors are always from trying to access restricted parts of the web server, so something is wrong on users side.

I downloaded the 2.9.8 latest version from the first link in the download page
Burned this iso to a pen drive under windows using Rufus latest version
Live preview works fine
Graphic install consistently fails at the point of installing GRUB
         - this happened on numerous older PC typically inter dual core with 4GB to 8GB of RAM and installing to an SSD
As a trial I installed 2.7.4 which I had on a pen drive without issue

It should be noted the 2.9.8 installed perfectly onto a much newer NUC PC using the same pen drive

I have installed 2.9.7 without any issues and will (Debian 13) and will look to update to 2.9.8 tomorrow when time allows

Please advise if any more info is required
Regards,  Paul

Hello, with the update and after doing a sudo install mesaflash the board is found and its working...
Also mesaflash is now reporting 3.5.16...

So I guess I was too sloppy with my version I build and what I was actually using...

Sorry for bothering you with these basics... and thanks for the responsive help.
Saved me from swapping EEproms...


sudo mesaflash --device 7I90HD --addr 0x378 --epp --verbose

EPP device 7I90HD at 0x0378:0x0778
Communication:
  controlled by FPGA
Board info:
  Flash size: 16Mb (id: 0x14)
  Connectors count: 3
  Pins per connector: 24
  Connectors names: P1 P2 P3
  FPGA type: 6slx9tqg144
  Number of leds: 2

 

Mesa configurations do not use pin numbers but channel numbers for things like stepgens and pwmgens
As long as you have the correct firmware, the order of these channels typically matches the breakout

For GPIO, GPIO numbers are used (the connector pin == GPIO mapping is in the readhmid printout)

RotarySMP wrote:

Good weather for welding Nice progress.

Not on this side of the world where the the temp is hitting 40 deg c and beyond! We holidayed in Canada over Xmas so went from -20c to plus 40c which took a week to get back accustomed to!