Advanced Search

@fully_defined
I'm sorry but I have grown tired of your antics. You have already been asked to leave once before and as you have stated ad nauseam that this forum has not been able to meet your expectations I would like to invite you again to find other places to seek whatever you are looking for.

thanks same error message with the modification

There are no normal encoders on TB3
(there are 4 MPG encoders but these are not suitable
for measuring frequency)

It would require different firmware to put standard
encoders on TB3 (7i96s_p1encd has 1 encoder on TB2 and
6 more on P1)

Your mesaflash command may have failed because either you have LinuxCNC running
or LinuxCNC did not exit cleanly. LinuxCNC blocks access to the Ethernet port it uses
when running.

The .pin file just a human readable file that  describes the firmware contents and
pin connections. Its made by running mesaflash's --readhmid command.

To make new firmware, one changes the PINXXXX.vhd file and re-compiles
the firmware source using the software toolchain for the particular FPGA.
 

You would connect the joint.n.motor-pos-cmd to the controlling
hardware (PWMgen etc)

You would need to loop back joint.n.motor-pos-cmd to
joint.n.motor-pos-fb

You may also need the scale component unless the controlling
hardware has offset and scale parameters.

PCW wrote:

The number of available encoders depends on the firmware and pin/FPGA size limitations.The 7i96s_p1encd firmware has 7 encoders: 0..6. They are all basically identical(except encoder 6 has no index input pin due to lack of pins)Here are all the encoder 4 pins and parameters (using 7i96s_p1encd firmware): 

  
 

 

That's good news.
I'm a little confused with the 7196s pin assignments associated with the encoders. Ideally there would be 4 encoders assigned to the P1 expansion port and 2 to the TB3 inputs. The two on the TB3, don't actually have to be quadrature inputs, because those two will simple be driven with a simple square wave .IIRC 7i96s pin assignment can be tweaked by editing 7i96s_p1encd.pin?

Can I simply edit that file, and if so how would I assign the last two encoders to TB3 pins?

I thought I could get the latest pin assignment with: 
mesaflash --device 7I96s --addr 10.10.10.10 --readhmid

However I get and error (see attached) when I try that.
 

Yes I am referring normal rc servo with 180 degree of motion.
How can I assign these servos axis. So that I can control like nomal axis movement and i can use genserkins

Do you mean the normal limited motion range RC servos?

They should works with direct joint position commands
(with appropriate offsets,  and scales), like any position mode
actuator.

How can i use Rcservo as axis? I want to drive 6dof robotic arm which has 8 steppers. One for each joint except 2 for shoulder and one for gripper. I have seen example of driving rcservo using pwmgen. That can drive servos, but I want know how to use these servos as axis.
Any help will be highly appreciated.

Hello LinuxCNC Forum,I hope I categorized this topic correctly. I have been using LinuxCNC for my mini lathe for six years, and it is working great. Recently, I came into contact with commercial CNC controls (Heidenhain and Siemens) while writing my thesis at the university. Some of them have a great user experience and good ergonomics. My goal is to build my own HMI based on Gmoccapy that is easy to use and ergonomic.But now the question has arisen: what makes an HMI really good, and are touch controls really the way to go? Which functions should have their dedicated hardware button, and which ones should be accessible via softkeys? The overall size of the display is also a topic where I am not sure.I hope that your additional inputs help me to create a usable HMI.

PCW-
As I mentioned, I have a Mesa 7i92. Is there a hardware encoder that's compatible with this that you'd recommend? I don't have quardrature, just an index and A signal.

Your current encoder should be fine but you need to use firmware that has a hardware encoder
and wire the (5V!) encoder signals to the 7I92 encoder inputs.

Actually, that is not such an easy question to answer.

1. Traditionally it would be the developers mailing list:
sourceforge.net/p/emc/mailman/emc-developers/

(Although it seems the number of people actively participating in discussions has dwindled drastically in the last couple of years.)

2. If you already have a proposed change then a pull request on github is the best way to get noticed.

3. Posting questions on the forum will certainly give you exposure to a sizable number of readers but how many of those would be aware of the whole picture I cannot say. Still worth a try though.

[edit]
Seems to me that this could maybe be handled in a custom kinematic component.