Advanced Search

In your ini file you have references calling those two files, and those two files are not in your config folder.
If there is nothing you added to those files, edit the ini and omit those two entries calling those files, save, try again.

Found the issue!

Checked all encoder connections, everythings fine. Removed the encoder cover and found small aluminum chips, removed them carfully and sealed it of better. Still the same issue.

The problem turned out to be the powersupply I suspect the thing was overheating after a while and shut off so the motor skipped some steps.

I will add cooling fans with fin filters to keep aluminum chips out. Thanks for the help I am happy to have cleared the chips from my encoder.

Hey guys, I'm struggling. I am beyond frustrated with trying to get Probe Basic to launch fully. I have been trying to get this to work for the better part of 18 hours. 

Here is what I know. 
I can launch the Dev with the sim on the PC. 
I figured out that one of my issues was the screen size. I now have a compatible screen installed. 
I have reinstalled the bookworm iso and followed the instructions several times.
I have cleaned and wiped the system at least 6 times and still always come back to an error launching.
i was having the issue of probe basic not launching error but after a wipe and reinstall and apt repair it seems to have gone away.  
I am now stuck at this point where "I think" I'm missing the custom.hal. I can not find any hal file by that name. 

I have attached a text file of the crash report. I would be very grateful for the help, as I just received a new touch probe that I would like to use. 
I apologize in advance if this is in the wrong section. 

Let me know if you need anything else! Keep on makin chips!



 

Which spindle oil is used? Is the chamber where the motor and spindle connect also the oil reservoir? I too have a chiron fz12w I retrofitted.

Your missing some things from config docs still,
AXES = ?
GEOMETRY = ?

 

Add geometry ini line, that determines which dro displays are shown

Yes post gui hal must include what's in the docs. Add your current items below the probe basic items.

Ok. I have a feeling that this is going to be either easy, OR a long road. I have the system popping up with no errors, however, when I try and test homing I get the following:Named parameter #<geometry> not defined. I cant seem to get it to complete anything else other than jogging and coolant pump Mist and Flood activations.

You rock, thanks for the speedy reply.

TB8 PIN    SIGNAL    WIRE COLOR   VFD
1    SPINDLE-           BLUE               GND
2    SPINDLE OUT   YELLOW            A11
3    SPINDLE+         ORANGE          P12 (12V)
4    NC                     BROWN
5    SPINDLE EN-    WHITE               GND
6    SPINDLE EN+   GREEN              X1
7    SPINDLE DIR-   BLACK               GND
8    SPINDLE DIR+  RED                  X2

VFD inputs must be set for NPN mode (J1)
 

Here is the manual for my VFD:
workerbeeit.com/H100SeriesManual.pdf


Here is the wiring I have for the SPINDLE header coming off the 7c80 (I am aware that pin 4 is not connected/used, just terminated the wire so it was not hanging loose)

TB5 PINOUT    
TB8 PIN    SIGNAL    WIRE COLOR
1    SPINDLE-           BLUE
2    SPINDLE OUT   YELLOW
3    SPINDLE+         ORANGE
4    NC                     BROWN
5    SPINDLE EN-    WHITE
6    SPINDLE EN+   GREEN
7    SPINDLE DIR-   BLACK
8    SPINDLE DIR+  RED


I am not sure how to wire the enable and direction controls to the VFD
VFD PIN   DESC                                    WIRE COLOR
AO            ALG. V OUT 
GND        GND ISOLATED FROM PE 
X4
X5
X6/Y1_FO
P12         12V OUT 150mA 
AI1          ANLG V IN 
AI2          ANLG V IN 
GND       GND ISOLATED FROM PE 
X1
X2
X3  

X1-6 are multifunction pins, and can be assigned, but i'm not sure how to wire this (someone on discord mentioned wiring as "single ended"?)

It also appears that this VFD can use ModBUS, not sure if that would be a better option than analog?

The mill also has a 2-wire manual (physical) speed dial (potentiometer) that I would also like to wire up, not sure if that should be wired to the 7c80 or directly to the VFD.

Have you a HAL file example
I have had this woking using the show hal example in you video

Hi,

The planner in the video does account the abc axis into the motion using endvelocity's.

However it has no abc tooldir (tooldir blend) optimalisation feature at this moment. 


 

Ok, here's the latest update.

Text from the log file:
[QTvcp.QTVCP.WIDGETS.GCODE_EDITOR][ERROR]  load_text(): [Errno 2] No such file or directory: '' (gcode_editor.py:338)
[QTvcp.QTVCP.WIDGETS.DIALOGMIXIN][DEBUG]  Setting ToolChangeDialog-geometry dialog geometry from from prefs. (dialogMixin.py:127)
[QTvcp.QTVCP.WIDGETS.DIALOG_WIDGET][ERROR]  No callback or STATUS message specified for: toolDialog_ (dialog_widget.py:317)
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 12756, resource id: 9629954, major code: 40 (TranslateCoords), minor code: 0
USRMOT: ERROR: invalid command
Linear move on line 277 would exceed Z's positive limit
Linear move on line 277 would exceed joint 3's positive limit
invalid params in linear command


The images I am attaching honestly make little to no sense, rather the values in the images.

 


 
 

setp hm2_7i92.0.packet-read-timeout 30

I would set this to 80 ( 80% = 800 usec at a 1 ms servo
thread period), or just comment it out
If you are dropping many packets, that might
be an issue.

Loss of steps might be an issue also. This may be improved
by using the interpolated encoder position, as a 10 count
per turn encoder is going to give a very rough Z axis position
command, only smoothed by the acceleration limits.

The Z motion plots look linear so the main error seems to be a variable offset
at the start. Are multiple passes at the same speed perfectly aligned?
The start and end of motion use maximum acceleration so  possible
locations of lost steps.

Or maybe you have a better way to run more than 3 axis look ahead?
I think along with the s-curve another major update would be the look ahead.