Advanced Search

You should try checking the Merge Circles box.
The test checks for a full, closed circle. If he distance between start point  and end point is < 0.01 mm it is a full circle.
Have to allow something for numerical precision but 0.2 mm seems a lot when it should be 0.

I see what happened. After the almost full circle, you got in a very short segment that should have been merged with the circle.
But instead of merging, it ended up as an own short segment. See line N430 in the G-code you attached. There is the small segment.
 

Thanks for testing

ohh, i forgot a package in the installer:
the BOB is added as module in the sample config, you can convert/split this into single plugins:
 

The pins on the left and right connector are named P1->P17,
like on the DB26 connectors:
 

hope that helps.





 

hier stand Unsinn 

Try this version for 2.9.
name it qtdragon_hd.ui
put it in YOUR CONFIG FOLDER/qtvcp/screens/qtdragon_hd/

Chris

I have LCNC version 2.9.4 on a core i5. I used the Installer-Script the script all went well smoothly.
I connected my Tangobob and the China 5 axis BOB and used the deafault config for the setup Gui. Found the GUI to be very intuitive. However after Generate and Compile when I try the Flash button, I get the following error:

openFPGALoader -b tangnano9k impl/pnr/project.fs -f
make: openFPGALoader: No such file or directory
make: *** [Makefile:41: load] Error 127

Also is there any DB25 pin mapping or schematic of the China 5 axis BOB available to customize the config, or am I missing something?

Any help will be much appreciated

Thanks

rebelx wrote:

Thank you NTULINUX. A few years ago I started running my machines with QtDragon. I have not used axis ever since. I think your Gentoo build gives me the perfect reason to start gaining some experience with FlexGUI, which I think is a great initiative.

JT made like a 5 line change to get FlexGUI working in Gentoo, ever since, FlexGUI has been rock solid with Gentoo.

Turboss and someone else (Lcvette I think) is working on porting qtpyvcp to pyside6. Once their migration is complete, I'll be pushing out a new Gentoo image with support for qtpyvcp. qtpyvcp currently is on Qt5, and Qt5 has been getting purged by the Gentoo devs and they've been dropping support for it all across the board. QtDragon is also based on Qt5. FlexGUI is your best bet right now as it uses Qt6 and I haven't had any troubles with it. Gmoccapy also works flawlessly.

Good afternoon Rob and Rod,

Thank you for very much for your helps. I appreciate the guidance and the info.

I have bought a Preciva HSC8 6-6A bootlace crimpper last month, it comes with 1900 ferrules.

I used it on the single driver I have, I found out that the wires on this driver are of different diameters, that is why I had to use different ferrule sizes:


I am happy with this crimpper, the first one I have ever used

I plan to use to common blocks with the switches. The blocks I have are from Jaycar: www.jaycar.com.au/16-way-100a-brass-busbar/p/SZ2004; they are rated for 100A, but I like how they look.

I have found that these common blocks work well with the ring terminal connectors: once screwed in, they don't come lose easily. The wires with the ring terminal connectors are salvaged from a Japanese Tiger rice cooker, I use salvaged wires during my learning process, but I will use proper wires for the final one. I plan to get a proper crimpper for this, too.

Thank you for the two websites Rod. treotham.com.au/contact is practically next door to my place, There is also a Jaycar store, and www.power-supplies-australia.com.au/ are also in the neighbourhood.

Thank you and best regards,

...behai.

Interesting, thanks for looking into that. Everything I've cut so far is with merge circles off, but perhaps I should check it and see what happens. What is odd is that there are three other holes in the bolt pattern of identical size without this issue. What does the check in this if statement actually do? Line 502: if (Vector.diff(circleBuffer.start, circleBuffer.end).length < toPreciseUnit(0.01, MM))

What would happen 0.01 MM was increased?

Thank you NTULINUX. A few years ago I started running my machines with QtDragon. I have not used axis ever since. I think your Gentoo build gives me the perfect reason to start gaining some experience with FlexGUI, which I think is a great initiative.

unknown wrote:

You could always choose not to run them.
Or you could run them when not machining a part.

 

Yes of course, but I prefer a clean install with minimum "garbage" and let a machine controller just be a machine controller. I would not run any other programs on my LinuxCNC production machines, for the same reasons as why I prefer not to have my machine connected to the internet: keep the machine clean and stable. 

im sorry if this is a dumb question how do i implement this
i have downloaded the qtdragon_hd_vertical.ui.
how do i load i up.

I’m using the QTDragon_HD UI and Probe Basic with a 3D probe.  Hopefully this may lead you to the Ah ha moment.  All values are in inches.These are the settings I have in my .ini, .hal, and qtdragon_hd.pref files..ini file

[PROBE]
# pick basic probe or versa probe or remove for none
#USE_PROBE = versaprobe
USE_PROBE = basicprobe.hal file

#3D Probe debounce & Tool-Setter-Debounce
setp debounce.2.delay 100 #this sets the delay 100 iterations of the servo-thread
addf debounce.2 servo-thread
 
#3d Probe
net deb-probe-in debounce.2.0.in <= hm2_7i76e.0.7i76.0.0.input-11-not
net probe-in debounce.2.0.out
net probe-in  => or2.probe_in.in1
 qtdragon_hd.pref

[PROBE OPTIONS]
Probe tool = 99
Probe diameter = .138
Probe rapid = 60
Probe feed = 10
Probe search = 30
Probe max travel = .3
Probe max z = .2
Probe extra depth = .1
Probe step off = .2
Probe xy clearance = .25
Probe z clearance = .25
Probe edge width = .2
Calibration offset = 0
Cal x width = 0
Cal y width = 0
Cal diameter = 0

John

Have you checked squareness of the part, using a micrometer measure the height in the 4 corners. It dosent look like a machine problem more like a clamping/squareness or misalignment issue. Unless you are loosing steps....

I am machining some clamps from a perfectly squared stock.I do an adaptive 2D contouring. I machine the top part and then I turn it over to machine the part that was previously held by the clamp. The measurement comes out perfect after machining but it has a kind of offset. In theory, since the stock is a symmetrical rectangle, when turning it over it should cut in the same place, right? Can someone tell me what could be the cause?