Advanced Search

A bit more progress.

I cut the cable channel covers to length and also the touch protection plate for the filters under the servo drives. This is most likely as nice a photo as I will ever get from the cabinet. From here it's most likely only downhill 
 

I have put the cabinet on the machine, and started with some preliminary commissioning. The first task is just to get the axes moving so I can adjust the linear scales and end stops (and that doesn't require much else than connecting the servos). Once that is done I will try to do some cable management for all the cables on the machine. Because I moved the electrical cabinet closer to the table, I cannot reuse the original way the cables were routed from the X/Z axes. But also in some other areas, I want to tie the cables down somehow.
 
 

Simply open the file in a text editor (eg notepad, geany, mousepad, vim, etc )

I want to work with my model file,. Could anyone guide me on how to modify or work with this file? Where should I make the necessary changes, and what’s the best approach for editingfiles in this context?Any help or advice would be appreciated!Thanks!

I'm using LinuxCNC 2.9.1 on a Raspberry Pi 400 with Debian 12 "Bookworm" (just for benchmarking, will upgrade to desktop when I get everything installed on a real machine) and connected to a Mesa 7i96s.

The 7i96 is connected to a DM542t, which is then connected to a Nema 23 stepper motor () that is set up for the X axis. I installed everything and ran the Mesa config tool and it shows a connection to the 7i96s.

When I turned everything on I was driving the stepper motor and knew this because it was frozen and I couldn't turn it.

The connection between the 7i96s and the driver is as follows:

Step 0--->Drag-

Step 0+ -> Pool+

Directory-->Directory-

Catalog+ -> Catalog+

I don't know where to start troubleshooting, any information would be helpful.

Thanks.[/url]

There are users with converted biesse machines on this forum. If you have the time and motivation to convert it then it is certainly worth it. To give a better assessment of what would be required to get it running with linuxcnc we would need to know more about the motor drives (axes and spindle) if you are lucky then you can reuse drives and motors.
The more information you can provide the better we can help.

Thank you for the kind words, and you are doing a nice job yourself.

Currently out of the country... sounds all too familiar. For me it's the largest reason why it seems to take me so long to finish my Maho - I'm so often away from home.

Maybe I jumped to conclusions / misinterpreted the information regarding the hydraulic pump. It depends on how you reached the conclusion that the machine is in emergency stop. In my opinion, the machine is in emergency stop if you don't have the 110 VAC "control voltage" at terminal 156 (with reference to terminal 150), shown in my second screenshot in the previous post. If you don't have 110 VAC at terminal 156 and the reason is related to the hydraulic pump, then I don't see much other reasons than the temperature switch. But in that case, the issue could also be caused by a few other things than the hydraulic pump.

On the other hand, if you determine that the machine is in emergency stop because light 3SH1 doesn't light up or the hydraulic pump doesn't run (for a short while) when switching on the power to the machine and pressing the 3SH1 "on" button, then there may be many other reasons, including 3F1. If this is the case, I would first measure the AC voltage across terminals 156-150 (after you have pressed the 3SH1 "on" button). If you don't get 110 VAC there, the issue can be one of many things, and to determine which would require some more measurements. Easy things that come to mind in that case could anyway be axis overtravel / limit switch.

Let us know in case you need some help troubleshooting once you get back to it.

RDA wrote:

I would say choose the best from a cost/performance point of view and dont worry about packages or layers.

I can help on the KiCad and 3D (case) stuff if you want.

EDIT: As for the isolation, I would minimize it as it always add quite a lot of cost. After you have a working board, isolation can always be put to the version 2 of the board if needed.

I think you're right, it's better not to make too many compromises,
then it will probably be the ECP5.

about the isolation, I already have all the components, so that shouldn't be a problem.

3d: i already have openscad templates for the housing

I will still need a lot of help with KiCad

onceloved wrote:

You can consider Tang Primer 25K

I had already thought about it, I also have a board at home, but the pin spacing of the connector is even worse than with the BGA ;(

If you zero without G43 'TLO Z' will be zero and once you activate it then the controller will lift the spindle up by the tool length offset (TLO Z) which seems to be set to 1.5 (inches probably).

Graphics card is added, not built-in. Without graphics card, max jitter comes in the range of 50,000ns~80,000ns.

And this morning I faced new error situation. Screen shot attached. It is reading error as message says. What exactly causes it? Machine inputs and outputs stops working with this error.
.
 

You can consider Tang Primer 25K

NTULINUX wrote:

PhilipME,

Are you using a vanilla Debian install from their website? If so, LinuxCNC is not installed by default so you should be safe to proceed and skip that step.

If LinuxCNC is already installed (not run-in-place) then I'm not sure what's going on.

If you're ONLY using run-in-place, you can also skip the purge command as well, but do not try to use the run-in-place instance as it will not work with RTAI unless you've built it against the RTAI kernel debs that are listed in the first post of this thread.
 



 

Sorry if I confused you

I edited this post so many times because I am working full time on this error

this is the final edit I hope. Next time I will have new entry for the edit

so when I dpkg three of the files, I get no errors

only linuxcnc_2.9.2_amd64.deb gives me the error above

dpkg: dependency problems prevent configuration of linuxcnc:
 linuxcnc depends on libboost-python1.74.0 (>= 1.74.0+ds1); however:
  Package libboost-python1.74.0 is not installed.
 linuxcnc depends on libboost-python1.74.0-py311; however:
  Package libboost-python1.74.0-py311 is not installed.
 linuxcnc depends on libmodbus5 (>= 3.1.4); however:
  Package libmodbus5 is not installed.
 linuxcnc depends on libtk8.6 (>= 8.6.0); however:
  Package libtk8.6 is not installed.
 linuxcnc depends on libudev-dev; however:
  Package libudev-dev is not installed.
 linuxcnc depends on iptables; however:
  Package iptables is not installed.
 linuxcnc depends on blt; however:
  Package blt is not installed.
 linuxcnc depends on mesa-utils; however:
  Package mesa-utils is not installed.
 linuxcnc depends on python3-tk; however:
  Package python3-tk is not installed.
 linuxcnc depends on python3-numpy; however:
  Package python3-numpy is not installed.
 linuxcnc depends on python3-gi-cairo; however:
  Package python3-gi-cairo is not installed.
 linuxcnc depends on python3-opengl; however:
  Package python3-opengl is not installed.
 linuxcnc depends on python3-configobj; however:
  Package python3-configobj is not installed.
 linuxcnc depends on python3-xlib; however:
  Package python3-xlib is not installed.
 linuxcnc depends on libgtksourceview-3.0-dev; however:
  Package libgtksourceview-3.0-dev is not installed.
 linuxcnc depends on tcl8.6; however:
  Package tcl8.6 is not installed.
 linuxcnc depends on tk8.6; however:
  Package tk8.6 is not installed.
 linuxcnc depends on bwidget (>= 1.7); however:
  Package bwidget is not installed.
 linuxcnc depends on tclreadline; however:
  Package tclreadline is not installed.
 linuxcnc depends on tclx; however:
  Package tclx is not installed.
 linuxcnc depends on python3-pyqt5; however:
  Package python3-pyqt5 is not installed.
 linuxcnc depends on python3-pyqt5.qsci; however:
  Package python3-pyqt5.qsci is not installed.
 linuxcnc depends on python3-pyqt5.qtsvg; however:
  Package python3-pyqt5.qtsvg is not installed.
 linuxcnc depends on python3-pyqt5.qtopengl; however:
  Package python3-pyqt5.qtopengl is not installed.
 linuxcnc depends on python3-opencv; however:
  Package python3-opencv is not installed.
 linuxcnc depends on python3-dbus; however:
  Package python3-dbus is not installed.
 linuxcnc depends on python3-espeak; however:
  Package python3-espeak is not installed.
 linuxcnc depends on python3-dbus.mainloop.pyqt5; however:
  Package python3-dbus.mainloop.pyqt5 is not installed.
 linuxcnc depends on python3-pyqt5.qtwebengine | python3-pyqt5.qtwebkit; however:
  Package python3-pyqt5.qtwebengine is not installed.
  Package python3-pyqt5.qtwebkit is not installed.
 linuxcnc depends on espeak-ng; however:
  Package espeak-ng is not installed.
 linuxcnc depends on pyqt5-dev-tools; however:
  Package pyqt5-dev-tools is not installed.
 linuxcnc depends on gstreamer1.0-tools; however:
  Package gstreamer1.0-tools is not installed.
 linuxcnc depends on espeak; however:
  Package espeak is not installed.
 linuxcnc depends on python3-poppler-qt5; however:
  Package python3-poppler-qt5 is not installed.

dpkg: error processing package linuxcnc (--install):
 dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.36-9+deb12u8) ...
Processing triggers for mate-menus (1.26.0-3) ...
Processing triggers for desktop-file-utils (0.26-1) ...
Processing triggers for mailcap (3.70+nmu1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for shared-mime-info (2.2-1) ...
Errors were encountered while processing:
 

look, the square encoder gives us the direction and frequency, you can also calculate the angle and so on, depending on the accuracy of the encoder, the Z channel allows you to refer to the position of something, for the MPG Z is not needed, for stepper motor feedback, I would choose a diver with encoder support, and now I want feedback of the spindle speed, in theory it can be implemented using A encoder channel, or the Z channel theoretically could also give such functionality, I don’t need to cut threads, just feedback of revolutions per minute

PCW wrote:

The 7I96/7I96S are step/dir controllers. The 7I96S has a one channel 0 to 10V
output for spindle control. I think tommylight suggested the 7I96S as it gives
you some step/dir outputs for added drives.

For an analog  servo system you need multi channel analog outputs and
multiple encoder inputs. You can add these to the 7I96S either by adding a 7I77
or a 7I85 and 7I83.

A 7I84 just adds more digital I/O say if you have a tool changer.

Sourcing means for example an output device that supplies +24V to a load with a negative common
 

Sinking means for example an output device that grounds its outputs to drive loads with a +24V common

so now I'm a little more confused.  I just read about the 7i77, which seems like doing the 7i96s plus 7i77 would get me where I want to be, but then I looked at the much cheaper 7i83, which appears to do the same thing?  

and you said pair the 7i96 with a 7i77 or 7i85 and 7i83, so why would I need the 85 and 83 together?  So is a 7i77 essentially like a 7i85 and 7i83 put together on one board?

I'm sorry for my complete ignorance, but so many of these cards seem to do the same thing, especially to someone like me who has no clue about things...

My RPi mill is currently LC2.9.2, and very successful.
But I cannot queue MDI commands, and Run From Here starts back at the beginning.

I have assembled a test setup to check operation of my old 7i96 Mesa, and installed LC2.8.4.
The LC2.8.4 allows queuing MDI (checked to 8 in stack), and Run From Here does just what it says.

I am inclined to change the mill back to LC2.8.4 to regain the "features".
What are the pro/con ?
Will LC2.9.3 include the "features" ?

The old Mesa card, originally removed because of perceived ethernet problems, is refusing to connect.
I will see if I can get the card checked locally (Sydney).

John.