Advanced Search

ok that makes sense, and after spending some more time working on it, including taking the scale back to 10, i have it now in a pretty good spot where i would consider it time to start tuning.

does the halscope guide tommy put together also work for tuning torque mode PIDs? otherwise im currently hunting out an equally well put together guide so i dont resort to just changing numbers and seeing what happens.

Thanks langdos, I did a similar fix

I have absolute encoders, so I just set the soft limits.

Maybe there is an issue with hard limits? Should I report this? GitHub issues?

You can also have a look at the EasyCAT:
www.bausano.net/shop/gb/home/1-arduino-ethercat.html

you can hook encoder pretty easily to that for much cheaper. And it is also quite flexible.
Encoder counting happens on arduino and current count is sent over EtherCAT to LinuxCNC, which saves you some hal configuration.

RE: EL1819 vs EL1809 response time - i think it includes signal debuncing, so 3ms does not necessarily have to be bad, because it's slower than 10us.

100 mA is a typical value for 5V, at say 24V the current is much less for most contacts (closer to 10 mA)
A small capacitor across the contacts can provide the wetting current without a large constant load.

If the relay does not show closed at 24V, its likely faulty...
 

This should be it.  

Yeh, my post must have broke. If you look a bit harder on eBay you will find better priced moduled for around $130. Some want stupid money. Don;t be frightened of buying from other countries...

Failed again to leave my workshop early.
Sorry i am blessed with writing jam at the moment, but good luck for recovery from the injury

version 2.9.4 did not get the change, only master branch.
You will need to save over the camview_widget with the supplied version again.

hey @rodw, was there something you wanted to add? looks like you just quoted my original post.... I know you have a lot of experience in this area, i have read more than a few of your posts so would love your input.

Thanks

The pierce delay starts from the beginning of arcOK so the delay turning the torch on makes no difference.
The internal relay will need a minimum current of 100 mA and the Mesa board generally can't deliver this. You need to add a pull down resistor as discussed in the qtplasmac docs.

bassti wrote:

At the moment, rotorhoming starts when i power on the machine.
The problem is that i want to home the z-axis first.

HOME_SEQUENCE in ini

Aforementioned docs references:

Reed relay:

linuxcnc.org/docs/devel/html/plasma/qtpl...l#plasma:reed-arc-ok

Contact loading schematic:

linuxcnc.org/docs/devel/html/plasma/qtpl...tact-load-schematics

Calculations:

linuxcnc.org/docs/devel/html/plasma/qtpl...asma:qt-contact-load

kworm wrote:

Unfortunately the relay in the unit is damaged and does not close. I ran through the diagnostics in the service manual to come to that conclusion and of course the service manual recommendation is to replace the inverter board which is half the cost of a new unit lol. It's also very difficult to access but some point down the road I will pull it apart and replace the relay on the board if possible. I'm going to try Tommy's suggestions and hopefully that will buy some time until I fix it or sell it and get another unit.

the most likely cause of a "damaged" relay is oxidisation because the current through the relay has  been below the minimum operating spec. Installing a HS10 1 K pulldown resistor is likely to fix the issue after a few operations once the oxide is burnt off. This is covered in the qtplasmac docs.

new features go into master branch (2.10) so this will never be in 2.9.4

Get a "reed contact" or "reed relay", make some 3 turns of the clamp wire around it.
That is it, cheap simple and never fails.
I am sure it was in the PlasmaC documentation, no idea if it is in QtPlasmaC.
See attached.