Advanced Search

tommylight wrote:

You have to compile the component again.

yes, I meant pin numbers as they are shown in the I/O column, but you are right I had a mistake as I tried to configure pwm1, but I experienced the same behavior with pwm0 on i/o pins 7 and 9.
if I use multimeter I see between 2,5..4V signal on pin6 (depends on the value, of course) but nothing on pin8. (corresponding 50pin numbers are 13,17)
/enable signals work properly.
thx

Mesa 7i95T or 7i97T would be all in one, but price might be on the high side for what you need.
You can safely use just a Mesa 7i92T, but must be careful with wiring as the pins are sensitive.
Having said that, i have Mesa 7i92 wired on several of my plasma machines, meaning very high interference environment, and the THCAD is wired with 5-7 meters if cable directly to Mesa 7i92 input, yet i never have issues, ever.
This does imply proper shielding and grounding is a must.
In your case just having good shielded cables and grounding the shield only on the Mesa side inside the box should be fine.

Are you sure you have the pinout correct?

PWM 0 uses 50 pin connector pins 15,19,23

Aciera wrote:

I'm with you, like most of us probably. People like that come and go.

My advice would be:
1. Don't get your blood pressure up, it's not worth it.
2. Only clarify wrong statements that are relevant to the question at hand.
3. Ignore the rest of the babble.

+1

Thanks for your help, that was the problem

Qtdragon changes displayed units based on g20/21 modes

Hi everyone,
I bought this device: SG-ELC-ADIO-DI16-DO16-PNP.
I wrote a custom XML file for it, but for some reason, after I load it, there's a 90% chance that EtherCAT crashes with an error.
I suspect that it might be slowing down the entire system, or maybe I wrote the XML incorrectly.Here’s what I wrote:
 <slave idx="4" type="generic" vid="EE000002" pid="00010205" configPdos="true" >
            <dcConf assignActivate="0000" sync0Cycle="0" sync0Shift="0"/>
        
            <syncManager idx="0" dir="out">
                <pdo idx="1a00">
                    <pdoEntry idx="3101" subIdx="1" bitLen="8" halType="complex">
                        <complexEntry bitLen="1" halPin="out-00" halType="bit"/>
                        <complexEntry bitLen="1" halPin="out-01" halType="bit"/>
                        <complexEntry bitLen="1" halPin="out-02" halType="bit"/>
                        <complexEntry bitLen="1" halPin="out-03" halType="bit"/>
                        <complexEntry bitLen="1" halPin="out-04" halType="bit"/>
                        <complexEntry bitLen="1" halPin="out-05" halType="bit"/>
                        <complexEntry bitLen="1" halPin="out-06" halType="bit"/>
                        <complexEntry bitLen="1" halPin="out-07" halType="bit"/>
                    </pdoEntry>
                </pdo>
                <pdo idx="1a01">
                    <pdoEntry idx="3101" subIdx="2" bitLen="8" halType="complex">
                        <complexEntry bitLen="1" halPin="out-08" halType="bit"/>
                        <complexEntry bitLen="1" halPin="out-09" halType="bit"/>
                        <complexEntry bitLen="1" halPin="out-10" halType="bit"/>
                        <complexEntry bitLen="1" halPin="out-11" halType="bit"/>
                        <complexEntry bitLen="1" halPin="out-12" halType="bit"/>
                        <complexEntry bitLen="1" halPin="out-13" halType="bit"/>
                        <complexEntry bitLen="1" halPin="out-14" halType="bit"/>
                        <complexEntry bitLen="1" halPin="out-15" halType="bit"/>
                    </pdoEntry>
                </pdo>
            </syncManager>
        
            <syncManager idx="2" dir="in">
                <pdo idx="1600">
                    <pdoEntry idx="3001" subIdx="1" bitLen="8" halType="complex">
                        <complexEntry bitLen="1" halPin="in-00" halType="bit"/>
                        <complexEntry bitLen="1" halPin="in-01" halType="bit"/>
                        <complexEntry bitLen="1" halPin="in-02" halType="bit"/>
                        <complexEntry bitLen="1" halPin="in-03" halType="bit"/>
                        <complexEntry bitLen="1" halPin="in-04" halType="bit"/>
                        <complexEntry bitLen="1" halPin="in-05" halType="bit"/>
                        <complexEntry bitLen="1" halPin="in-06" halType="bit"/>
                        <complexEntry bitLen="1" halPin="in-07" halType="bit"/>
                    </pdoEntry>
                </pdo>
                <pdo idx="1601">
                    <pdoEntry idx="3001" subIdx="2" bitLen="8" halType="complex">
                        <complexEntry bitLen="1" halPin="in-08" halType="bit"/>
                        <complexEntry bitLen="1" halPin="in-09" halType="bit"/>
                        <complexEntry bitLen="1" halPin="in-10" halType="bit"/>
                        <complexEntry bitLen="1" halPin="in-11" halType="bit"/>
                        <complexEntry bitLen="1" halPin="in-12" halType="bit"/>
                        <complexEntry bitLen="1" halPin="in-13" halType="bit"/>
                        <complexEntry bitLen="1" halPin="in-14" halType="bit"/>
                        <complexEntry bitLen="1" halPin="in-15" halType="bit"/>
                    </pdoEntry>
                </pdo>
            </syncManager>
        </slave>

