Advanced Search

Also, anytime you update if there is something missing in probe basic using your machine config on program open, check the probe basic simulation from within the linuxcnc sims. It will always have any updated requirements performed. If the sim opens and appears normal, then it's a safe bet that  it's your machine configuration requiring new updates. We put information right on the status page that is updated with new releases with a link to any requirements due to upgrades in probe basic.  Always start there.

Read the release notes!

kcjengr.github.io/probe_basic/update_notes.html

Hi. Yes, but no.

Speed tutorial is there but its just procedure what to send to drive. I have no clue how to implement that to Linuxcnc. 

 Thank you.

Looking around, this may be a Ryzen/kernel version issue.

Typically this is done by by connecting the MPG count to all axis
and selectively enabling jogging on the desired axis

Yes.  That's the idea.  I have a 7i96s already mostly wired.  I spent much of this weekend working on getting the configuration setup, using pncconf.  Only to find that Claude (online AI) led me astray.  I should have been using stepconf.  Or even better... MesaCT. 

pncconf and MesaCT can both create 7I96S configurations, stepconf cannot (stepconf is for parallel port hardware)

To tell the truth I'm not a big fan of Rufus, it tries to be too smart by far.
When I had to create bootable USB stick via windows I always used win32diskimager.org/

Or if using Linuxdoes the job fine, askubuntu.com/questions/1333102/what-is-...-hard-drive-over-usb

> Why not just use it as-is?

• I don't have a license for Mach3
• I prefer to use Ethernet
• I'm removing Windows from all my computers, before October.
• LinuxCNC does not fit on the old computer.

The PMDX board and the pendant will be repurposed for a Sherline from the same guy.  The CPU is barely practical, but I'll give it a try for that Sherline. When that 22 year old hard drive dies, that's the end of that too.

> Maybe just put a mesa board in place of the PMDX
> ... wire the drives directly to Mesa 
Yes.  That's the idea.  I have a 7i96s already mostly wired.  I spent much of this weekend working on getting the configuration setup, using pncconf.  Only to find that Claude (online AI) led me astray.  I should have been using stepconf.  Or even better... MesaCT. 

> Does it work fine right now?
Who knows? It was working fine in 2009, when it was last used. Yes, the servos move. I can't yet try the spindle until I put in a new electrical circuit.  My garage has one outlet, shared with the lighting and garage doors. And my breaker panel is full. 

> What is that IPAC board?
It takes commands from button presses on the pendant, and injects them into the keyboard communication. Then you run Mach3 with keygrabber so that the pendant buttons are captured and sent to Mach3.  There are two ps/2 keyboard ports on the IPAC.  One goes to the computer, the other to the keyboard.  (Which is a real IBM M1... precious metal to me.)

> He obviously took pride in his work.
Yeah.  I was surprised he didn't use more off-the-shelf options. Learning and building was his joy, so that makes sense. 

>Why change something so neatly and carefully made?
I can't make use of the pendant because the new computer doesn't have any parallel ports, and the pendant needs its own parallel port. 
The servo control box will look exactly as it does, except the PMDX board will be swapped out for a Mesa 7i96s. 

 

I have two rotary switches, each switch has 2 outputs driving inputs on a MESA card as 00,01,10,11

Switch #1 is used to select MPG increment 0, 0.0001", 0.001", 0.01"  I'm using a MUX4 to control that. No problem with this.

Switch#2 is for selection of where the MPG ticks   ( net encoder-counts  <= hm2_7i96s.0.inm.00.enc1-count ),gets routed, so to either:
X, Z, C (Compound), or N(None), so....
axis.x.jog-counts
axis.z.jog-counts
anglejog.counts-in
or to nowhere when position N is selected






 

Is that the Delta 2000 CMC-EC01?
There is a manual for download includes a speed demo example.
downloadcenter.deltaww.com/en-US/Downloa...=cdate&sort_dir=DESC

It work well using this : self.myPin = QHAL.newpin("MyPin", QHAL.HAL_BIT, QHAL.HAL_OUT)

Thanks a lot for your help

pin hm2_5i25.0.write.time did not change anymore.

Suggests this is a PCIE communication issue and probably
not related to 7I77 5V

It may indicate a grounding/EMI issue. Do you have an issue when
the 7I77 in not connected to the rest of the machine?

This is why i asked for a dmesg log as PCIE issues should show up there.

EMI was also one of my suggestions, at the time where the 6i25, 7i77 and the PC was part of the machine, so i decide to use shielded wires between the servos and their drives. Wires from drive to mesa are shielded too.
But the problem was the same.
Now i build a system with only the cards, the pc and rotary encoder but the problem is still the same.

Does dmesg show any errors?

Checked dmesg and there maby we have a track, the problem occur immediately after starting linuxCNC, this is the output:

[ 1323.534393] mce: Uncorrected hardware memory error in user-access at fcb01000
[ 1323.534404] Memory failure: 0xfcb01: memory outside kernel control
[ 1323.534405] mce: Memory error not recovered
[ 1323.534528] mce: [Hardware Error]: Machine check events logged
[ 1323.534532] [Hardware Error]: Uncorrected, software restartable error.
[ 1323.534535] [Hardware Error]: CPU:3 (17:8:2) MC0_STATUS[-|UE|MiscV|AddrV|-|-|-|UECC|-|Poison|-]: 0xbc002800000c0135
[ 1323.534541] [Hardware Error]: Error Addr: 0x00000000fcb01000
[ 1323.534542] [Hardware Error]: IPID: 0x000000b000000000
[ 1323.534544] [Hardware Error]: Load Store Unit Ext. Error Code: 12, DC Data error type 1 and poison consumption.
[ 1323.534546] [Hardware Error]: cache level: L1, tx: DATA, mem-tx: DRD

Is there any PCIE power management enabled in the BIOS?

Indead there was, but i disabled it before doing dmesg.
 

Hi everyone. I have made some progress on 3x Lichuan + 1x Delta C2000. Now I am able to measure the speed when the drive is turned on manually. But still no success with the speed command.

I found that the speed command in HAL CiA402 is 60FF and here in Delta it is 6042. I have tried both, but when I set only 6042 in the XML file, I am not even able to turn on the drive.

Any idea? Thank you. 

 
   

Its unlikely this is specific to the encoder but maybe to changing PCIE data

Did you check dmesg kernel log?
 

Thanks for your quesses. The encoder that is now connected is mikrocontroller that simulates the encoder to trigger the error as fast as possible. The controller uses the single ended mode of the mesa and outputs 3V. I looked up the datasheet of the encoder ic on the 7i77 and 3V is in the ic s range. on a second encoder input i have connected a rotary encoder, that uses the 5V of the 7i77. 
And in the beginning the encoder inputs were connected to a 5V glas scale.
We also tried the encoder outputs of an ESTUN Servo drive.
All gave the same (bad) result.