ok, fixed. so the update works well. it does NOT solve the servo noise/resonance/howl. It does seem to have fixed everything else so far.

NWE wrote:

ihavenofish wrote:

sudo apt install build-essential git linuxcnc-uspace-dev ethercat-master libethercat-dev

--- and the line above gives a 404 error.


 
That one is pulling from several different sources, could you post the 404 error?
 

this is what i get, thanks

E: Failed to fetch download.opensuse.org/repositories/scien...cc5-1%2b27.1_all.deb   404  Not Found [IP: 195.135.223.226 80]
E: Failed to fetch download.opensuse.org/repositories/scien...5-1%2b27.1_amd64.deb   404  Not Found [IP: 195.135.223.226 80]
E: Failed to fetch download.opensuse.org/repositories/scien...5-1%2b27.1_amd64.deb   404  Not Found [IP: 195.135.223.226 80]
E: Failed to fetch download.opensuse.org/repositories/scien...5-1%2b27.1_amd64.deb   404  Not Found [IP: 195.135.223.226 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

 

ihavenofish wrote:

sudo apt install build-essential git linuxcnc-uspace-dev ethercat-master libethercat-dev

--- and the line above gives a 404 error.


 

That one is pulling from several different sources, could you post the 404 error?

Don't know whether this would be a solution for your use case or not, I have been doing this in libreoffice draw. Sometimes I get to crowding the pages a bit, but if I'm not planning on printing to paper it is easy enough to set the page size larger.

Each hal component pin is an individual rectangle. The signal wires are 'connectors' so they readily stick to the rectangles and come with when I pull rectangles around. For the signal names I've just been pasting smaller rectangles on top of the connector lines. They're not attached and easily get lost if I start rearranging stuff. Next time I'm drawing one of these I want to use two connector lines to one signal like:
[hal pin a]  -  -  -  [signal name]  -  -  -  >[hal pin b]
(still in libreoffice draw) the first connector will be drawn from "hal pin a" to the signal name rectangle. The second one will be from signal name to "hal pin b"

With the rectangles I do a lot of copy/paste. I don't drag them around much with the mouse, rather select and move in increments with the arrow keys or enter calculated positions.

I frequently work with the page display zoomed in some when doing this, makes it easier to grab the handles.

I see andypugh has his input/output pins left vs right justified, that is a new idea for me, I'll start doing that way as well. I had all my text center justified.

I tried to set this up and i get a 404 error. What have I done wrong?

i followed these instructions:

#remove old linuxcnc-ethercat
sudo apt remove linuxcnc-ethercat

#install pre-requisites
sudo apt-get install golang
sudo apt install build-essential git linuxcnc-uspace-dev ethercat-master libethercat-dev

--- and the line above gives a 404 error.

(remaining instructions:)
#patch download
cd ~
git clone github.com/grandixximo/linuxcnc-ethercat.git linuxcnc-ethercat-patched
cd linuxcnc-ethercat-patched

#patch install
make
sudo make install

I removed the pango stuff and with just 1 line 'set_markup' it was possible to set color and weight.

 
 

 

Thanks that's at least a big step in the right direction. Now I just need to get the label change working again. (That's what all the Pango stuff did) It was supposed to change the ZW at the top center to ZZ and change the color of it when the "gladevcp.label-trigger" hal pin changed to true.

Changing that does not make the hal pins from the call back file work for me. I can only see the hal pins created by the hal glade widgets.

If you're just looking for a schematic, you should take a closer look at KiCad.

Hi djdock99

I'm new here and I saw that you've retrofitted an MH800W.

I just acquired an MH800W and I've decided to completely rebuild the electrical and CNC components.

I'm going to use Mesa boards and a LinuxCNC interface.

Could we discuss about these modifications?

I have some original Maho documentation if you're interested.

Did you have any problems preserving the KDS driver?

If you'd like, we can discuss this here or by email if you don't want to clutter the forum.

I'm going to create complete documentation and a detailed log of my retrofit; this could be useful to future users. I'll create a new thread on this forum when my machine is complete and finished.

See you soon

I tried something with your files. This changes made the pins show up, but still many errors displayed in terminal.

I tried something with your files. This changes made the pins show up, but still many errors displayed in terminal.

just found this manual matic pendant, but teensy 4.1 is too expensive ower price board, can i use teensy 2.0 this ? lot lot cheapen, and what need dong encoder or other library, ?not understand english good, need change arduino ide encoder library to new and were have ? i come old teensy 2.0 USB pendant all time only errorrs whit encoder.h
no declare scope etc. i not know what this all mean. not need diplay , only encoder and rotary SW change acis and scale. can move XYZ remote controll. were i found code teensy 2.0 can use. this.