Advanced Search

That is OK for a Mesa card and about where mine ran for years. I'll try and remember to look at my brix tonight.
Did you do the cpu affinity?

Hi, 

I have a touch probe that requires an additional activation signal prior to probing. I've mapped motion.digital-out-00 to the pin and would like to know the best way to add M64 P0 before probing and M65 P0 after. Should that be added to each probe routine, or would it be better to use a macro for that functionality? I'm using Qtdragon_hd and Versaprobe.   

Thank you

I have a STM32H753ZI development board and would like to install remora, would that be possible?

I isolated the cores today and ran the test. Still need to do the kernel upgrade.  

FYI: Based on memory and a quick look, it appears the default and maximum velocity and acceleration variables (4 total) have an added "LINEAR" in the name for 2.9.4. This is from comparison of the TRAJ section for 2.9.4 and TRAJ and AXIS in 2.7.14 documentation.  The 2.9.4 document does mention some additional variables that carry over from the conversions involving scale aspects.

iov2 seems to removed from master..
I have manual tool change that is connected to an output pin that releases the tool(hydraulic) so spindle must inhibited from running when this is activated
also when spindle runs tool change must inhibited
Both inhibitions must be done for safety reasons.

How to do this ?

I was trying to have this automatically set so that upon login/startup, it is set.

However, Im good with your solution. Only thought would be if I can activate with a button on screen as well. Or better yet, connected to one of the existing buttons like Probing screen. What would be the best way to achieve this? Would that be via User buttons, and if so, how is thee M101 called for use in a User button?

If it is just "settings" I just hope they're better than the compatibility layer that the rpios uses.

Thank you PCW for your unconditional support.

is that just on acceleration, or is that lag on a straight line?
what is is the acceleration?

20 microns if its only on high acceleration and speed is "a good starting point' i think. shows much promise.

for comparative reference

My JMC ihsv57's were tuned to about 6 or 8 microns, at 0.3g and 1800rpm (as fast as they would go)

My omron ethercat servos are now tuned to like 4 microns in in acceleration moves at 1G and 1 micron during constant speed.

Made suggested change...another issue.  The provided line was in the file from the conversion script and I totally missed it as I was preparing INI and HAL files base in Imperial values rather than metric.    However, another issue arose: program could not find variable INPUT_SCALE.  I believe this is the updated name for the old (2.7.14) STEP_SCALE.  I changed the INI to reflect this and tried again.  Still an issue.

Notably as I have been working on this configuration conversion.  I have encountered several apparent variable name changes between 2.7.14 and 2.9.4,  Unfortunately I did not create a list which at this point would have been helpful.

In any event here is the set of documents for my latest attempt:

The "Z" signals are needed if you want to home to index.
(for more accurate homing)

Yes, normally you would connect the encoder ground at both the
drive and 7I97T end.

Dont know if this help but I managed to tune the following error to around 20 micron at 3000mm/min. The drive is non ethercat, just regular step+dir. Tuning it was quite trivial. Turning speed forward gain to 100% should reduce the following error significantly

Good on you for saving another 400E,
Mark

Yes, i checked the files twice but could not find anything strange, so try using the "show hal configuration" from the "machine" menu to watch the charge pump pin if it gets active when you enable LinuxCNC.