Posts made by Ryan Lock

Thanks for tagging me @T3P3Tony. I can confirm Buffalo CNC are Not related to Ooznest in any way. The connectors on that Duet have a yellow tint, ours do not look like that.

@EasyTarget Haha i will figure it out

@EasyTarget Thanks for the suggestions, i will take them all on board. I have had a few other people prefer the bullseye approach to jogging as well. I have stuck with the current Duet Web Control jogging in our control to speed up production. But definitely something for the future. I have also got a lot of request for keyboard jogging.

Thanks for the suggestion i will see what i can do.

Thanks for the info, their system is pretty nice! I like their graphics to see which layer you are on.

Mine is simply just a drop down list which allows you to select which one. On one of the settings page i am hoping to add a panel where you can see the work zero for each system in machine coordinates, edit them, and give each system a custom name, which will then show in the drop down instead of the number.

@Danal I haven't got any to hand right now, but will make some

@EasyTarget Yeah we have found for users doing production manufacturing they require easy use of all work coordinates. After the release of this version, the next thing i am going to add is the ability to apply custom names to the systems, instead of just numbers.

Yup you can find it here: https://github.com/lockryan/DuetWebControl

Hey, as above DWC only displays work coordinates of the system you are currently in. That homing position is the same as what we use on our CNC Machines. I am currently making an alternative web control for CNC Machines which puts all the buttons needed to hand and allows easy switching between work coordinates. You can download the beta at: https://learn.ooznest.co.uk/Wiki/WorkBee_Firmware_Releases

@jzagaja There is nothing stopping you from doing it as the Duet can control a 3D Printer. But i always advise to have a separate CNC Machine and 3D Printer. The mechanical hardware isn't designed for a 3D Printer. And 3D Printers need to be clean, CNC Machines are far from anything clean

Hi David,

Sorry for the late response on this.

Yes it is 53 1/3 exactly.

Changing it to 53.333333 did allow movement from the homed position on all axis. However when getting to the other end of the travel, you could never get to your absolute minimum on the axis with 53.333333.

So putting the G92 command in the homing files is the best solution to this.

Best Regards

Ryan Lock

Hi David

Not a problem. Yes i did notice it didn't display the error but refused to move. But if i remember correctly switching back to the original web control it showed the error. So i presumed that was a bug in the new gui.

A fix would be great.

Best Regards

Ryan Lock

Hi David,

Please see attached. I have also attached our homeall file.

Best Regards

Ryan Lock

1_1552643858526_config.g 0_1552643858525_homeall.g

It also affects the Z-Axis. And stops homing of individual axis for the X and Z. For example:

G91 ; relative positioning
G1 S1 Z94 F1500 ; move quickly to Z axis endstop and stop there (first pass)
G1 Z-3 F2400 ; go back a few mm
G1 S1 Z94 F300 ; move slowly to X axis endstop once more (second pass)
G90 ; absolute positioning

Gives an outside machine limits error. Same for the X-Axis. But on the Y-Axis it works, even though it is the same code, except Z replaced with Y.

Ryan

@dc42 Sorry just got round to testing 2.03Beta2, and the bug is still present.

Hi, I just wanted to see if a unified scheme for restore points was sorted? And that restore points will now go back to the correct position for the work coordinate systems, without having to manually select the work coordinate system before resuming?

In addition, I was testing the power loss resume today, and it seems that it ignores which coordinate system was selected when the file was running. Even manually selecting the coordinate system before resuming doesn't seem to work. I tested this today on 2.02 RTOS

Ryan Lock

Hi,

With the M453 command in the config.g file, with no parameters. After homing the machine, the X-Axis cannot be jogged as it gives an out of limit error. Even though the command would be well within the limit of the machine.

However if you then to proceed to jog the Y-Axis once. Then proceed to apply the same X-Axis jog command which gave the error previously it now works.

Removing M453 from config.g, and the issue goes away.

Firmware version 2.02 RTOS.

Ryan Lock

Hi @magdi,

Thanks for posting your config.g file and the model of your motor. You want to see it to no more than 1.45A.

That error normally relates to a wire being disconnected or not properly connected. As DC42 suggested try the known working X-Axis wire with either the Y or Z-Axis motor.

If that fails try plugging the known working X-Axis wire AND motor into the Y-Axis or Z-Axis port.

Best Regards

Ryan Lock

@dc42 Thanks for making them changes. I have tested it out and it all works as expected.

One other thing i have noticed is that when pausing a file, and then resuming it, the machine goes back to machine coordinates and forgets which work coordinate system it was in. The way to solve this is to select the work coordinate system at the start of the resume.g file. Selecting the work system through the g-code console while in pause mode doesn't work, it has to be set in resume.g as far as i can see.

The effect of this is that the pause button can only practically be used in one coordinate system. As to use it in the others would require the resume file to be changed to select the correct one before resuming.

I am sure that before i upgraded the Duet to the latest firmware version it used to remember the work coordinate system when paused.

Ryan

Option C would be best in my opinion. If a user wants the coordinate system to autosave, they can setup macros to send the command and then autosave.