Advanced Search

I'm using MesaCT to build a new configuration for a 3 axis mill with DMM servos in Analog mode.

I get the message that "Drive x Scale must not be blank".  Since scale is defined as "the number of pules to move one user unit", should this value be 0 for analog servos?

Thanks,

Skylor

I pushed some initial work.
If you use basic probe, setting the probe tool number in the tab will now also compare to the current tool number. If they match a HAL pin will be set (qtbasicprobe.probe-loaded)

In Versa probe, it works the same but at the moment you must set the probe number by editing the preference file - I ran out of room on the tab.
It's pin name is : qtversaprobe.probe-loaded

You would then connect that pin to spindle.o.inhibit.

I pushed this to master.
I changed a couple property names ( base_color and base_gradient_color) and added properties for the gauge center color (center_color, center_gradient_color)

Also added the details to the widget docs.

Qtdragon-hd now uses your new gauge styling to showcase the changes.
Thank you for this work!

Chris

sorry for not replying sooner. usually I get an email when a reply comes in. i also have not had time to tinker but i will check that out

Thanks Mecanix for helping us test. The 5.4.279 kernel shouldn't cause any regressions as it's all just backported fixes, and the respective LinuxCNC package for it restored some files I shouldn't have deleted in the earlier Debian package, so if anything it should be better and not worse, and this is a run-on-sentence.

On the servo enables and alarms is usually possible to combine all the
enables together so they can be driven by a single output, and likewise,
combine all the alarms so they drive a single input.

If you used a 7I96S, you may need to add a daughtercard to get enough I/O
The 7I95T probably has enough I/O but lacks the 0-10V. The lack of 0-10V
may not matter if the spindle drive can use an alternate speed control method
(also 0-10V can be added to the 7I95T with a  SPINX1 adapter)

Can you post HAL and ladder files? I want to see the tool changer code.
Thank you.
Scott

Hey, this is my code.

Not real pressing news but we wanted qtpyvcp built and ready to go since we use it to build custom GUI's.

Dave2024 wrote:

GeckoWorks wrote:

So, as for the question about signal levels for the B2 servos' Z pulse, I am honestly a bit daft when it comes to eletronics and don't even yet have a grasp on when a signal is digital vs. analog...

I can only find a mentioning of: " Z-phase Differential Signal". Not sure if that's what you're after. And then some screenshots from the manual:
 

 

 

Ok I think you've got a differential encoder.  Differential encoders will use 6 wires but you can also configure them to only use 3 if you wanted being single ended.  The wires will be A+, A-, B+, B-, Z+, and Z-.  Sometimes the encoders Z will be called Index or I.  So it would instead of Z+ and Z- its I+ and I-.  There both the same I and Z.  If you get the Mesa 7i96s theres a jumper called W3 that you can change the boards encoder input from single ended(3-wire) to differential(6-wire).  They come out of the box already set in differential so you wont have to move it.  Differential is what you want anyways its more accurate.  Also sometimes this differential and single ended terminology is called biphase encoding.  Theres like four different kind of encoding signal/protocols its all really complex and is difficult to understand sorry

Thanks for giving it a go:). 
So, perhaps to get homing to the Z-index pulse working, I just need two wires, maybe 1 In pin only, maybe 2. But since I think I will be needing an extra board with more Ins anyways, perhaps this is less important now. And the part about actually making this work can come later - it will take a while to get the boards here anyways. 

I've been digging a bit deeper in the manual and if I really needed to save on pins or somehow wanted to move some tasks out of Lcnc then I could actually have the servo drives do the homing themselves. The limit switches would then also go to the drives and I guess just one dig out and one in to basically tell the drive to start the homing routine and then an in to receive a signal that it was completed. 

But I think I want to keep as much as I can in Lcnc so just waiting for PWC to confirm which daughterboard he thinks is the right one (or anyone else with the overview). I am just dreading the whole sourcing/sinking question right now as it may impact which daughterboard I'd need...

I've finally finished at least one axis of my machine ( pic ), so I'm now continuing with testing of riocore and my one-axis prototype hardware for it.

Thank you very much for the quick reply!

I had tried to call the MDI commands 
halui.mdi-command-21, 
halui.mdi-command-22, 
halui.mdi-command-23, i.e. to use them again, which did not work.

With a new MDI command, it becomes quite simple.
 

The only useful thing on that module for this purpose is Ethernet PHYs. But even then, I don't think implementing an Ethernet core is worth the effort, considering W5500 and UDP2SPI bridges already (kinda) work.

Dmclements wrote:

The dpl firmware just turns my spindle encoder header back into general I/O, right?

No, the dpl firmware should be for plasma, so it make 3 single input encoders as it needs only encoder velocity to function.
Any Mesa firmware, if you do not use a module in hal, will leave the pins as normal IO.
Just do not load the encoder and use encoder pins as normal.
Beware those are only 5V pins.

Scratch that, my fault, used the wrong file extension.