Advanced Search

As a start, I would set the encoder scale so the position is approximately correct.
You will likely need to add an offset component to zero the position as well.

Maybe you can modify the probe screen source to use CSS and then reduce the margins with CSS.
That's how I made Gmoccapy fit into the old sizes when migrating from Gtk 2 to Gtk 3...

Thank you, it solved the problem, the screen is showing the correct display.

 

But when I try to start the machine, the message "error calculating movement on axis 1" appears. I tried to change the max_limit and min_limit values ​​in the INI file, but without success.

When this error message appears, is it possible to see in more detail which configuration is still wrong?

Do you have any tips or examples of how I should configure axis 1 so that the error does not appear?

Below are the HAL and INI files for your consideration.

   
 

You cannot run that command when LinuxCNC is running
or when it exited on a major error, because linuxCNC
blocks access to the Ethernet port it is using when it is running.

LinuxCNC restores access when it exits normally

 

Thanks for the suggestion of the command below:

mesaflash --device 7i96s --addr 10.10.10.10 --dbname3 7i77 --readhmid

It's a great option to debug any problems. But unfortunately in my case it wasn't allowed, the error below appeared:

lbp16_access.send_packet: Operation not permitted
Aborted

Do I have to assign a name or register it in the system so that readhmid works through the name? If so, do you have an example?

Try this:

# ---Encoder feedback signals/setup---

#setp hm2_7i96s.0.encoder.00.counter-mode 0 #Default PNCConf Wizard
setp hm2_7i96s.0.encoder.00.counter-mode 1 #change to accept signal from THCAD2 board as Z axis feedback
#setp hm2_7i96s.0.encoder.00.filter 1 #Default PNCConf Wizard
setp hm2_7i96s.0.encoder.00.filter 0
setp hm2_7i96s.0.encoder.00.index-invert 0
setp hm2_7i96s.0.encoder.00.index-mask 0
setp hm2_7i96s.0.encoder.00.index-mask-invert 0
setp hm2_7i96s.0.encoder.00.scale [JOINT_1]ENCODER_SCALE

net z-pos-fb <= hm2_7i96s.0.encoder.00.velocity

#net z-vel-fb <= hm2_7i96s.0.encoder.00.velocity
net z-pos-fb => joint.1.motor-pos-fb
net z-index-enable joint.1.index-enable <=> hm2_7i96s.0.encoder.00.index-enable
net z-pos-rawcounts <= hm2_7i96s.0.encoder.00.rawcounts

Good afternoon, dear friends.

Please, how should I make the connections in the HAL file so that the 7i77 electronic board accepts the frequency generated by the THCAD2 electronic board as feedback from the Z axis?

Below is the basic code generated by PNCConf from LinuxCNC:

Note:

The TCHAD2 electronic board receives the analog voltage from the Z-axis movement which is a magnetic sensor with repeatability accuracy of 10µm (MICRA, micron or micron), with a recordable speed of 10m/s (meters per second) and IP67 classification (dust protection and water and oil resistance).
This sensor provides 0 volts at the output when the Z axis is lowered and 8 volts at the output when the Z axis is raised. The TCHAD2 electronic board converts this voltage into a frequency of 100kHz to 1Mhz (according to the chosen jumper). Then the 7i77 electronic board receives this frequency on encoder channel 0. It displays the position results counting to infinity, with only velocity being usable as position, with the low Z axis having a low frequency and the high Z axis having a high frequency.
Please, any basic example helps or suggestions. I appreciate your collaboration. Attached is a video showing how the values ​​from the TCHAD2 electronic board are being received by LinuxCNC.

*MICRA: The symbol (µm) and correspond to the microscopic unit of measurement, where 1 micron is the same as dividing 1 millimeter by 1000


 

Hello @cornholio:

I hear you. "AI" is a tool. One can try it out as is their desire, but that's getting harder to do given that it seems it's being forced down our throats sometimes. But, that's a problem not solved in this one post.

So, does the gyroscope created by the rotor in the router "cause issues" because the earth is rotating and orbiting about, and by the fact we have gravity or, am I mistaken? Either way I have never investigated gyroscopes beyond crashing some (model) helicopters. They seem to cause confusion (maybe just for me), but after a while that's not an excuse not to learn about them.

I also need to read and understand "background" material I may post, like the citation about "kinematics".

Many thanks,
Tom

Can you post the ini and hal files.

Here's the pinout of the input pins on my PMDX-122 breakout board.

Pin 10: E-Stop to PC (Internal, Works great)
Pin 11: Home X and X-axis minimum limit
Pin 12: Home Y and Y-axis minimum limit
Pin 13: Z-axis minimum limit
Pin 15: Maximum limit for all axes.

I know all switches work fine )

My machine is set up so "Home" means the tool is at the bottom-left corner of the table. (Y axis.)

Note, you can get a better idea of sserial channel --> 7I77 assignments with:

mesaflash --device 7i96s --addr 10.10.10.10 --dbname3 7i77 --readhmid

I have a separate home switch for each axis.

Each home switch has its own wire leading to the beakout board.

Each home switch is also the minumum limit switch.

I also have maximum limit switches that are all wired in parallel.

This error appeared when I took the data generated by PNCConf to try to include part of it in the programming code of the machine that I am already developing. But while I was waiting for your answer, I had the idea of ​​creating a new file through the basic PNCConf and gradually including the code of the machine under development. In this code, it is accepting the "analogout scalemax". I will leave it attached in case anyone needs a basic initial code for 7i96s with 7i77. I will try this method. Thank you for your attention, Mr. PCW.

 

Look, like you have the channel number wrong for the analog 7I77 section
(its channel 1 not 0)
 

Yes, you need the appropriate D connector for CN1