Advanced Search

You can use 7i80hdt_sv12d.bin (for 3 7I33s)
 Just enable 4 encoders and 4 PWMgens and the
rest of the pins will revert to GPIO (for the 7I37s)
 

Yes, I'm seeing exactly the same issues you're describing.

Adding M5 to on_abort.ngc does indeed work well in this case, although, as you say, it only masks the problem.

Nevertheless, it won't hurt to leave M5 in permanently.

I tend to think it'll be fine as all I'm using the 24V is for my homing switches and powering the board to let me control the spindle.

Regarding how I go about controlling the spindle, I'm not sure about how to do it. I have attached my hal file below. When I measure the voltage between the pins circled in red I get 0.01 Volts (even after I've homed my axes and and sent it an m3 s500).


 

Logthor wrote:

I believe my BoB is optically isolated ( this is the link to it). 
 

I just measured it. The 5V and 12-24V voltages are isolated from each other, but 12-24V is also used to power the home, estop and probe inputs on the opposite side of the board. If there is a risk of applying high potential to the 12-24V power supply, it is safer to use a separate cheap Chinese PWM->0-10V board and a separate small power supply. As for the 0-7V range, it is probably enough to scale the spindle speed appropriately (for example, setp pwmgen.0.scale 2000 instead of 1400, i.e. 1400 rpm will be 70% of 10V)

Hardware: 7i95T **rev A** (Efinix), LinuxCNC 2.10.0~pre0.6386.g3cd702c690
(buildbot deb), `hm2_modbus` + `mesambccc`. Slave: Delta C2000 VFD, 19200 8E1
RTU, address 1, parameters verified on its keypad.

Wiring per the 7i95T manual for 2-wire RS-485: TX+↔RX+ / TX−↔RX− bridged,
SG+/SG−/SGND to the drive, end-to-end continuity checked, bias resistors
fitted (2×2k2 to +5VP/GND), termination tried both ways (W23, rev A), both
polarities tried. A 7i84 runs error-free at 2.5 Mb on either serial port, so
transceivers, connectors and cabling are known good. A Saleae logic analyzer
at 24 MS/s sits directly on the RS-485 pair.

I believe I found three independent problems. As far as I can tell from the
forum, nobody has ever reported a *working* hm2_modbus setup on a 7i95T
(threads 51956 and 52858 both end without a success report), which would be
consistent with the following:

**1. TX drive enable polarity is not honored.**
Both official bitfiles (`7i95t_1v3pkt.bin`, PktUART v3 on serial 0, and
`7i95t_1pktv2d.bin`, v2 on serial 1 — md5-identical between mesact 2.1.8 and
the current mesanet.com 7i95t.zip) declare the TX enable pin as sec_pin 0x2,
which pins.c names "Drv Enable low". The hostmot2 driver never applies that
polarity: out of the box the RS-485 driver is **never enabled during
transmission** and the bus stays completely silent. Workaround found by
experiment: `setp hm2_7i95.0.uart.00.tx-drv-en.invert_output 1` — after which
the drive enable does toggle (visible on the analyzer). Should the GPIO
inversion be applied automatically by the driver from the sec_pin type?

**2. With DE fixed, no serial data ever appears on the line.**
Whatever is sent (hm2_modbus frames, or bytes pushed directly into the TX FIFO
via the raw interface at 0x6100 + sendcount at 0x6200), the analyzer shows a
**single solid low pulse per transmission, never a UART bit pattern** — even
for 0x55 payloads that should produce a dense alternating train. Pulse length
for an 8-byte frame is ~550 µs, which is ~88 bit-times at ~160 kbit/s, i.e.
about 8× the commanded 19200 (TX bitrate register readback is 483 for a
commanded 2304 baud, consistent with rate = baud × 2^24 / 80 MHz on the driver
side). So it looks like the serializer runs ~8× too fast AND the data path to
the TXData pad is stuck low during the burst. The slave never decodes
anything; the drive's own receiver decodes our DE edges as occasional 1–2 byte
ghost frames, which is what hm2_modbus then reports.

**3. The TX module eventually locks up entirely.**
After a series of hm2_modbus reloads and raw FIFO writes, the transmitter goes
completely dead — no pulses at all, not even via raw register writes — while
the watchdog has not bitten and all other functions (sserial, stepgen pins,
encoders) stay alive. Persists across hm2_modbus reloads; not yet re-tested
across a power cycle.

