Advanced Search

• 7i97T, firmware 7i97t_7i74d.bin; a 7i74 on P2 with a 7i70 and a 7i71 on smart serial
• LinuxCNC 2.9.10 (uspace), hm2_eth; ssr.00.rate at the default 1000000, all invert-NN 0, all out-NN 0
• 5 V from a Mean Well MDR-40-5 on P3: 4.99 V measured at P3
• OUT0–OUT2 switch the logic inputs of a VFD (Control Techniques Commander CD, about 14 V open circuit, about 1 mA), with OUT+ toward the drive. OUT0 and OUT1 pass through safety-relay contacts. Nothing is connected to OUT3–OUT5.

• All outputs off: OUT0, OUT1, OUT3, OUT4 and OUT5 read O.L. That holds both while the LEDs glow and with ssr.00.rate set to 0, when the LEDs go dark.
• OUT3 commanded on: 0.3 Ω (the meter leads), LED fully bright. Off again: O.L, back to the dim glow.
• The LEDs are dark before LinuxCNC starts, and go dark when it exits or the watchdog bites.
• Two days ago, with the VFD powered and the outputs off, its inputs on OUT0–OUT2 read their full open-circuit voltage.

1. Is a dim glow on the output LEDs with the outputs off normal for the 7I97T? Or does it point to a damaged output driver?
2. If it is damage, can it get worse? Could an output that is off start to conduct? Is there a further test you would suggest?

Aciera wrote:

many further changes are currently in testing and will hopefully be merged step by step into master over the coming months.
 

#!/bin/bash
halcmd setp ini.x.max_limit 1000
halcmd setp ini.x.min_limit -1000
halcmd setp ini.y.max_limit 1000
halcmd setp ini.y.min_limit -1000
halcmd setp ini.z.max_limit 1000
halcmd setp ini.z.min_limit -1000

# Filename: M166

#!/bin/bash
halcmd setp ini.x.max_limit 146.0
halcmd setp ini.x.min_limit -86.0
halcmd setp ini.y.max_limit 178.0
halcmd setp ini.y.min_limit -178.0
halcmd setp ini.z.max_limit 100
halcmd setp ini.z.min_limit -10

# Filename: M167

; Filename: M428.ngc
; by remap: kinstype==1 (xyzab-tdr kinematics)
o<428remap>sub
  #<kinstype> = 1        ; xyzab-tdr

   G12.1 P#<kinstype>                   ; select kinstype, syncs interp and motion

o2 if [[#<_task> EQ 1] AND [#<_kins_type> NE #<kinstype>]]
     (debug,M428: Wrong kinematics type)
     (debug,STOP)
     M2
o2 endif
m166
o<428remap>endsub
M2

; Filename: M429.ngc
; by remap: kinstype==0 Identity kinematics
o<429remap>sub
  #<kinstype> = 0

   G13.1                                ; back to identity kinematics, syncs interp and motion

o2 if [[#<_task> EQ 1] AND [#<_kins_type> NE #<kinstype>]]
     (debug,M429: Wrong kinematics type)
     (debug,STOP)
     M2
o2 endif
m167
o<429remap>endsub
M2

tuxcnc wrote:

But today a serious problem arose and I had to look into it

tuxcnc wrote:

The second image is in program execution mode. Why the hell do the parameters change from black to gray,

tuxcnc wrote:

And if this is the case, why is the default g-code theme set to "classic" and not "gcode"?