Advanced Search

Omg That would be great opportunity but I am in UK If You not require me on site and I can help anyhow I can try.

easy fix, you have not formatted the sidebar by adding a widget container or telling the current widget container to format vertically or horizontally so the widgets are there but out of view. need to add a layout format type by right clicking and selecting from the bottom options in the right click dialog.

I’ve released the first version of a small utility called CNC File Shuttle.
I originally wanted a simple way to send G-code files to a LinuxCNC computer with the same basic convenience I was accustomed to on another controller: select some files, choose the destination folder, send them, and see whether the controller and LinuxCNC are online.
CNC File Shuttle is written in Python/Tkinter and supports Windows, macOS, and Linux. I have primarily developed and tested the packaged Windows version, transferring files to a LinuxCNC computer over SFTP. macOS and Linux can currently run it from source.
Main features:
* Local folders, mapped drives, mounted shares, USB drives, or SFTP destinations
* Saved machine profiles
* Multi-file queue with destination preview
* Local and remote destination-folder browsing
* Requeue completed files without selecting them again
* Ask, always-overwrite, and skip-existing options
* SSH-key generation and guided public-key installation
* SSH host-key fingerprint verification
* Transfer progress and remote file-size verification
* Automatic read-only LinuxCNC status monitoring
* Display of the loaded program and current executing line
* Protection against overwriting the program currently active in LinuxCNC
* Failure-only diagnostic logs
The LinuxCNC status portion is intentionally read-only. It uses `linuxcnc.stat()` through a small helper installed under the remote user’s `~/.local/share/cnc-file-shuttle` directory.
It does not create a LinuxCNC command channel and cannot start programs, jog or home axes, reset E-stop, change machine power, or issue MDI commands.
Status monitoring also does not impose a blanket transfer lockout while the machine is running. Unrelated files can still be transferred, but the application blocks an attempt to overwrite the exact program path LinuxCNC reports as active.
SFTP is handled internally with Paramiko. The application supports key-based or password authentication, although key authentication is the intended normal setup. Passwords and private-key passphrases are used only for the current operation and are not stored in machine profiles.
The Windows release is packaged as a one-directory application, so Python does not need to be installed. The complete extracted folder must be kept together.
The project is MIT licensed. Source code, installation instructions, and the Windows release are available here:
CNC File Shuttle on GitHub
This is the first public release, so feedback is welcome—especially testing on macOS or Linux, different LinuxCNC versions, and installations using program-directory layouts different from mine. If something fails, the Activity Log and automatically generated failure log should provide useful information for tracking it down.
 

correct probe is stored tool with a z offset required and you also need to run the calibration to configure the trigger distance if you have not already done so.

Vielen Dank für eure Hilfe und die Zeit, die ihr für mich aufbringt. Das ist nicht selbstverständlich.
Meine xml sah schon so ähnlich aus, ich fürchte es hängt an der .hal Datei
     

I did inspect the tack and servo and the brushes and both commutators look like they were never used. Also, my pid settings are now in a usable state, not perfect but better than the all zeros that were in place before. They didn't transfer over for some reason and i missed that one. 

So the DC servo is like new, but coupled to a second hand drive that i had to replace the mosfets on. I bench tested the drive and it works very nicely with my power supply to control the servo. When i disconnect the +-10V from the mesa card it holds position and is what im assuming is waiting on a +-10v signal. When i hook the +-10v back to the Mesa card it just starts running until i get a following error. It is unresponsive when i try to command a jog signal, it just runs and then errors out.  

I see the manual is available in various languages. Can I set  the UI to german?

Muzzer wrote:

Muzzer post=349428 userid=18852

How do you plan to handle bug fixes and feature upgrades? Do purchasers get free perpetual upgrades every time new features are added or are they stuck with the release that was active at the time of purchase? I can't see how the first option would be commercially sensible for you and the second wouldn't work for users.

Centroid have an interesting model where you can choose to pay for periodic major updates where new features have been added but otherwise you purchase is forever and includes free minor updates and bug fixes. Might be worth considering something similar?

Certainly it won't be long before some kind of machine learning / AI becomes usefully capable of this kind of feature recognition and takes a lot of the surprisingly laborious CAM off of our hands. There are hints of it already in CAM such as Fusion where you can use Claude to create toolpaths directly inside Fusion via its API and an "MCP" connector. I've done this myself and it's surprisingly powerful but at this stage it's not something I want to stop doing myself. In my experience, agents like Claude currently have the capability and dependability of an excitable junior engineer who doesn't know what he/she doesn't know. This will surely improve in the medium term.

Here's a view of the Claude / Fusion integration at work:

Hi.

1) Until we release a new version of the software, you get unlimited updates. If and when a new version is released, the previous one is locked for life with no further updates. We expect that the product would have reached full maturity by then. We expect to release a new version every 24 - 36 months
2) We expect to have an update a month during the first 3 - 4 months and slow down after, these are more for features rather than bugs or refinements in UI. We dont claim to be bug free but we have tested thoroughly already. We are also working on a couple of additional machining strategies like radial thread on a rotary setup - all will be free updates.

Whatever you do, Fusion will cost you 1500 per year for a basic 4th axis. Takshak wont.

We have a community space for feature requests / posts submissions / bug reports etc..
We have videos on our Youtube Channel showing both 3 axis and rotary Feature recognition. It does not cost you anything extra. comes standard.





 

Cheers, I appreciate the reply

This is the internet your not gonna hurt anyone’s feelings but that about the pi is what I half thought.

only issue with the parallel port is I wont have enough I/O.
Back of the napkin mathematics says 14 output 10 input but could be 6

Spindle PWM Dir Enable / Feedback (optional)
Step / dir XYZ 6 / 2 end stops each for some reason 6 (3)
Tool change step dir 2 / end stop / sensor to count tools for some reason
DC drawbar 1 /compressed air 1 / 1 for sensor

but could still get it working limited the re do the extras later.

just wondering if their was a better option

How do you plan to handle bug fixes and feature upgrades? Do purchasers get free perpetual upgrades every time new features are added or are they stuck with the release that was active at the time of purchase? I can't see how the first option would be commercially sensible for you and the second wouldn't work for users.

Centroid have an interesting model where you can choose to pay for periodic major updates where new features have been added but otherwise you purchase is forever and includes free minor updates and bug fixes. Might be worth considering something similar?

Certainly it won't be long before some kind of machine learning / AI becomes usefully capable of this kind of feature recognition and takes a lot of the surprisingly laborious CAM off of our hands. There are hints of it already in CAM such as Fusion where you can use Claude to create toolpaths directly inside Fusion via its API and an "MCP" connector. I've done this myself and it's surprisingly powerful but at this stage it's not something I want to stop doing myself. In my experience, agents like Claude currently have the capability and dependability of an excitable junior engineer who doesn't know what he/she doesn't know. This will surely improve in the medium term.

Here's a view of the Claude / Fusion integration at work:

Parallel port.

I boot vmlinuz 3.4-9-rtai-686-rtae  (linux version 12.04 LTS) on Compaq Presario Desktop and run vi parallel cable.  I think this uses the pci 8255 driver, but not sure. 

Thank you jjdege.
Schaublin12: du müsstest die xml nur noch etwas anpassen. So in etwa:
Die Pins findest du dann in der Halshow

Em vez de seguir pela borda, a máquina faz uma curva arredondada.

Li sobre usar o comando G64 PX no início e funciona.

MAS! Fica absurdamente lento!

Existe outra maneira de obter um resultado melhor?