Also possibly related: at load time the "Drv Enable low" pin is listed on
implausible connectors (`TB3-16/TB3-17` for 1v3pkt, `TB4-22/23` shared with
TXData for 1pktv2d) where the .pin files say "Internal".

Has anyone ever seen the Efinix 7i95T PktUART actually transmit? Is a fixed
bitfile possible? Happy to test anything and to produce fresh analyzer
captures on request — this is for a lathe retrofit where the spindle VFD was
planned on this port.

Made an issue:
github.com/LinuxCNC/linuxcnc/issues/4465

Found some things in testing:

-I can see the spindle speed display go to 0 on first abort then immediately return to previous speed.

-The sim uses on_abort.ngc but removing it doesn't make a difference, but adding an m5 to the script will stop the spindle reliably. I think this is just masking the problem.

-I also note in the test program the initial line that starts the spindle is silently ignored.
I am not sure this is related.

-If I abort close to the beginning of the program - always restarts the spindle.
If I abort near line 500, 1000, or 1500 spindle stops.


Do you see the same?

I tend to think I'm making some sort of mistake. I currently am only making use of the PWM pin, do I also need to include pins for turning my spindle on and off as well?

I believe my BoB is optically isolated ( this is the link to it ). I just would like an example HAL file with my settings. When I measure with my multimeter after using stepconf, I get nothing even after I issue a command like s500 (my axes have all been zeroed). 

I'm replacing a 5i24 PCI card with the ethernet equivalent (7i80HDT): outputs go through a 7i33 + 2 7i37s. A previous posting (but referencing a 7i80HD-16) here said that the SVST4_8 bitfile would appropriately configure the card. Although the file is referenced in the manual, the file (neither .bin or .pin) does not exist in a newly downloaded (8/24/26) file set for the HDT card.
Where can I find a copy of the needed bitfile?
 

    attached find a screen dump of /tmp/isotri.ngc . This file was generated by an execution of polygonpockete.ngc (zipped).  My original goal was to make a log file which listed origin, endpoint, length and tilt of every line in my pocketed figure. This could be used to take advantage of highlighting in the MDI window on my version of linuxcnc.  Length and tilt are stored as comments on lines in the log file where a g0 gcode command to the line's origin and a g1 gcode command to the line's endpoint executed in a MDI window highlights an individual line after the execution ofpolygonpockete.ngc and an erasure of the lines it already highlighted.  To my  surprise the MDI window ignored the length and tilt following the ; and the linuxcnc interpreter went right by the g0 gcode command and executed the list of lines like it was a gcode program, a program containing lots of nasty numbers instead of nasty trigonometry. You'll have to edit polygonpockete.ngc to put the log file where you want it, see (logopen, (log, and (logclose)  The logfile does not contain any curved lines, nor does it contain the shortlines I put into polygonpockete.ngc to discourage the linuxcnc trajectoryplanner from rounding over the vertices.

Hi Aciera!

i solved it, my problem had several culprits.

1. I have a documentaion for my MPG, which told me which keys are generated. i don't know why, but for 3 buttons, the documentation was simply wrong..  While learning the keyd feature, i learned how to grab the sent keys...

2. With the right udev rules, i can load the "keyd virtual keyboard" into the hal-input.
Everything works fine now, 

3. I did not solve my problem that a few keys triggered the ui, i tried with -KRAL Option, no luck, but i remapped the keys with keyd, so ther is no interaction with the ui any more.

Thanks for your help!
I would say i start figuring out how to net the keys in the halui, i think i will need some help there, because all my buttons are push-buttons, with no lock in pressed-state.

Do you think it is helpful for other people how to handle keyd?
I can offer to write a small tutorial for this tool, but only it there are interested people around..

Greets, Tom

What is the correct way to share the bidirectional index-enable function between:

spindle.0.index-enable
orient.0.index-enable
encoder.0.index-enable

You just need to connect all three to the same signal, so for example like this:

Be careful as many KBIC speed controllers have a analog speed control
input that connect directly to line power, so requires an isolated analog
voltage source.

You can use single ended encoders with the 7I96, to do so,
you must set jumpers W2,W3,W4 into the left had position.

This is described in the 7I96 manual on pages 2 and 12
 

I did finally get this problem to show in a sim, with your test program.
It didn't show with 3d_chips.ngc though.

I actually can see the spindle (by the spindle speed display) stops then starts again.

If I put an m5 in the on_abort.ngc file I could get it to always kill the spindle.
That is masking the problem, but would help in the mean time.

I am testing master, which I think you are using too.