Advanced Search

hi i get a issue...

i have an very old servo driver that needs a 5+ pdm signal about 10khz.
my card i use is a 7i92.. the pdm output is sinking on the 7i92.. correct?
what is the best way to convert it?

thanks

Digging into a bit deeper, whenever I run it in reverse the setting jumps to 8.25 and stays there. If I run it forward it stays around 2.69 with some variation in the next 5 digits. It moves up and down with speed adjustment. 

This should work.

Thank you for letting me know about halshow. There is a wealth of data in here that will be VERY helpful. Unfortunately, the image size exceeds allowable data limit so I can't attach them just yet. Looking into reducing the file size. 

Thanx and I sorry about changing subject line...didn't realize it created problems.

I’ll test this out.
I ran the latency test before but wa slightly confused how to read them .

I think part of the issue I’m having is the crappy bios and not being able to disable things .

OK so fairly complex...

As I said before, maybe the first step is to take a look at
hm2_5i24.0.7i83.0.2.analogout0 in halshow when running
the spindle in each direction.

Dear new Member please don't change the Subject when posting it renames the thread in the Index and makes it hard to find

4GB RPI5 is fine, if you are going to jump that way. But I'd be more inclined to look at the x86 offerings from Odroid. I've been using one for 4 or 5 years without an issue.

Sorry , I guess you are right, G33.1 also looks at the spindle speed 
But this works better with good velocity estimation, Though as I mentioned
you cannot use position interpolation except for constant speed applications
like threading on a lathe.

This is wrong because the TP does use the velocity value:

It is precisely true, LinuxCNCs TP only looks at the encoders position
in G33.1 moves. There is no other information path.

Looking a bit more into this, It does not look like the encoder velocity
( spindle.spindle_num].spindleSpeedIn ) is used for position mode synchronized
moves (G33 G76 etc) but only velocity mode synchronized moves (G95).
At least with a quick look at  tp.c 
 

PCW wrote:

Velocity estimation is unrelated to G33.1 as G33.1 only looks at position.
 

It is not true.
Tool moves while spindle stops, even if position is reached.

Hi,
I'm not too familiar with the integration into probe basic, but I'm pretty sure the surfacemap tab did work when it was released.

It's possible that posting your config might help narrow down any issues.
And can you show your halshow for the relevant pins when you believe it should be enabled?

Also, It is possible to use the compensation component standalone, with no involvement from probe basic, even if the process is slightly more manual.
Use the version from Scott's Repo and follow the instructions there:
github.com/scottalford75/LinuxCNC-3D-Pri.../master/compensation

For PCB milling, I think that this compensation component should work really well. Since the component is taking the current XY point and outputting compensation in Z, it's always 'playing catch-up' as the machine moves, but unless you're demanding very quick changes in the compensated value (think feeding fast over a rough surface) any deviation in the compensated position isn't really much of an issue.

I haven't tried any other compensation approaches, but G-Code Ripper with the Auto-Probe operation can warp your G-Code to the probed surface.
The version bundled with LinuxCNC is located in the /usr/lib/python3/dist-packages/qtvcp/lib/ripper/ directory (and you can run it standalone if you want).

It may be fixable

What servo thread period are you using?

what does:

sudo chart 99 ping -i .001 -q -c 60000 [7i96_ip_address]

report?

(it should run for 1 minute and report timing statistics, [7i96_ip_address] is the IP address of your 7I96S card)

Did you run a standard latency test?
 

I believe I got them and then some. 

Velocity estimation is unrelated to G33.1 as G33.1 only looks at position.

If you do position interpolation, it's only for threading (Constant speed)

Also, as I mentioned, you need hardware timestamp support for velocity estimation.