Advanced Search

What aspects of Andy's carousel.comp have you identified as needing improvment, and/or what other features/funtions are you adding with this comp?

Do you have a github repository, or just keeping the current version of code uploaded to the initial post in this thread?

My Schaublin tool changer is extremely simple, with just a single input to open the tool change pneumatic valve, for a fixed duration, and then checking the next feedback pin went high. Cycling through until the target position is reached. I don't need much of the code like tool unlock, tool lock as that is all pneumatically sequenced.

I am not sure what to do about motion to a tool change position. Given the excessive size of my carousel, relative to the lathe envelope, and wide variety of tool geometries, tail stock etc I suspect it is safer to not automatically move to a tool change position. Do you have thoughts on that?
Cheers
Mark

PCW: Thanks for that, I'll consider changing kernel, or maybe trying with another pc.

rodw: processor: Intel(R) Core(TM) i5-8400T CPU @ 1.70GHz, echo $(nproc) prints 5.

pos is of course the number of rotations since zeroing on index. This is the main driver for
the synchronized move, the z-axis is being forced to follow pos.

Rotational speed isn't mandatory, but convenient to have.
You use rotational speed for the at-speed pin and is displayed in the gui.
I guess enc-frequency-scale should be set to 1/2000, so 0.0005, for rps.
For rpm 1/(2000*60) = 8.333333e-6.

Hello,
Is the Forum where discussion of new hal comp takes place?

On Github, on my fork there is a Discussion button
On Github in LinuxCNC.linuxcnc there is no button.
Google said the Forum was the main location for discussion.

Where is proper place to discuss?

My case is
  problems with package creation and a new comp.
 My comp builds and runs fine locally,
but a PR fails during package creation.
I hope a new push will fix the packahe creation error.

I'm not sure on that. pos = position so it implies reading a linear scale when you have a spindle, you want to measure RPM or RPS which a frequency resolves to with appropriate scaling. 

Hi All, 
The ohmic enable gets randomly triggered when laser is enabled. The wiring is as follows to the 7c81 board: 5v from bob , signal to 7c81 encoder pin direct, pins 3 and 4 to gnd of bob. Please help!

doesnt enc-pos provide an accurate speed.

I have these:
www.ti.com/product/LM331
but i never bothered to use them as the time is worth more than the price of THCAD.
Easy to use and can be plugged to parallel port with a single optocoupler.

Yes, inverting and decoupling. 
Wouldn't be surprised if there is a similar isolated SPI component.
Best if the ADC has some kind of free run mode. Otherwise the reading of a value can take too much time.
Was looking for a new value every millisecond, with as many bits of resolution as possible.
Have also used ADS1014 with similar good result.

Some clarifications before this goes sideways:
-COM0/COM1/COM2 are referred to serial ports, be it RS232 o other, usually.
-LPT0/LPT1/LPT2 and sometimes only P0/P1/P2 are referred to parallel ports, usually.
What are you referring to with COMn ?
Serial ports are pretty much useless with LinuxCNC, except for some stuff.
Parallel ports, also known as IEEE 1284, are used for machine control still, are perfectly usable with LinuxCNC, but have limited pulse rate capabilities compared to Mesa board.
Reasonable pulse rate or encoder pulse rate for parallel port would be 10000-20000 PPS, sometimes can go to 50000 PPS with a bit of luck/tweaking the BIOS.
At 3000 RPM, that is 50 RPS, so for a 100PPR encoder ends up 5000 PPS, and for a 1000PPR encoder it is already way to fast for most PC setups, see above.
Now convert that to mm/m, as you gave us no info about drive/gear/reduction.
After all that, yes, you can use a parallel port, yes it will work with encoders (2 max normally per port), and yes, you can lower the speed if you have higher count encoders.
But first, fix the wiring and get rid of interference/bad grounding.

alangibson wrote:

My intention with the TVS was to limit input voltage to 250V.

OK, but you must also add resistors in front of it, or it will blow up the first instance the voltage goes above 250V.
-
Personally, i have a strict policy of doing the voltage divider using 3 resistors, always, saves a lot of headache in case of mishaps or wires shorts or any of plasma wires touching ground or machine.
Example, in case of Hakan's schematics, i would use a 2K7 in the middle of two 50K. The other side of both 50K would go to plasma arc voltage, and the measuring would be done on the 2K7.

hi, I am using a absolute multiturn spindle encoder , it is working but I need to simulate de Z index for G33 and G73
so I define the follow net

net spindle-index-en    and2.2.out => spindle.0.index-enable

but always say spindle-index-en and after some test I found spindle.0.index-enable it is already linked
So I delete may hal and leave just basic things like lcec  etc.. basic to make my ethercat network working 
but any way say the signal is already linked, I made allot names changes and this has the same result   
on ini file I have only a call to this hal file.  
after I comment the net line and run the linuxcnc
On hal show I look for the linked spindle.0.index-enable, and I can toggle  the input spindle.0.index-enable
on bash I look for the variable spindle.0.index-enable
at moment the linuxcnc probe basic stance running, there is not link result.
so mean that input is not linked jet, but after I close the linuxcnc instance and remove the comment the net on hal file I get the same error,
spindle.0.index-enable already liked 
I been using probe basic GUI for lathe. i found that you can simulate the spindle feedback or use the encoder feed back, is this option can declare this spindle input?


as additional comment I have the encoder count working and can calculate the right speed test as  tested whit tachometer and it is really precise , so I can control the spindle position net spindle-index-en    and2.2.out => spindle.0.index-enable


Any advice

Have you tried to use the example configuration?

github.com/scottalford75/Remora-RT1052-c.../remora-rt1052-basic

There is some latching logic in the hal file:

net user-enable-out <= iocontrol.0.user-enable-out => remora.enable
net user-request-enable <= iocontrol.0.user-request-enable => remora.reset
net remora-status <= remora.status => iocontrol.0.emc-enable-in

Thanks for the schematic. I wish I had found this a while ago.

I like how you use isolated and regulated voltage. I need to see if I can find a single component that does that.

> The torch is negative, ground is positive.

Ah right. I forgot that. Is that why U4 is inverted?

I took a stab at dissecting your schematic. This is what I got:

Voltage source
5V: Common 5VDC power source
U1: 1W Isolated DC-DC 9V out; Isolation 1.5k VDC/min
C3: Decoupling
U5: 5V LDO voltage regulator
C3: Decoupling
VCC_ISO: Isolated 5VDC

Input stage
R7,R9: Voltage divider, 38:1 ratio
D1: Limit input to max 5V
R6: Current limiting
U4: Voltage buffer (inverted ?)
R8: ?
R5: Current limiting?
C4: Decoupling?
C5: Decoupling?
U3: ADC with 12C output
R4: Pull-up resistor
R5: Pull-up resistor
C2: Decoupling?

Output stage
U2: I2C isolator; Isolation 2.5-kVrms
C1: Decoupling?
R1: Pull-up resistor
R2: Pull-up resistor

At a first glance, I think you have the wrong GND
connected to  the 7I96S spindle analog SPINDLE- (TB2 pin 22).
It should be the potentiometer GND not the digital input GND.