Advanced Search

My setup i pretty rude, as in photos. Currently no h-bridges connected (have no wires available...) but checking encoders and limit/home switches would be great for me. Actually, even starting without crash would be great:)

Thank you for pointing things out.I did my best and studied the files. I wrote INI and HAL based on initial CT output and config from you Tommy.My linuxcnc is crashing with debug info:

---

hm2_7i95: dlopen: /usr/lib/linuxcnc/modules/hm2_7i95.so: cannot open shared object file: No such file or directory./main.hal:17: waitpid failed /usr/bin/rtapi_app hm2_7i95./main.hal:17: /usr/bin/rtapi_app exited without becoming ready./main.hal:17: insmod for hm2_7i95 failed, returned -15142Stopping realtime threadsUnloading hal componentsNote: Usid POSIX realtime

---

Attached HAL, INI and crash report. 

Yes it's working good with these parameters.
I wanted a PID control for better results in threading.

I think you can close the topic. 
I used the calibration tool and everything seems smooth now... 
P=1 was a huge mistake, it's 0.02 now 
Thank you for your help PCW

Yup -- but I was asking about the TB1/TB2 pins. They're listed on the preceding pages, but only with their step/encoder/serial functions. Not as I/O pins.

Guys, rather than burying all this good MAHO 700C retrofit information deep on page 173 of a thread on the MH400E, why not start a specific thread on the 700C so that people in the future looking for that information will have a chance of actually finding it.

Hey,
i'm running LinuxCNC 2.9.4 on a Raspberry Pi 5 in combination with a Mesa Card 7i96S.

I seem to be doing something wrong with my limit switches.
When i manually trigger one Switch all LED's to the coresponding pins to the 4 Limit switches on the board turn on.
They are wired to the board as seen in the picture following
X = 0 / Y1 = 1 / Y2 = 2 / Z = 3
The VCC and Ground are wired in parallel to the 5V and Ground the Mesa card is connected to.

Any help would be appreciated. 

I don't understand why 'feed-mm-per-second' drops to zero every time 'current-vel' reaches a local minimum.

Hi Evgen,

If you try to do roughing G64 P1 Q0 or even G64 P2 Q0
The velocity will be more constant. And the path tends to be G3 continious.

My conclusion for the file:
From what i see is that the file set a velmax for a lot off indiviual G1 line segments. The planner will react to this.
Some off the line - line segments transitions in the file are very sharp, non smooth. Tiny clothoid fillets, will slow down the
motion.

OK.
I think my issue may not be related to yours : Mine seems to have something to do with the graphic driver or something like that.
When I export DISPLAY:0 to my window laptop, I never have this problem.
See dmesg lines when running without export DISPLAY about drm and DMA_VTX_PROTECTION

(fixed the title, wording seems a bit different in german)
EDIT title seems not to be edited.
There was a desktop sized thing on ebay for 130,- EUR so I just bought that one. Assembled, 3-axes, linear rails, steppers, cables. Seems the right starting point to learn.
I'll post details of the steppers, when I get it.

Hi
Has anyone had experience with this controller? I plan to do a retrofit, but these drivers are not very clear to me, i.e. I'm not sure if they have an analog input somewhere? Thanks

I acknowledged most of that.  It’s ok to just say “Thank You”.

Qtdragon_hd normal open 100-120Mb file. It takes about 40 sec on N100 with 8gb ram and ssd disk.

That is correct. 9 stepgens (6 for the main hardware + 3 for the BoB).

 

The inputs and outputs on TB3 are described on Page 10 of the document you shared