Advanced Search

Zig wrote:

I would need to design an interface card which would live between a mesa 5i20 card and the three servo amps.
.

You might be able to point-to-point wire. I am currently hooking-up my Mesa card to with these connectors as they give a lot more flexibility in what signals go where than the ribbon connectors:
uk.rs-online.com/web/search/searchBrowse...etProduct&R=681-2865
They fit nicely side-by-side in the Mesa headers.

Chris,

I would be happy to set up my machine to try out the stepper with encoders combination.


I am using CNCteknix servo amps which run with step /direction inputs and the encoder is connected directly into the servo amps. In essence the servo amps are a PID controller which drives a BLDC motor.

I would need to design an interface card which would live between a mesa 5i20 card and the three servo amps.

The servo amps have the following 10 pin interface

Pin Label Description
1 RX Input – Serial (5V logic) RX connection for the tuning software.
2 TX Output - Serial (5V logic) TX connection for the tuning software.
3 STEP Input – The rising edge of the step input commands a single encoder step rotation in the direction selected by DIR.
4 DIR Input – A logic high selects a clockwise step and logic low a counter clockwise step.
5 ChA Output – Re-transmission of the encoder Channel A signal to the controller.
6 ENABLE Input – Logic high enables the driver to control the servo motor. Logic low stops all output to the servo motor.
7 ChB Output – Re-transmission of the encoder Channel B signal to the controller.
8 RUN Output – Logic high output indicating the drive is running correctly. If the drive is ENABLE and an error occurs the RUN output will indicate logic low.
9/10 GND Logic ground connection.

I would need to know which connectors on the mesa come into play ( I think this info will be availble in the output from the pncconf utility)in order to design the card.

Additionally the encoders generate homing index pulses the Index pulse is one quadrature resolution wide in duration.

The index pulses are available to me in differential mode so the interface card will also carry receiver electronics along with pulse stretchers to allow correct homing sequence.

Chris, rather than waiting for 2.5 to come out etc if You generate the files, I can then get on with the hardware and trials.

For me this means a quick changeover from working configuration to an experimental one and vice versa.

the development version of pncconf allows steppers with encoders. Not that I can test the feature.(I have no steppers with encoders)
I'm just not sure if the newest pncconf will make it into EMC 2.5, I am behind in stabilizing it....

Hear... hear...

( meaning uncontrolled expressions of rapture and joy at the thought that steppers and encodrs will make a baby)

Are you wanting to add ngcgui or just get tabs for pyvcp?

What version of EMC are you running?

John

what file do i need to edit to be able to get tabs? it's been about 2 or 3 years, i ask someone and they say
go read this or that. i do, but NOTHING i've ever seen told me WHICH file/program to edit. time later and i ask
again, so i try to read what the told me. again again no mention of which to start with. i would appreciate
ANY help, even if you tell me to go read this or that. i would try again. Thanks for any help

Thanks Rus. I have inserted that in my HAL. Didn't get a chance to test it tonight, as the computor is inside hanging on the lan cable.

Thanks for sharing that Rick. I did a quick search and found where the "custom" tab was added but not how to add it.

John

glad to meet you. now I'm studying the interpreter. well, a rough job~

I'm here but I know nothing about the interpreter...

John

I recently added the ngcgui to another machine by editing the existing config files.
Everything went smooth but I no longer had the "custom" tab in Axis.
I looked for the difference and found that I needed to add...

NGCGUI_SUBFILE = ""

in my list of subfiles in my ini file.
Probably in the docs but I missed it, now all is well.

Rick G

hey,hey!! I made a big big mistake. I got down to reading the file, and found what I really want ,hah hah~

Attached is my complete hal file. FWIW I never used turboCNC so I'm not sure what the connection with 1 signal per rev is. Anyway my sensor is working dandy. Let me know if you have any other questions. I'm using a slightly older rev of EMC2 but don't think it matters. Rus

Here's the section:
addf stepgen.capture-position servo-thread
addf encoder.capture-position servo-thread
addf motion-command-handler servo-thread
addf motion-controller servo-thread
addf stepgen.update-freq servo-thread
addf abs.0 servo-thread
addf scale.0 servo-thread
net spindle-cmd <= motion.spindle-speed-out

setp encoder.0.position-scale 1.000000
setp encoder.0.counter-mode 1
net spindle-position encoder.0.position-interpolated => motion.spindle-revs
net spindle-velocity encoder.0.velocity => motion.spindle-speed-in
net spindle-index-enable encoder.0.index-enable <=> motion.spindle-index-enable
net spindle-phase-a encoder.0.phase-A
net spindle-phase-a encoder.0.phase-Z
...
net spindle-phase-a <= parport.0.pin-15-in

I want to ask if I can find some meterials about how the interpreter works?

since now I only get the RS274/NGC_3.pdf, but this only told me the input & output result of the interpreter, not how the interperter interpret the G code, can anyone help me?

and I also notice that some of the files in the source code, saicanon.cc/rs274ngc.cc, for example, do the interpreting job.
but if there are docs about the interpretation, things may be much better~

Wow, it writes backwards!

Cool.

John