Advanced Search

As I also stated on github, I really like the MDI queue, but I understand why some may not want it. Please make it configurable. I would even say that the old queue behavior should be the default, and if someone is making machines to sell, they can put a line into the ini file to remove the queue. No need to take it away from me, I used it a lot... until a few days ago when I upgraded... to find out that someone decided for me that I should not have it!

That would probably require modifying the PlasmaC component code as it is built in:
github.com/LinuxCNC/linuxcnc/blob/master...ponents/plasmac.comp

I mean this where is in qtdragon_hd gui
linuxcnc.org/docs/html/gui/qtdragon.html#_touch_plate

EDIT: I double checked and it seems you received my email. I removed your email from my post. I will type out a small part of my email here for other people in the community who might find it useful in the future.


Part of email:

Importantly, I have an external encoder that is already attached to the lathe headstock, so I DO NOT need to use the encoder on the servo driver, infact, I already have the encoder set up correctly to my mesa board. In a future project I may use the servo encoder but i suspect my drive does not actually have encoder output setup as the manual says not all versions come standard, and i have no connector (although it must be somewhere inside haha)


Using your files, here is the progress I have done:

1. I have went through and integrated my machine parameters into your hal and ini, halcompiled the caxis and gn-userkins, and added the remapped gcodes
2. The software does boot up successfully but doesnt fully work: X and Z move and work fine. The encoder works and outputs the live C value

What does not work - something that has failed me in many other attemps

1. The C or spindle do not work, the first issue from debugging is homing - it seems homing does not work. I am going to try and disable homing or try a workaround
2. I suspect after homing is fixed, I will get some additional vague command line errors. Likely from my lack of coding experience and improper linuxcnc logic, but not certain.
3. There are a few other annoying issues I suspect, but I do not want to get ahead of myself.


I will also upload my current HAL and INI which are the only files of your I have changed. Is there any chance I could get your input on the HAL and INI and if you have any obvious suggestions I may be missing?

unknown wrote:

For the sunix cards that use parport_serial you need to look here for the list of devices.
github.com/torvalds/linux/blob/master/dr...ort/parport_serial.c

But notice that the driver code used is different depending on kernel version. As I linked to before here.
linux-hardware.org/?id=pci:1fd4-1999-1fd4-0100

Use this page to search by PCI ID to see what drivers match what card.
linux-hardware.org/?view=search

Driver matching & Loading (binding)
docs.kernel.org/driver-api/driver-model/binding.html

Wow! Thank you very much!

Model: Unitek Y-7507 ( 1245 / KFD-4VO / KFD-4V0 / E162585 / 94v-O / 94v-0 )
Chipset: Moschip MCS9901CV-CC
Interface: PCIe
Modes: PCSPP, TRISTATE, EPP
Supports X Mode: NO (Control register pins are not open collector)

A detailed report is attached.




 

If I received it, please delete the email address. I have another question: Do you have feedback from the servo motor encoder connected?

are you using sheetcams linuxcnc-plasmac post processor?

Work through this which Hakan was referring to.
docs.google.com/document/d/1jeV_4VKzVmOI...diY/edit?usp=sharing

If you have following errors when slowing down, your accelleration could be too high. I used to get this with my Ethercat drves (mostly on homing) and then surmised that possibly the inertia was overtaking the accell settings. Slowed it down a bit and it works.

Since you say 5V, assuming using the IDC26 connector, so inverting does not work for you, but using a single transistor and 2 resistors can do that easily.
Might also check the 7i76 manual if there is a possibility of disabling the pull up resistors, but even if it is, it would mean the outputs will be 3.3V, not 5V, usually not a problem.

I have a 6i25 7i76 setup that is outputting a PWM signal on an extra step generator (thank you peter). When my control box is powered on and linuxcnc is not running my PWM is at 5v. Is there a way to invert this signal so that I am getting 0v in that situation so i dont have to run it through a relay to cutoff output when linxcnc is not running?

Hope that made sense and here are my relevant hal lines.

# --- LASER POWER ---

setp hm2_5i25.0.7i76.0.0.output-00-invert true
setp hm2_5i25.0.7i76.0.0.output-01-invert true
net laser-shutter-output      => hm2_5i25.0.7i76.0.0.output-00
net laser-on-output        => hm2_5i25.0.7i76.0.0.output-01

setp   hm2_5i25.0.pwmgen.pwm_frequency 100
setp   hm2_5i25.0.pwmgen.00.scale 200
net laser-pwm-enable   => hm2_5i25.0.pwmgen.00.enable
net laser-pwm-value  <= motion.analog-out-00 => hm2_5i25.0.pwmgen.00.value

Thanks
Kent

 

INI =hal files and settings and scaling and....
HAL = connections between software and actual hardware
So if there is nothing about the spindle in hal = no spindle
And no shooting today, slept in total 5 hours in last 3 days, so i might miss !

For the sunix cards that use parport_serial you need to look here for the list of devices.
github.com/torvalds/linux/blob/master/dr...ort/parport_serial.c

But notice that the driver code used is different depending on kernel version. As I linked to before here.
linux-hardware.org/?id=pci:1fd4-1999-1fd4-0100

Use this page to search by PCI ID to see what drivers match what card.
linux-hardware.org/?view=search

Driver matching & Loading (binding)
docs.kernel.org/driver-api/driver-model/binding.html

Text removed