Advanced Search

Got the new version, built and tested. This one works as well, no big difference from the previous version.
Maybe the linearity is a bit better, it goes to zero Volt now when there is no voltage.
 

View from initial test.
 

I just upgraded from a 2019 version of PlasmaC to the current QTplasmaC on a new SSD. I now am having massive issues with latency/jitter. I’m running a BRIX mini pc that’s sporting a J1900. In the past it was fine but now it wont even run. I went into the bios and disabled everything like I did in the past and disabled Wifi. I think befor my max jitter was like 20k but now the max jitter is Max Jitter (ns) 129316 / 106580

Am I just out of options with this older mini pc? Is it time to look for a more powerful cpu mini PC? 

thanks for all your help. 

For your coolant flood, you would use the "toggle2nist" component.
It has 4 hal pins:
toggle2nist.N.in Would connect to the output signal from your button input.
toggle2nist.N.is-on Would connect to the output signal from the hal pin "halui.flood.is-on".
toggle2nist.N.on Would connect to the input signal to the hal pin "halui.flood.on".
toggle2nist.N.off Would connect to the input signal to the hal pin "halui.flood.off".

There is not any pre defined pins designated for lube or spindle release. You must build your own logic to handle these functions.

Often machine integrators will set up custom M-codes (M100-199) that turn the required hal pins on or off. Then implement special logic (Hal or PLC) to prevent or enable the states as necessary. Such as preventing the tool from being released if the spindle is running.

The issue is that the disk is not listed there.
Motherboard is MSI. I will try something else later today, but does not look promising.

I would consider integrating a drive using RS485 a more advanced subject.

Start with reading the Linuxcnc documentation, and begin with a basic configuration for running your machine without spindle control. Then after you have a better handle on Linuxcnc, and the basics of Hal programming, try to integrate the modbus spindle control into your configuration. There may be an existing modbus driver compatible with your drive. (I don't know, never used one.) If so that would probably make integrating RS485 control much simpler. But if not you can always make the generic Mb2hal driver work, but this is a bit of a chore to set up and configure. (I have done this before.) The generic RS485 drivers are a lot of work to set up because you must research all of your drive's modbus settings and communication parameters, and every drive (even different models from the same manufacturer can) have different parameter arrangement, there is no "standard" way drives do modbus.

If you are following steps which I have desribed somewhere here at the forum... It has to working properly every time on startup.. I am running profibus, profinet and canopen on single koppler in same time over ethercat

After koppler restart have a look at command -

sudo systemctl restart ethercat.service

... But U are decribing other type of problem... I am currently working on C# console app which will generate us configuration from ethercat slaves && ethercat pdos commands ... I have beta version but it is not too adult to outcome on public... Do U have a TC3 project?