Advanced Search

Thanks for the information. One of the issues I'm running into is something to do with needing an "enable" signal or something. Still working through that.

I did the latency test. It came out around 150 nanoseconds if I remember correctly.

PCW wrote:

I would think a direct frequency output would be desirable as its readable
in real time by many different types of interface hardware.

Thanks Peter. What would be a good maximum frequency to work with? You will know a lot more than I do

I made my own version of the CIA402 and custom home components for the A6 servo and put it on github -> github.com/CollinBardini/linuxcnc-a6-servo
The custom home component writes to a signal called "start-cia-homing" (from Rod's implementation), which kicks off homing in the CIA402 components. The CIA402 component then handles starting homing by writing to controlword and operation mode. While the servo is homing, the home component monitors the statusword until homing is complete.
I made it as barebones as possible to help others get started. I will write a README when I get time. For now, Rod's README is a good starting point.

hello, for some reason delta put a sticker on for their high frequency drive VFD-H, i removed the sticker and it was actually a B drive VFD-B and i checked the manual it does support modbus,

JT wrote:

I deleted my post because I had the nic set to 10.10.10.10 and the ping times were quite wrong.

JT

That is what i was pointing out when the post disappeared on me!

..

  The sensor controls the flow of current through the wire, a simple electronic circuit that operates over a wide range of voltages and gives a low state at the output when the current flow disappears. See diagram.The connectors on the left side 1 and J1 are connected to the wire and the connectors 1 and J2 on the right side are the output.

Thank you for the explanation, in the morning I checked with a friend on the milling machine and he has similar solutions, now I know that it is ok

I deleted my post because I had the nic set to 10.10.10.10 and the ping times were quite wrong.

JT

Die Konstruktion ist halt sehr nichtlinear da werden natürlich Schwenkachsenwinkel und die Position der Kugeltriebspindel auch nie in einem linearen Verhältnis zueinander verlaufen.
Wenn dir der open loop Betrieb nicht präzise genug ist dann könntest du eventuell die Encoderposition in einer hal-Komponente in die Motorposition des Kugeltriebes umrechnen und dann mit einem PID korrigieren.
Wie realistisch das in einer Regelschlaufe ist kann ich aber mangels Erfahrung nicht beurteilen.

Hello,
it seems you have not the folder to move.
Mybe you are in the wrong place.

If you list the folder by typing ls command, can you see the NativeCam folder listed?

If you aren't trying to get a gantry going don't look at what I've posted, it will only set you back.

It is in the hal file I attached in a previous message. Search for probe1rising. Please note that this is a work in progress (or lack there of for a couple of weeks). I just wanted to show my hack to get a gantry going. Download all the files and search them. Be aware of the LinuxCNC underscore dash translation that occurs between various files. That's why my naming is poorly readable.

Why do i get that it cant find "cia402.0.probe1rising". Where does these pins get added? And in what directory should i have the .comp file?
 

Tanks for the tip. It helped!
In the meanwhile I chnged to Probe Basic and got it to wook.
Tool measuremt and probing works now.