Advanced Search

I haven't looked but I am fairly sure the the software supports mcode with decimal places ? M7.0 or m7.1  etc and so on. 

the current coolant/cutting fluid controls are way to limited and require to much special handling. It would make sense to update the current scheme with mcode that could be numbers 

M7.1 air blast
M7.2 mist
M7.3 flood
M7.4 through tool 

etc and so forth. I can modify the existing post processor but where exactly would this change have to be made in the core of the linuxcnc software base ? Also the existing mcodes for coolant can be left standing. I am just trying to avoid creating custom mcodes for controlling the various cooling systems I am adding to my machines, but many NEWER cnc machines also have many varying types of coolant schemes. 

Hi JT. have found an issue with the CT.

using 7i97T. My first joint is fine but subsequent joints do not have the scale referenced correctly within hal txt file.

in the below snip I believe this should say Joint 1

 

That is great thanks mate. Makes sense to me now. Not sure how to tag people in these posts but I'll try inform JT of the issue.

or set feed override to 200 %..then the feedrate setting could be nominal and adaptive would be .5 for nominal feedrate (I think)

If you don't go with expensive absolute encoders make sure you get glass or magnetic encoders with index signals for accurate homing. It doesn't look like a quick homing operation at power up would be a problem with your machine.

Also pay a lot of attention to how you will install and adjust. You need to install/adjust colinear with the axis movement. On my lathe, I found machined surface for X that works great with magnetic.

I use mesa boards with glass and magnetic encoders with index signals. I enable the quadrature error detection. I needed to update mesa firmware and add a connection or two to get the Stepgens to reset on the encoder index. That was quite a while ago, not sure if config index default is automatically correct.

If encoder 2 is assigned to joint 2, then yes, that should be [JOINT_2]

I am being a bit vague because there is no fixed mapping between
hardware=encoder/PWM/stepgen etc and joints. 

Hi PCW.

I believe I have found an error in the mesaCT's hal file... but I could be wrong (I have just been comparing axis and trying to figure out how these files work)

Can you confirm that the highlighted joint reference is wrong  

This is X Axis, joint 00
 

And this is Z Axis, joint 02. Should the highlighted say 2 rather than 0?
 

Edit. If the highlighted is wrong, looks like Mesa CT was correct for joint 00 but it has this error for joints 01 and 02, for PWM scale and Encoder scale.

If you can jog Z faster than 150 mm/m the likely culprit
is the spindle encoder or spindle encoder interface.
(that is, it's probably not Z that has the issue but
encoder mis-counting above a certain RPM)

The lack of spindle sync also suggests encoder issues.

You might do some basic encoder checks:

Is the encoder RPM correct at all speeds?

If you enable quadrature error checking, do you ever get errors?

if you check the index, does it always zero the position and the index location?
 

Thanks tons PCW,
halcmd show all > all.txt is an excellent tool, and your explanations are brilliant.

Its taking me a while to figure out what each item does and what we are achieving but the cogs are starting to mesh in my brain :-D

I might have to finish work early today and do some more digging.

Thanks again,

 I think this is what you wanted did not see an output or copy of the terminal window so I screen shot it.  I also attached the G-code but had the error with out loading it.
Thanks for your time
 

 

Hello everyone!
I've been reading the forum for a while now!
I successfully installed rt1052.bin on ec300.
Linux is connected, Ethernet led lights up, connected.
But due to the MPG error I wanted to upload the new fixed bin. 3.1.3.
But I got these two errors.
Does anyone know the solution? Some have already run into this.


E Error during motherboard assembly: [session]
0000984 C No ACK received [__main__]

If any one face the issue described in this thread, make sure when you create the image to use GPT partition scheme. Should not use MBR partition scheme


Good day

Philip

how do i config it ? Please help.

Used the source from: github.com/armbian/linux-rockchip
The rt patched source is now next to the deb files.
The only thing I noticed was that when you create a deb package it automatically compresses the kernel image (which gives a missing arm64 magic error), so to workaround that I repacked it with the uncompressed kernel.

Also after installing LinuxCNC it updated the iniramfs of the old kernel and linked uInitrd to the old kernel one. To prevent that from happening it might be better to remove the old kernel (after making a backup).
Otherwise you could: sudo update-initramfs -u -k all

I've updated the deb package with the iwl driver by the way.

Moved, thank you.