No Z Motion On Probe or Probe Test - DRO Indicates Motion

A legitimate manufacturer would have replaced new/obviously defective board long before I was forced to seek a third party repair.

Not installing product for which I would not consider purchasing a future replacement (ie: Screw me once, shame on you. Screw me twice, shame on me).

But then again a manufacturer can only warrant faults he knows about. Did you actually contact Mesa once you diagnosed a manufacturing fault?

Mesa was never contacted, nor are manufacturing defects common
(we have a much lower than 1% return rate for any reason).
Things like setup errors are much more common so we typically
verify those things first.

If you had simply contacted Mesa, said you believed you had a
defective card, we would have issued a RMA# for warranty
return/evaluation/repair/replacement.

PCW:

Obvious 7i96 board hardware failure from day one - which I'd have recognized (and you most certainly should have from what you've read here) knowing what I know now.

Your apathy and indifference with respect to your products is surprising, more so after effort to provide firmware that might have (I'll never know) provided near-painless upgrades on the majority of machinery that I own or service.

Contrary to your desires or intent, your arrogance is most welcome, now, before installing your product here, in the field, stocking, or recommending it to others. Better kicked to the curb initially than latter being unable to support products from bad vendor that (at that point - and now) I'm warning everyone to avoid.

In closing, thank you for less than nothing - which turned out to be a good thing.

Plus 1 on this
PCW has given me tremendous support often in less than 2 hours

Mesa nightmare ended a couple of hours ago when my fraud complaint resulted in refund appearing in my account.

Someone should address/report issue with plasmac_gcode.py at line 289. (Optional) line number and white space were just removed from line, which results in zero length string if line contained only a line number. Index into it then raises error. Blank lines, with or without a line number, are allowed in gcode and are ignored by commercial controllers.

@mustbme
If you dissappear from this forum, i will not cry.
m5c

It is absolutely unacceptable how you behave towards pcw!

Other issue in plasmac_gcode.py - get_last_motion:

Adding #<holes> to otherwise valid gcode raises error parsing rapid motion string.

N0060 G20 (Units)
N0070 M52 P1 (test-allow paused motion)
N0080 #<holes> = 2 (test-auto slow for holes)
N0090 g0X8.1563Y0.6048F500 (Rapid)

ValueError: invalid literal for float(): 8.15630.6048500

N0060 G20 (Units)
N0070 M52 P1 (test-allow paused motion)
N0075 F1250
N0080 #<holes> = 2 (test-auto slow for holes)
N0090 g0X8.1563Y0.6048 (Rapid)

ValueError: invalid literal for float(): 8.15630.6048

Not an issue for me as CAM usually deals with holes/radius.