Advanced Search

I installed LinuxCNC onto a RPi 400 with a touchscreen and GMOCCAPY. It works very well, but something has changed on the system and it is now unstable. LinuxCNC, is locking up after periods of inactivity. Running a Mesa 7i96 board. Wonder if doing another clean install will fix it. Might have had a bad update along the way. Will let you know what I discover....

I made:
and files was in:

Copy that just was curious!

Glad to hear you’re getting better results

zz912 wrote:

It looks good BUT the file
~/linuxcnc/configs/sim/gmoccapy/macros/change_g43.ngc
is created after load sim configuration. For example in my computer this file dont exist.

In my RIP installation file is here:
/home/zdenek/linuxcnc/linuxcnc-master/configs/sim/gmoccapy/macros/change_g43.ngc

This scripts must work also in debian instalation.

It is defined here:
github.com/LinuxCNC/linuxcnc/blob/1c72d4...ipts/linuxcnc.in#L53
But I dont know, how to use it.

 

Did you build a package from master and installed it?
I am pretty sure that the change_g43.ngc file should be next to the change.ngc file in the directory because all files from this folder are copied so this one should be copied as well.

"~/linuxcnc/configs/sim.gmoccapy/macros" (or similar)

Having studied the information a bit, I think you are using something like this. This is an interesting method, but it has a number of its own shortcomings. In addition to 7745, there are many more successful chips (for example, ZSSC3123AA2R, MAS6513, PCAP04, or the simplest   cav424 with an external ADC).

I will reveal the details that I found out on my own and were hard to find on the Internet:As for AD7745/AD7746, I tried to use it as a controller for gas burners. It was not easy because it worked on the desk, but during cutting, the gas changed the parameters very much and the AD7745/AD7746 measurement method was not suitable.1. It is not suitable for lasers because the reading is too slow 90Hz.To make sense for Lasers, the absolute minimum sampling is 500Hz (2ms), I have 3650Hz sampling but I do not want/cannot reveal why this value is chosen and it should be selected for a specific type of processing.2. AD7745/AD7746 have a measurement range of 17pF (60pF tollerant), which is definitely too little because the parasitic capacitances on the wire, head, etc. are 50-200pF3. The useful measurement range of the distance is 0.1pF - 30pF, although for some types of nozzles the range may be wider4. I chose the method of measuring the capacitance charging time, although I also experimented with measuring the frequency as in BCL-AMP BCS, which was a bit less stable but also very good.5. Unfortunately, I did not find any ready-made circuit like AD7745/AD7746 that would be suitable, and I had to design everything from scratch. 

Hi everyone,I've started developing an I/O board using the Raspberry Pi Pico. The prototype will feature 8x 24V outputs and 16x 24V inputs, communicating over Ethernet UDP with a real-time HAL driver. If everything works well, I plan to develop additional boards with step generation, analog outputs, and encoder inputs.At the moment, things are still evolving—I'm currently having the first batch of 5 PCBs manufactured and have already ordered the necessary components. Communication between the Pico and the real-time HAL is already working. :)I'll keep you updated as the project progresses!

Thank you for the input!

Just got back to the machine.

Was not sure what value to set maxerror to so i started with 0.001. It did pretty much eliminated all overshoot, but i also feel that the P value has no effect anymore. A P value of 5 or 100 have the same response curve.

I tried milling with P=2 and maxerror=0.001 but still got a rpm drop of about 70 revolutions. Also tried P=5 and got a drop of 130 revolutions!

If i up the feedrate while under load i have the feeling i could easily stall the spindle.

Maybe the vfd is faulty?´

Also anything in the VFD setup that slows response will limit the highest stable P term.

Would reducing or disabling the startup acceleration also count here?

I attached a image of halscope with encoder feedback, speed cmd and pid output. The pid is working and trying to combat the drop, so maybe the spindle gearbox is not dynamic enough to respond quick enough? In the image the difference is not so big but again if i increase the load the difference gets much bigger.