Advanced Search

Thank you Master PCW
I used (pncconf) to get some sample code to apply to the project. The code looked like this:

 

The frequency reading is appearing on the panel, but when trying to move it, this Z-axis movement calculation error appears:

 

Please, how should I proceed? What alternative and configuration for this?

 

-
Santa came early this year, also brought a Zoyi ZT-703S osciloscope!

Ok, was ist denn ein CAM ? ist das ein Programm?

Gcode für Tangentialmesser wird meist vom CAM generiert. Die XYZC Werte müssen für eine Kurve simultan abgefahren werden, dazu muss das CAM für jeden Wegpunkt auf der Kurve den Tangentialwinkel berechnen und als C-Achsenwert ausgeben.

hello everyone,I have just received my 7i96s board, the 5 axes work correctly with my RPI 4 . but I would like to work with an XYZBC trt configuration . The construction is easy with the configurations already proposed in stepconf . but I have no idea how to convert /establish the same configuration with Pncconf which is MESA oriented but without predefined configuration. Could someone please help me?Thank you

Thank you, Master PCW
In the factory, the Z axis is driven by the 7i77 board connected to 7i96s.

It works with a positive voltage of 10 V, the punch goes up, and with a negative voltage of 10 V, it goes down.

I am in my laboratory, hundreds of kilometers away from the factory. Unfortunately, I do not yet have two 7i77s to do all the simulations here. But I do have two 7i96s to do the simulations here in the laboratory, while the other one has already been installed on the customer's machine. However, before I travel again, I need to have the programming ready to apply it to the machine.

I have been working on this for a long time. You advised me to use THCAD2 to receive the signal from the magnetic ruler.

The big challenge with this machine is that the Z axis is a hydraulic cylinder that hits the punch and pierces the metal sheet, but this movement has to be done with millimeter precision. If it exceeds the limit, it pulls and deforms the metal sheet. I think your idea of ​​using THCAD2 is great, because it has some similarities in the way the machine works, because the purpose of THCAD2 is to control the height of the plasma torch and in my case it is to control how far the punch can reach the metal sheet. However, I am new and inexperienced in configuring Hal to connect this and the LinuxCNC system understands that the speed of the frequency is the displacement of the Z axis, for example at 100KHZ the cylinder advanced all the way and at 1MHZ the cylinder returned all the way. Because the future interest is that with the G code, I can determine the depth that can reach the metal sheet. I will check your recommendations, but if you can give me some examples, I would be very grateful.

Das mit dem (G64 weglassen) habe ich noch nicht ausprobiert Ich hoffe, dass ich morgen Abend wieder an die Anlage komme.
Bis dahin habe ich mich ein wenig durch die Dokumentation gewühlt und bin auf den Punkt "5.2. Center Format Example" gestoßen.

Allerdings habe ich nicht wirklich verstanden, was ich da genau eintragen soll.
Oder habt ihr eine andere Idee, die ich ausprobieren könnte, so dass die Bewegung hämonischer aussieht und von Staaten ausgeht.
(Momentan kann die C-Achse noch mehr als 180° drehen, außer einem Laserpointer ist noch nichts angeschlossen. Im Moment sind es nur ein paar Tests, die ich mal zeigen kann).

auf dem Bild sind die Werte der ersten zwei Linien zu sehen.
 
 

Need to know all the version info, what Debian, what linuxcnc etc

At least i uninstalled Probe Basic and reinstalled it over this documentation.
kcjengr.github.io/probe_basic/stable_develop_branch_change.html

I use the second window frequently for moving files around without needing to exit full screen.

That said, If you guys find it important enough to put the time in to make the updates to the ui functionality and want to submit a pull request I will gladly review and accept into the main branch.

For me I have a list of more pressing items that I have on my plate that I need to carve out and allocate time for. But don't be shy to submit pull requests for features that make it better and more universally useful, the more folks puttig time in the more gets done! And it's appreciated!

Thanks guys,

Chris

You would use the encoder velocity as the joint feedback source for the joint used for the Z Axis

Basically, if you make a configuration (using pncconf or MesaCT) with Z being a
normal step/dir axis, you would replace the feedback coming from the stepgen
with the encoder velocity. What drives the Z axis?

Note that you need to scale the encoder velocity so it reads in machine units.
In addition, you will likely need to offset the reading
(perhaps using the scale or offset components)

The encoder scale will probably be a large negative
number, I can give you the math for this later. just stepping out
the door...

How are you installing?

Dies the sim show correctly?

Linux docs for hal things, probe basic docs for the rest