Built a new controller app - feedback wanted

Yep - rapid is already in here!

Keyboard shortcuts are on the list:

Yep! As Cullen mentioned, I have the specs for the Pro XXL and those will be in the next version (probably tomorrow night). The size is the total work envelope, or basically how far you want the spindle to move in any direction.

The tool sync seems like a hot topic! I already have it on the list. I’ll probably start with Fusion, but will support Vectric, too.

2 Likes

Ok. I took a quick look at the header of the file and it indicated SQLite so I downloaded a tool to open SQLite and it seemed to open ok. I have not dug into the structure yet.

You are a better tech than I !

I wouldn’t go that far. I am a DB kinda guy but don’t know anything about TinyDB or SQLite. Maybe they are related.

I avoided db’s in my job. If it had geometry, I was in

@cryptyk You should see if you could add tool changing capability utilizing the rapid change atc (rapidchangeatc.com) I know it is compatible with gsender specifically, would be cool if it worked with your controller.

Ryan,
run the fabulous piece of SW first time.
Absolutely great!
You asked for feedback:

  1. would be great to import CC native format*.c2d, to avoid the need for gcode. So far this excludes users of the free CC, since gcode export is for CC pro only. Also would make it easier for CC users, spares them a step of work.
  2. Went to pause in the middle of the project. Had to be chased back to work manually. Bug or feature?
  3. It is my impression that the device does not necessarily start at the set zero, for X, Y and Z. Please check. There is probably an offset in all dimensions.
  4. Users IMO should be aware that the definition of the bit from CC is not imported into AxioCNC. The bits need to be defined in AxioCNC, I am not sure how the bits one defined in CC are exported to AxioCNC, and I do not see an option to import custom bit -and bit properties, feed and speed…- definitions into AxioCNC database. That is a lack of CC/CM too, any change in bit default settings cannot be automatically transferred to CM, and even less with AxionCNC.
  5. I cold not find bitsetter options, and I did not find an option to run the bitsetter before the cut itself after defining zeroes.
  6. I stopped my cut before I had the chance to see how the bit change would be performed. Without info what bit should be used I wonder whether that would go smoothly, I could start the cut w/o being asked to fasten the bit needed.
  7. Obviously the size of the wasteboard and the Z-gate (precisely: the distances the router center can travel) are the only values to be entered to define the machine? Therefore IMO it is not necessary to define every single machine out there from your part, that should be easy for any user.
  8. can’t get the carbide3d pendant running.

Again: great, absolut wonderful piece of software engineering!

This here are just my 5ct.

1 Like

Thank you for all of the feedback! I just released a new version (0.0.89) that completely rethinks the zeroing system.

  1. I’m not sure if c2d is an open format. If so, I’ll try to support it
  2. Pause might be from a tool change?
  3. The new version (v0.0.89) completely changed the way zeroing and probes work! It’s much cleaner now!
  4. I’m going to add the option to import bits, and also to read them from the comments in the gcode
  5. BitSetter is in the settings under “Zeroing Methods”
  6. Tool change should work very smoothly now
  7. Yes, but I like giving people the dropdown presets to make setting things up easier
  8. The pendant isn’t supported :frowning:

It didn’t have the slash through it, so it seemed to install, but Mac didn’t like it…