And I’m also attaching the original XML file.

as per manual there is only one variable receive and one variable transmit PDO : 0x1600 and 0x1A00.
Each is limited to 10 entries.
You should see some error messages in /var/log/messages.
If you need more than 10 entries, you can use SDO instead of the 0x1600 PDO.
SDOs can be queried/set with "ethercat upload" or "ethercat download".
SDOs are permanently saved to the servo controller, so this is useful for nonchanging config parameters only.

github.com/zmrdko/3DWorks_EasyCAT/blob/main/3DWorks_EasyCAT.ino

you can find some examples of IO, which I tried.

Hi,

i try to get qtdragon_hd in metric mode.
in my .ini file i have: 
[TRAJ]
LINEAR_UNITS = metric

Debug output has the line
QTvcp.QTVCP.QT_ISTAT - DEBUG - Machine is METRIC based. unit Conversion constant=0.03937007874015748

Some of the menus have mm as units. 
However the main screen shows Units = IN. 

What is wrong with my config?
The qtdragon_hd sample configs with metric seem to work fine.

Finally all my Motors are joggable. The key was this part of the hal-file where I had to add some entries:
addf lcec.read-all servo-thread
addf cia402.0.read-all servo-thread
addf cia402.1.read-all servo-thread
addf motion-command-handler servo-thread
addf motion-controller servo-thread
addf cia402.0.write-all servo-thread
addf cia402.1.write-all servo-thread
addf lcec.write-all servo-thread

The amp-error still pops up from time to time but this is something wich could be caused of the not yet tuned motors I think.
Thx a lot (!!!!) for all you help and hints!!

Hello,

today I stumbled across this error and I might be able to provide a useful hint.

I am using Probe Basic 2.9.3 and if I have NO_FORCE_HOMING = 1 in my ini, it remembers the tool.
If I have NO_FORCE_HOMING = 0 in my ini, it won't remeber it.

I guess it sets the tool in the background with some MDI command and it can't execute this command, if it is not allowed to execute a MDI command because it is not homed.

I added #5400 in my .var and with every toolchange it changed that value to the toolnumber.
Whenever I started PB with NO_FORCE_HOMING = 0, it changed the value of #5400 to 0 right after PB started.

I don't mind using NO_FORCE_HOMING = 1 but that causes Issues with the "REF-ALL / HOMED" Button in the Probe Basic UI because that one uses the "status:all_axes_homed" from the QTDesigner and this status only works with NO_FORCE_HOMING = 0...

If someone knows any workaroud, let me know

If that function works for you and your setup can handle the calculated angles then I don't see a problem there.
I would stick with the fanuc format since it uses ijk words which are already handled in linuxcnc. The A3/B3/C3 words of the siemens style would first have to be built into the interpreter.

Thank you for your answer!

Based on your reply, I understand that G43 tool length compensation depends entirely on which kinematic mode is active. I have implemented a conversion from vector format NC (IJK) to XYZAB for my machine, and it seems to work. However, I am concerned whether a simple conversion might misinterpret the intent of the CAM output, or if these two formats (IJK and AB) are truly equivalent and interchangeable.

Here is the logic of my transfer function:

def ijk_to_ab(self, i, j, k):
norm = math.sqrt(i**2 + j**2 + k**2)
i, j, k = i/norm, j/norm, k/norm

a_rad = math.atan2(j, k)
a_deg = math.degrees(a_rad)

b_rad = math.atan2(-i, math.sqrt(j**2 + k**2))
b_deg = math.degrees(b_rad)

return round(a_deg, 6), round(b_deg, 6)

I have two more questions:

Are there any problems with my transfer function (ijk_to_ab)? Although it works in practice, I am worried that a direct conversion might not fully capture all the intent or precision from the CAM output.
If I plan to extend the RS274 module to support vector input, which vector format would be better to implement: the FANUC-style IJK (G43.5) or the SIEMENS-style A3/B3/C3? Are there advantages or disadvantages to either format, especially regarding compatibility and ease of parsing?
Thank you again for your help and suggestions!