Advanced Search

I'm kind of stuck I think there are some mistakes in my hal and ini setup.
I wonder if it would make sense to start new but its a relative complex machine an I've also done a lot to the GUI.
I attached my config files maybe some one sees what I can't see at the moment.
If not I'll restart new new

 


these two files are for gui and hand wheel

   


thanks Patrick
 

You may have the wrong forum. This forum deals with the use & installation of Linuxcnc.

I use 4 PICOs RP2040, a total of 16 ADC channels (4 ADC channels
per PICO) where the trigger signal (reference voltage) is connected to GP14. I’ve programmed the Picomite to set a trigger value for a falling edge, which means the trigger should activate when the signal reaches 0.8 V. However, I’m encountering an issue where the output voltages I’m getting are higher than expected—they should be lower or close to 0.8 V. The trigger signal frequency is set at 360 Hz, and the input voltage is a 1.2 V AC sine wave at the same frequency. Currently, the output voltages from all ADC channels are between 0.85 and 0.87 V. When I increase the frequency to 400 Hz, 450 Hz, or 500 Hz, the output voltages rise even higher, which is confusing. Could you please help me identify where I might be making a mistake?
I aim to capture the input signal precisely at the point where it crosses the trigger voltage of 0.8 V on a falling edge. To achieve this, I set the offset to zero (minimum). I connected an oscilloscope in DC coupling mode on the input side to monitor the amplitude and frequency of the input voltage. Since the trigger is set for the falling edge, which means the system should capture the signal as it transitions from rising to falling and reaches the trigger level, I expect the captured voltage to be less than 0.8 V.
Kind regardsHasham

Yuhp I found it -_- Sorry guys

Thanks mate I am an stupid

Thanks Ill have a look. hopefully this is the case I have a habit of not finding things right in front of me

Hi Scott
Thanks!
I'm stupid,
it was the classic solution that you have in front of your eyes and you don't see.

The output must be enabled, of course, and the scale must also be set, of course,
but I didn't think of it, even though I had done the same thing for the FR4000
I'm speechless....

Everything works, I'd say the driver is ok

Thanks again for your time!

Thanks for the reply.
I was wondering, after having obtained the map of the points, I thought of inserting them in a linuxcnc compensation file.
But the compensation file compensates errors related only to the axis involved and not to axes in mechanical relation between them, for example z with respect to y.
I thought of actually verifying the geometric displacement of y, in relation to the advancement of z and of relating them with trigonometry.
the result of the offset that varies in real time as Z moves, insert it with an offset component to the command position of the Y drives. It should work if the points taken are precise.

The keyboard is generally comfortable, only the spacebar button is fuzzy, you have to press it only in the middle. The track ball is unfamiliar to me, but it works well. I don't think it will be used often, the touch screen and keyboard covers 99% of all requests.

I don't have to use gmoccapy, the reason I use gmoccapy is because it automatically reads the g-code file when it first starts and has a file refresh button. I can use another graphical user interface. I have a file whose name doesn't change, for example CutDocument.ngc, but its content does.
I don't want the operator to select the g code file every time. Because the g code file is sent to linuxcnc over the network without changing its name.

I think you are Chinese. If you are, add me on QQ and I will help you solve it.  QQ:304394405

There is a Linuxcnc post in F360. It may be called EMC. I never had to modify anything.

It seems very similar to the Rtelligent ECT1616 which was very easy to work out with a generic driver like I did here.
github.com/rodw-au/linuxcnc-cia402/blob/...hercat-conf.xml#L158

It has some PWM functions as well.

Large horizontal mills with a quill will drive you crazy. The only way that I know of for correction is to use a laser scanner and develop a point cloud of X Y and Z. Starting with X0 Y0 Z0 to max travel in a grid. Then develop an error table based on measured and commanded. Remember that lights shining on the machine and room temp will cause drift. The weight of the tool will cause error. After you develop an error comp table, you can then correct the errors in the program in advance. Each axis has pitch yaw and roll, so a simple comp on Y to Z probably will not fix your problem. This is why we don't have horizontal Jig Bores.

www.faro.com/en/Resource-Library/Webinar...g-Processes-on-Track

You could try API for volumetric compensation, they can help. apimetrology.com/machine-tool-calibration/

Okay, a quick look through the code and a look at the ESI file for the EasyIO doesn't show anything *glaringly* wrong. On the other hand, I don't know if anyone has actually tried using this driver before, so 3 of 4 isn't too bad...

One quick question: did you set aout-1-enable?

What are the various aout-1-* pins set to?

Leadshine has an amazing ability to put out products with multiple names and not document them clearly (at least in English) for months after they start slipping into the channel. So I'm not sure exactly what a EM32DX-E4 is. I can find pictures, and a manual in Chinese (oss.leisai.com/uploadfiles/EM32DX-E4%20%...%8B%E5%86%8CV3_1.pdf) that I *think* says that it's a 16-port in, 16-port out digital I/O board with something somewhat odd about the first 8 digital inputs and 4 digital outputs

Ignoring the "something somewhat odd" part, it looks pretty straightforward, 16 ins packed together at 0x6000 and 16 outs at 0x7000. It'd be pretty straightforward to modify one of the other packed digital I/O board drivers to support this hardware.

github.com/linuxcnc-ethercat/linuxcnc-ethercat/issues/434