Writing and Testing 'Stuff'
-
@nightowl IMO, you can't really beat having a real, functioning machine. Sooner or later, you'll have to test your "stuff" like that in any case. A trick I use is to simply drop the belts off the motors. That way, everything works except homing but no damage will ensue if I do something stupid. If your CNC is screw driven, you might have to disconnect the couplings rather than the belts.
-
The cheapest board running RRF 3.4 these days is the BTT RRF 1.1 -- it runs the STM port, which works fine.
That said, I agree with @deckingman that you will eventually have to have the actual machine connected, otherwise you'll only make some motors spin. And just droppnig belts/disconnecting leadscrew couplers gets you a long way. As soon as you want to try out endstops etc. you will need a functional motion system though. What you can do is replace the spindle with some variable voltage light to emulate that.
-
@nightowl said in Writing and Testing 'Stuff':
the existing board is located a long way (in the workshed) from where I can comfortably sit
Sorry, I ignored the fact that a CNC doesn't fit well with the furniture of your living room - of course, my 3D printer can sit on the same desk with the iMac. Now I understand your need of a second board to test things out. However, @deckingman is right when he states that you'll need "the real thing" for some tests. Hm … what about a macBook and some comfortable arm chair in your shed?
-
@infiniteloop said in Writing and Testing 'Stuff':
.................. Hm … what about a macBook and some comfortable arm chair in your shed?
Or an IP camera
-
-
I think I may not have explained properly is that I want to write macros and config files in my comfy chair (Oh no! Not the comfy chair!) with the CNC machine in the workshed.
At the moment (unless I've completely missed something) I can only edit/review existing files when the Duet controller is powered up.
It's taken quite some time to fettle the mechanics of the machine to make sure it's square in all three planes and flat, so I really don't want to start disconnecting couplings, stepper motors or making any other physical changes.
No, all I really want to do is develop my existing knowledge and learn more about meta commands and how they work - or don't. At the moment, the CNC runs as it should - with a lot of help from here, I might add - so I just want to enter an experimental stage
without affecting the CNC.Oh, and I would never leave a CNC working on it's own, with or without a camera. Things happen far too quickly with motors spinning at 20,000rpm with a piece of sharp steel in its jaws and lumps of wood/metal flying around the place!
Few things are more dangerous than taking the advice of someone who thinks he knows what he's doing.
I'm still on my learning curve, so take everything I say with caution!RatRig 1075, Duet3 MB6HC, Sorotec SFM 1000 PV-ER milling motor, Hobbyist
-
When I started out with Duet's I had a test setup built on a piece of MDF.
It included the board, steppers, endstop sensors, heaters, fans, etc.
The steppers didn't move anything but I could verify and test operation.
In the same way the other parts didn't actually respond to axis travel, heat hotends, cool parts, etc.
But I could experiment with GCode and observe the results.
Frederick
-
@nightowl said in Writing and Testing 'Stuff':
.................... At the moment (unless I've completely missed something) I can only edit/review existing files when the Duet controller is powered up................
Ahh, if you think that then it puts a different light on things. You might want to consider adopting a strategy similar to that which I use.
Firstly, your SD card will fail at some time in the future. It's not a question of if but when. So you need to have a backup of all your files. Secondly, if you have a copy of everything on your SD card, you can edit those files to your hearts content without going anywhere near your machine.
What I do is maintain a copy of the entire contents of my SD card on my PC. This is backed up to both a local NAS as well as cloud storage. I only ever make changes to the files on my PC and then upload those files from my PC to my printer's SD card - never the other way.
So I suggest you do the same or something similar. There are numerous way to backup your SD card but possibly the easiest is to simply remove the card and insert it into a computer of your choice, then copy the contents into a new folder. The files themselves are simple text files so you can use any text editor to make changes. I use notepad++ but there are numerous alternatives. Once you have finished "writing stuff" you can then upload the files to the SD card via DWC to test them on your machine.
-
@deckingman
I get all that, but backing up the microSD card is something I also want to do (step in here anytime, @fcwilt!), but not by taking the card out of the controller. I'd only do that if I really had to, e.g. a catastrophic failure!No, the real point is to run stuff within a protected environment before trying it out "in the field". I like the idea of a "test bed" machine, as per @fcwilt's post, but I don't have any spare hardware - yet!
-
@nightowl said in Writing and Testing 'Stuff':
I get all that, but backing up the microSD card is something I also want to do (step in here anytime, @fcwilt!), but not by taking the card out of the controller. I'd only do that if I really had to, e.g. a catastrophic failure!
As you may have noticed the FTP file transfer to and from the Duets was having some problems.
The firmware folks found the cause and have posted a fix. I just got back from a trip and haven't yet been able to test the fix. I hope it solves the problem because uploading/downloading files using FTP is very simple and beats removing the SD card. I've broken two of those tiny things.
Frederick
