Advanced Search

This might be related
github.com/LinuxCNC/linuxcnc/issues/3486
I have something with spindle-at-speed in HAL, have not looked into it as I just see this now, and need to sleep.... If possible....

Can now confirm that versaprobe has the same issue for me.

Hi, it may be helpful to share your config.txt, hal and ini files so that we may see your setup.

The following error is generated internally, not by the driver not being enabled. Hence maybe a config issue.

I have the magnetic linear encoders (MSR5000) in front of me. Next to the magnetic (10mm width) tape is a steel tape (10mm width), so which standard aluminium profile would you suggest for mounting it?

works now perfect

The Ethercat Master For Linuxcnc is not an executable file. It says We need to patch and Compile based on our application. ! What are the variables that may vary mainly? Not universal at all? (Looking For a traditional 3 Axis Wood router with Dual Y Motor.)

Sir,
New guy here..!
Thanks for those precious lessons.!!!

  The latest Linux version with Realtime kernel is available as a bootable image on the official site right?
Once I install the OS, Can I directly go for Ethercat Configuration?

I am planning to Use EL7 -400W Ethercat Servo Drive from Leadshine with 23Bit magnetic Encoder.
I hope the ESI File of the Servo drive gives me the encoder Counts per revolution????

I set them Up in INI file right?

How does the "LinuxCNC-HAL ----INI----Ethercat

---

Servo" Drive RelationShip Toplology work?

Traditionally ,I write in the "INI" File that , My servo Drive encoder needs 8million/5=1.6million encoder Counts for a millimeter of travel.
(Because My servo Drive encoder needs 8million counts for every revolution.And my ballscrew travels 5mm at full revolution of the servo)

What happens next?
The INI file sends instruction for  1.6 million counts for 1 millimeter on X axis  if I say G0 X1 in Gcode.

There is no such detailed videos on YT  either..!


Thanks.

 

This isn't a linuxcnc-specific question, more of an electrical/wiring question. The CNC router I am retrofitting has a Woods E-Trac X2C AC inverter powering/controlling the spindle. As I'm re-wiring the machine for my Mesa card & LinuxCNC, I'm trying to make sense of the existing wiring.

The machine is (and was previously) powered by single phase 220V (i.e. North American residential standard). The AC inverter/VFD manual states that either single or three phase wiring can be used. The manual states, "incoming power leads L1, L2, and L3 must run through the ground fault CT before being fastened to the terminals... If operating with single-phase power, use line terminals L1 and L2."  However, on my machine, L1 and L2 do not pass through the current transformer. Instead, there is an Ogden Mighty watt resistor (MXEG03A1493, 250Ω, 400V) wired to some undocumented terminals on the inverter (under the cover) and these leads pass through the current transformer. Can anyone speculate on why this might have been done?

Bevor ich das vergesse, der Treiber ist zurück gegangen. Modbus wurde versprochen, aber ist quasi nicht nztzbar. Es wurde etwas in die Firmware des Treiber gebaut, damit konnte man ein wenig lesen und auch etwas schreiben, aber wirklich Modbus ist es nicht. Das was in der Beschreibung versprochen wurde, konnte definitief nicht gehalten werden. Ein anderer Händler hatte dann wenigstens zugegeben, das damit angeblich speed Modus möglich wäre, aber position funktionniert nicht.

same advise as above, follow how the pb launchers are working and do the same thing for your vcp1, they are calling scripts and will require the terminal be in venv mode and the scripts pointing to the correct files.

the existing atc macros are designed for dumb motor carousel operation. if you are using the carousel.comp component, you would need to follow the components setup instructions and integrate into the macros or build new macros based on your machines mechanical configuration. you could use the existing macros as a template for the qml graphics connections.

Thanks for the insight. I'll do some testing outside of pncconf once I get all the stepper drivers installed.

Hi,

Thank you for your time and response. I think the UI polls data from the STATUS data. Probably, if a signal is only high fraction of a second, the UI might not refresh quickly to show that. But I think the underlying logic in HAL is catching all states. 

I just run linuxcnc with debug and verbose output from the terminal, but nothing other than the latch return error is printed to the console during the issue  .

Hello,

Thank you for your efforts, I thought I was the only one.
But I did not pursue this further due to time constraints, especially since no further reactions were made to my post.
The switching states are displayed properly on my mesa card. However, if I quickly press my mesa card in a row, the mesa card reacts correctly, but the LED in QT_DRAGON_HD sometimes does not react as expected.
Possibly a timing problem with signal processing.
I have a flying button that measures both workpiece and tool length. Workpiece height is the built -in routine and tool length and change your own, but that makes no difference.

Many greetings Frank.

What do you have selected to enable the spindle?

Typically you need one output for single direction spindles 
and two for reversible spindles.

On a 7I96S, in hal, these would normally connect to the isolated
outputs on TB3, which in turn need to be wired to appropriate
VFD control pins.