Advanced Search

No one has asked for a specific facility for manual tool setting, which would start with specific procedure. There are a few common tool length strategies.

'Touch Z' usually implies _coordinate_ touch off which QtDragon has buttons for (REF and ZERO).
For tool setting, you can of course manually change the offsets in the tool offset page but also when you are on the tool offset page, the 'HOME' buttons change to 'TOOL' buttons.
Pressing that button will give you several options for setting the tool offset.

If you have errors with a base period (not frequency) of 100000 reducing it will not fix it, it will only make the issue worse.

What you will need to do is run a latency test and see how things are going.
The first error that shows in your picture is a latency error, that need addressing first, you will need to set a very high base period and slowly work backwards.

A base period of 500 would yield a base frequency of about 2Mhz, a 250000 base period would yield a base frequency of 40kHz. The larger the base period the slower the base frequency.

If you were getting errors at at base period of 100000 i would double this to see how things are, you may reach a stage where the base period is so high that the machine may not be usable with the hardware\OS combo.

At some stage you may have to get access to the BIOS.

Be aware that when timings are talked about they are in nano seconds, it does make things easier if that convention is kept.

Hi,

Has anyone done a plasma interface with Flex GUI?

Just a short reply to end the thread.

At the end of the day I used external-offsets and it worked like a charm. No g-code has to run at all in my current setup.
linuxcnc.org/docs/html/motion/external-offsets.html

It's very similar to the jog-counts/jog-scale approach that was suggested here too, but I wasn't sure whether I would be able to control acceleration in that case. So I started with external-offsets and that was enough.

Thanks everyone for the advice!

And the slotted disk can sometimes rust.

I am 100% convinced it's a software issue. I was able to create a basic application using the Modbus library, using the same basic logic as the hy_gt_vfd hal driver, and it works. Meaning no communication error, and I can start and stop the spindle fine. So that along with the mbpoll that also works, it's in the hy_gt_vhf hal module.

I think that there is a memory allocation that stepping over the modbus context (where the port settings are)?
 

From what I can tell it looks like it is attached in Hal?

Hi langdons! Thanks for your question!
Yes the VFD has more than one output. One +24V for maybe switches or relays, two relay outputs and one +10v output that puts voltage to the electronic potentiometer on the 7i76e. The mesa doesn't have such a voltage output on board, so you have to give that from an external source (eg the VFD 10V out) to the spindle+ input. The spindle-output then gives the 0-10V voltage correspondingly to the set rpms back to the VFD's analog input and, if the FWD signal is on, the spindle turns.
In my case, the rpm output voltage AND the spindle.enable = spindle.on signal is only given out from LCNC if I do this from a file. Normally - and any time before, this works even with any MDI speed command.

So - the VFD (now) works as it should but LCNC has problems to give the right MDI Commands as ordered to the outputs of the MESA card.
The VFD had no +10V on its H output as it came to me, from the dealer, new product, no NOS, freshly produced 3 years ago. I wasn't ready to build that thing in because I was busy with the mechanic part of my CNC. I put some parameters in the first weeks, but no real testing with any controller, so I didn't mention that problem. I found that few weeks ago, as I installed the VFD and tried to get the spindle turning. And found that there is no +10V at Out H. Then, the external 10V source, but I wanted the VFD beeing allright, so I sent it to Hitachi for Service.

I wasn't able to go down to my machine the last days, but I will make a video of that process the next days.

Kind regards!

Hello atrex77,
this is a very nice project. I found this video , it looks fantastic.
A very fast LinuxCNC-Board for low cost.

You made a very good job, but is it useful in practice?
I think there are not enough input and output free.
In my opinion you need for a machine:
- for each axis 2 inputs (one side switch for reference and limit together, other side only limit)
- one input and one output for e-stop
- one output for enable the spindle additional to the PWM
- one output for the coolant
- if you have a machine enclosure, you need one input for the switch and one for enable the drives.

What do you think about this? Do you use it in an other way?
Do you already have a solution in your mind?

One thing about optical encoders, they really don't appreciate contamination. If oil or coolant get into them, it will generally really screw them up. Even if none of the electronics with are hurt, a little dirt in the wrong spot or on the wheel can be very bad. Also when they get really old sometimes the LED source can get weak or fail.

Latency is not really an issue with Modbus as it's not real time to begin with...

andypugh wrote:

M62 and friends need connections in HAL to have any effect. Do these connections exist? (motion.digital-out-NN etc)
 

Im not sure they do right now

This seems to be ocuring for other people too like this thread.
www.forum.linuxcnc.org/plasmac/42445-hel...s-qtplasmac?start=10
The feed reduction commands in gcode were not working for them but it never got solved. Other than using the post to generate the small hole fix.

So it was a busy week, but here is the list of keys that I modified to get the spindle running.  Some of the values are specific to the spindle itself.  My spindle is 2.2kw air cooled, so my max rpm is 24000 and the minimum rpm is 12000.  also my pwm range is from about 5v to around 9.6, so i adjusted the values is the 5 section to make my max voltage equal 24000 rpm. the values in the parenthesis are the values that i used, but will vary depending on your spindle

P00.01 - 1
P00.03 - [MAX OUTPUT FREQUENCY] (400)
P00.04 - [MAX RUNNING FREQUENCY] (400)
P00.05 - [MIN RUNNING FREQUENCY] (200)
P00.06 - 2 [ANALOG INPUT 2]
P00.07 - 1
P00.10 - 60 
P00.11 - 6 (seconds to accelerate)
P00.12 - 6 (seconds to decelerate)
P00.14 - 4.0 (2.2 KW)

P02.01 - [MOTOR RATED POWER] (2.2)
P02.02 - [MOTOR FREQUENCY] (400)
P02.03  - [MAX RPM] (24000)
P02.04 - [MOTOR VOLTAGE] (220)
P03.05 - [MOTOR RATED AMPS] (6)

with this section, anything under 5v will also give me 50% power, so the spindle can never run less than 12k rpm.  just to be on the safe side, i also set the AI2 settings to the same values (37-40)
P05.32 - 5.00
P05.33 - 50.00
P05.34 - 9.6
P05.35 - 100.0
P05.37 - 5.00
P05.38 - 50.00
P05.39 - 9.6
P05.40 - 100.0

This allows me to use the stop key to override the spindle in case of emergency
P07.04 - 3 
 

Thanks for the help. It wasnt in the accessories submenu. So I did a full reinstall and now it works perfectly fine. Just gotta learn how to set it all up. Thanks a lot for the help