Advanced Search

I'm working towards getting a servo on the knee/bed of this machine, but I'm not there yet.  I will have a glass scale on the knee axis soon, but adding the servo is a bit of a project that will take some time.  For now I just have servos on X and Y, and W and Z will be manual.

I have not read up on the extra joint functionality so I'm not familiar with how it works.  I'll give it a look!

FYI I did end up submitting this as a PR ... github.com/LinuxCNC/linuxcnc/pull/3324#issuecomment-2642569284

-Steve


 

NT4Boy wrote:

loadrt not count =2 (I'll just show one here)
add not.0 servo-thread
net my-input-signal-1 <= hm2_7i92.0.encoder.03.input-index
net inverted-signal-1 = not.0.in
net inverted-signal-1 => your-desired-component (which I guess is min-y)

Yeah, that is not OK, should be something like
loadrt not count =2 <<<<< if you need two inverted pins, needs also another addf
addf not.0 servo-thread
addf not.1 servo-thread
net my-input-signal-1 <= hm2_7i92.0.encoder.03.input-index
net non-inverted-signal-1 = not.0.in
net inverted-signal-1 => not.0.out
net inverted-signal-1 => to whatever signal it needs to go

net my-input-signal-2 <= source of the input for inverting
net non-inverted-signal-2 = not.1.in
net inverted-signal-2 => not.1.out
net inverted-signal-2 => to whatever signal it needs to go

Yes, it is the index pins that are inverted. Thanks.
net min-y <= hm2_7i92.0.encoder.03.input-index is a pin that needs inverting.
i tried with
net min-y <= hm2_7i92.0.encoder.03.input-index-not , but it errors
the other syntax my friendly AI chatbot suggests for this is:-

loadrt not count =2 (I'll just show one here)
add not.0 servo-thread
net my-input-signal-1 <= hm2_7i92.0.encoder.03.input-index
net inverted-signal-1 = not.0.in
net inverted-signal-1 => your-desired-component (which I guess is min-y)

I don't get what the connection is between inverted-signal-1 and my-input-signal-1
Or should all three lines read inverted-signal-1

Still trying to learn.

vizavadsky wrote:

Could not open command file 'custom_postgui.hal'
Could not open command file 'shutdown.hal'

Edit the ini file and omit those two lines then try again, usually they are not used.

unknown wrote:

Be wary of those devices, they could just be a USB to parallel port. I bought a similar device thinking it would be a proper hardware serial port, but what it actually was a a USB to serial port.
Getting the right laptop to work can be a bit of a hit & miss exercise. Tho it's not something that I would recommend for a parallel port setup. Mesa maybe.

 

Ah, I hadn't thought about the "hidden" USB being a risk at all. 

Tommy Light has a good little thread on Lenovo laptops that he has gotten to work great on production machines so if I go down this path, I would try to get one of the ones he has had luck with. But yes, he does run them on Mesa Ethernet cards. 

Thanks again, let's see what I'll end up with. This is research as of now though I do think I'll pick up the lathe within a few weeks. 

Thanks a lot, this is now working well.

I think it's good to have an information system that notifies also about new features that are disabled by default (for compatibility reasons).

I implemented such, based on Acieras snippet.
It is able to hide the messages you have read but displays new ones id there will be any in the future.

You can try it out using this branch: github.com/hansu/linuxcnc/tree/gmoccapy-info-message