This is the pinewood derby car side that i was attempting to cut.
This is the LinuxCNC logo gcode that they default load.
This is the pinewood derby car side that i was attempting to cut.
This is the LinuxCNC logo gcode that they default load.
The following are a cut and paste from my personal log on the milestones as I got the CNC working. I figured I’d paste them here since rewriting them wasn’t going to be much more interesting than their content as they stood.
A few notes though:
A very cold week of negative temps prompted me to find a propane fired heater for the garage. Unfortunately, Home Depot and Lowe’s both were sold out, as it’s seasonal and that’s all they were shipped. OK, I get that it’s a seasonal item, but seriously, I live in an area of the country that’s cold during the winter, and you only had 5 heaters? And you won’t get any more for the entire year? It’s not May, it’s January! There’s at least three more months of cold. Sheesh, you brick and mortar stores don’t want to lose business to online retailers, but you refuse to restock, then I have no choice. ACE and other stores in the area likewise were out. OK, a visit to Amazon later and it was on it’s way. Prime is an awesome thing, and today I unpacked and fired up the propane heater. Aaaaaah. Very nice. Just need to make sure to keep vented.
First movement! Got the right signal out on Z-axis step. It only moves in one direction though, which makes me think that the z-direction isn’t being toggled. I’m using the “Test this axis” in stepconf, so it jogs it back and forth. Also in AXIS gui, trying to jog the z axis doesn’t go but one way.
Spoke with Seb about it (Seb is my friend that is one of the active developers of LinuxCNC). Learned a few new things about LinuxCNC, and the halcmd shell that allows you to toggle stuff. Also about HalScope and HalMeter. He definitely agrees that it needs to be scoped out from the PC down. Looks like that’s the next step because there’s no other way to tell. Good thing I have a scope… Also spoke about the weird power issues. Turns out it might not be the right pin being toggled for the Amplifier Enable pin.
Tonight I used the scope and traced the signal for Z-axis direction out to the driver. The steps are making it through, but the direction isn’t. Well, you can plainly see on the scope, the signal goes into the optocoupler chip, but not out. It’s a fried channel on the optocoupler. Dunno if it’s from rough ESD treatment or just plain failure, but it’s needing to be replaced. Hello Mouser, here I come again. Sucks to pay shipping on a $0.70 part, and it sucks that a $0.70 part is hanging up the show. Oh well, I have other things I can test out.
In my friend Jim’s config, I noticed that he didn’t slave the A axis to the Y, he just set the Y pins (step and dir, inverted for dir) to Y’s nets. So that’s what I’ll do too.
Also changed pin 1 to be Amplifier Enable like Jim’s config has. That seems to solve some of the strange power control issues.
Got X-axis to move. I don’t know why the pins aren’t changing for pin 8 and 9 which is what I also have Y-axis step and dir mapped to. The pins off the port aren’t changing, so it’s not an issue with the board.
Working with the “gold brick” Asus Aaeon industrial PC, installing a SATA drive and putting LinuxCNC 2.6 on it. Wifi issues abound. As it turns out, through the various machinations, it’s somehow a problem of interference between the Parallel port card that was installed and the wifi card. I don’t know if it’s a PCI conflict, since the parallel and mini-pci wifi cards are both on the PCI bus, or what, but every time I pull the Parallel card it works, and when it’s reinserted, it doesn’t. Who the F knows. Ordered a PCIe wifi card tonight to avoid having a USB dongle hanging off of it, to give it a bit more mechanical stability. It needs the duck antenna if it’s going to be out in the garage, the little USB plug that I tried from Edimax loses packets because there’s too much interference.
Wireless PCIe card arrived, installed it. No problems connecting. Must have been a PCI conflict of some kind, possibly both slots shared the same electrical connections. Also installed the new optocoupler chip into the driver carrier board. No dice. things still not working the way they fully should. I need to spend some more time on it, but don’t have it tonight. Got the internet connection up, so I’m happy about that at least. Now comes the tough part of getting the board debugged.
Wahooooo! All three axis are moving, all four motors! The transistor for the z-dir pin optocoupler was disconnected. No connection even though the trace is there. Some sort of defect keeps it from being connected. A bit of wire wrap wire and some solder got it working. So I didn’t need a new optocoupler chip afterall, but whatever. I didn’t expect the trace to not be connected. Also, Stepconf wizard doesn’t understand sending the same signal (y-step and y-dir) to two sets of pins, so it only moved one motor not the two of the Y axis gantry. After getting the config written, AxisGui had no problem with the signal going to two motor controllers.
Used Pololu current setting document to setup drivers. Drivers running much cooler now. Each driver will measure at 0.70 of what they really are pulling, so when you want to find out what current they’re really at, you need to multiply by 1/0.70, or 1.4 of what’s showing on the current meter. Set trimpots and got the three axes on the right current. Drivers and motors both happier now.
Built small fan shroud out of strips of scrap ABS plastic. Smaller fan now blows directly across the heatsinks of the drivers and in the right orientation. Drivers are warm, but never burn-your-fingers hot now, due to this and the current adjustments. Now the biggest frustration lies in making it accurate. It doesn’t step right.
Found out that the switches that were installed on my control panel are wired correctly, it’s just that the 48v power supply that I bought has a ground fault in it (as evidenced by having only ground and hot hooked up, and it still tripping the GFCI). Every time power is applied to it, it trips the GFCI. Ordered a new one.
Wired up the new 48v spindle power supply, tested with the spindle and the motor controller. All in that chain work well. Got the control panel wired up with the new power switches, and all the wiring tidied up and looking good. Used a new step-down powersupply to drop 24v down to the 6v that my fans require. They’re 12v fans, but I wanted them to be quieter. I used a 6v power brick, but it means that it’s switched on and off different than when the motor drivers are. It’s easier that if they get turned on, so do the fans at the same time.
Got it to step smoothly. It’s now needing to have it’s carving space defined so that it can run programs. Might need to ask for help on that, but I’m also taking apart Jim’s files to see if there’s something there that could clue me in. Need to start coming up with artwork or at least some designs that I can run through a CAM program and generate some ngc files.
Update – got it to trace out the sample LinuxCNC ngc file it comes with. I still need to do work on scaling it so it can be accurate, and getting the Z-axis right. I’m not sure what I’m going to do, it needs to know where it’s home is, and I think I need a switch that is actually on the top for home, with the bottom being limit. Otherwise, I’m not sure it will carve right.
Early morning, got out to the CNC machine and tried more configuration now that I had used Seb’s G54 knowledge. Messing about with configs, I was able to get it accurate, for the most part. But now I need to get it tuned, because it’s close, but not enough. Z-axis remains a pain in my ass. I need to get it’s soft limits set in.
Problem now exists where it’s skipping steps or stalling on Z. While it works, it doesn’t work well for Z. Start looking into SMI and other possible reasons for stalling or skipped steps.
(Turns out, the gold brick just wasn’t awesome for this application, it had a horrible latency histogram, as found by the latency-histogram tool. This is part of what I’m referring to in the comment about SMI above. I won’t explain that here, it’s better explained in the LinuxCNC docs. I eventually had to go back to the HP Pentium4 desktop PC I was using before I obtained the gold brick.)
Installed new USB wifi dongle, it works. Continuing with removal of PCIe wifi card and inserting a PCIe video card. Tried several from the stash, settling on one that supposedly doesn’t do too much better than the Intel G945 one that’s built in. Ha! Launched and played around with Axis GUI and it’s fluid. FLUID. Not this chunky crap that the Intel one had. OK, it stays in.
Spent time rebuilding the gold brick. Long story short: nouveau driver works, but is broken. Predictably broken, but annoyingly so. It’s workable. What isn’t is the nVidia drivers. Because of a problem with a GPL symbol, the driver wouldn’t compile. and left the system in a crippled state. Had to copy off my crap and rebuild to get it back. Not happy. Tried again, but it had the same effect. Finally reverted back to nouveau, and sticking with it. Wasted too damn much time on it.
Talked with Seb, he thinks that latency issues aren’t to blame for the z-axis missed step/stalling. he thinks it’s an issue with the threaded rod possibly. This was something he mentioned after I mentioned that the noise was coming from the center of the carriage rather than the motor. Sooooo, time to take a critical look at the entire axis and see if it’s got mechanical issues.
After getting the Z-axis re-aligned again, I was able to see a correlation I hadn’t seen before: when the Z motor was jogged when the Axis gui was set to a high jog rate, it seized. I always had to drop the jog rate because it would just go too fast. I discovered that slowing down the velocity and acceleration for the Z-axis significantly allowed it to move the axis without seizing and losing steps. In other words, the acceleration and velocity were set too high for the motor to handle it, and so it wasn’t a latency issue, it was that the motor just couldn’t move fast enough. once those values were turned down, the axis didn’t lose a step. After this, I was able to get the system using a sharpie without ramming it into the bed. Of course, I also had to learn that the LinuxCNC sample gcode has the 0 for the z set at 2mm above where it puts the tip as it’s moving. When I accounted for that, I got the right results. I also created a spring loaded pen/pencil/marker holder so that I can use pencils in the CNC. Works like a charm. I set it to move on 5mm increments, and it does. It’s now fairly accurate. Next step is getting some Gcode put together and attaching a spindle. I might use my dremel tool to start, so that I can see how it goes before putting my more expensive spindle in harms way.
Z axis is driving me nuts. Damn thing can’t move faster than 632mm/min without seizing and stalling. And what’s worse is it seems every CAM program doesn’t get that on evac out of a cut, the Z can’t move that fast and needs to go slower. I’ve tried editing the gcode, to limited success. I took time to figure out how to adjust that with Cut2d, and CamBam.
Installed the T-Nuts and got the wasteboard zipped down to the frame using 10mm M4 BHCS and drop in nuts. Used the Forstner bit and went 7mm deep, leaving 5mm of it to grab onto. Now I need to cut some hold down pieces to use with the T-nuts.
Tore down the Z-axis in anticipation of replacing the screw drive. I had thought it was bent by the way it wobbled, but it turns out it wasn’t. It was how it was fastened together. Only by tearing down the Z could I also figure out (now that I had something to drive the motors, unlike I did when first installing it) that the high jog rate would stall the motor even without the load of the carriage and the screw drive. Implemented a much better limit switch solution, got it so the carriage can now travel the full negative z. This gives me a z axis length of 57.5 mm.
CAM is a nightmare. I’ve tried many of the different packages, free and commercial demos. it’s a nightmare to get a usable piece of software, but it’s also a format nightmare. Even when you get a usable piece of software that isn’t cryptic, it may have issues not being able to read the drawing files you need to hand it. Some allow you to route “on the line” instead of to the inside or outside of it. Others won’t, and if you want to it’s an “engrave” operation. Oy.
My selection criteria are:
Ones I’ve tried:
What I’ve used to draw with:
I’ve learned that DXF isn’t always a DXF that is compatible. Apparently, as my friend who works for a CAD vendor said, “welcome to the hell of CAD file formats”.
(I finally settled on CamBam. I’ll probably do a post purely on that, there’s much to cover. It’s $149, it does all of the simple and all of the complex stuff that I’ve thrown at it. And above all, the guy that wrote it allows you 40 free unrestricted uses, which helped me while I was attempting to get things working and not have to worry about plunking down the full money for it until I did. If you’re looking for a CAM solution, I highly recommend CamBam.)
I was able to get the SVG to DXF script to work, and was able to get my daughter’s request (“LOVE” drawn out) done with pink marker. She was happy, but so was I: finally able to get inkscape SVG drawings into CamBam. So this looks doable. As for 3D? None of them seem to be easy to get a 3D STL file mapped out, except for MeshCAM. I would be willing to spend the $250, if and only if it made it easier to do 2D and 2.5D CAM, but it doesn’t seem to. Since the majority of what I’ll be doing is 2.5D, CamBam is more appealing as it is easy to get paths laid out. It does 3d too, but i haven’t had much luck with it yet, and can give it time since that’s not the primary focus of my CAM experience.
Tonight’s the first cut! Started with a 1/8″ end mill, in the spindle with about half the speed it can go, and did some cutting using manual jog. I was attempting to use it to cut the side of a pinewood derby car, since my daughter wants an ice cream sandwich for a car and I needed to cut down the side of one. After failing at this miserably, I decided to get a piece of 1/4″ MDF cut to the right size, and give the good old LinuxCNC logo a try. Set to a height off the surface of 1.5mm, this meant it would (should) cut .5mm deep, since it plunges 2mm on that program. It finished without an issue. WOOOOT!
Wiring is a pain. One of my friends at the hackerspace that had built his Shapeoko2 mentioned that assembly was the easier part, the hard part was wiring it up and he was right. Included in this work was also figuring out how the power supplies and the other bits would be arranged. OK, it wasn’t that much of a pain. It was fun trying to figure out the layout of the power supplies and the control boards, as well as where the emergency shutoff switch was going to be located. It was one of those moments where you look around for what you have on hand, because you need to solve problems you didn’t know you had until you run smack into them. McGyver moments if you will. A few examples are the fan shroud, the cable strain relief, limit switch mounts and the e-stop button.
It starts with a slab of particle board as the base of the layout. This section of board is meant to be somewhat detached from the table, so that I can move it in and out as needed to service various parts.
I had to figure out how to mount the e-stop switch as well as the spindle speed controller’s pot. I decided to make myself a slanted control panel. I had some of the black plastic you see in the picture, already cut at a slant. I grabbed a piece of clear acrylic and slapped it together with some glue. The best solution isn’t always the prettiest. Over time this panel has grown to include the master power switch, the lights, motors and spindle switches. At some point, I may re-engineer this panel, including using the CNC to machine it’s own panel, complete with engraved labels. But that’s off in the future.
Cable strain relief
Had to get inventive on this one. I needed a way for the cables sticking out of the side of the machine to be strain relieved so they didn’t damage the motor controller board if they accidentally got yanked on. It doesn’t happen that often that something falls or something gets caught on the wires, but once is enough if there’s nothing there to hold it in. The mounting board is a bit of acrylic, which I solvent welded a thicker chunk of acrylic to. With some holes in the thicker acrylic, wire ties can now be used to keep the bundles from being yanked out of the screw terminals. To date, it’s saved the controller board terminals at least three times. The bluish colored blobs are epoxy putty (love the stuff, so useful) which the aluminum stand offs are stuck into. This solves the problem of mounting the circuit board to the acrylic strain relief board, without having to counter bore the underside to use screws. Simple and effective.
The NEMA23 motors for the X and Y axes required a gauge that could take a continuous load of 2 amps. I decided to use a flexible 16ga speaker wire, I needed the flexibility for movement, and although I technically could use 18ga, I tend to over engineer. Monoprice had a wonderful deal on a 100′ roll of 4 conductor speaker wire for $40. This gave me enough with spare. I used 12ga solid core conductor from the power supply to the motor controller board, because it could carry a max of 34 amps.
Cable chain mounting
I finally figured out that I could use a salvaged block of HDPE to mount to the side of the X gantry and attach the cable chain head to that. A bit ugly, but it works well. The cable chain for the X carriage is less sophisticated, and at some point in the future, I’d like it to be a proper cable chain, but at the moment the woven cover is good enough.
The limit switches I bought came on these little circuit boards and while they looked nice, there were two problems: they were wired up wrong for my electrical setup, and they got in the way. I had to throw them out, they just wouldn’t work. So I desoldered the switches off of them and decided to mount them myself with a few pieces of plastic. I over engineered the switches mounting plates. I figured you couldn’t just glue them to the plate that you screwed onto the rail, because over time the pushing on the switch might crack the glue. Thus I used #1-72 screws. If I’d thought harder, I’d have realized that it’s total overkill because if your limit switches are taking enough strain to crack glue, then you’re doing something wrong. 😉
Stepper drivers get hot. Like burn your fingers hot, and that’s even well before they hit their melt down temp. They definitely need cooling if you want to use them long term (longer than a few runs of the CNC that is). My first attempt was poor, because even though the fan was sitting on top, it wasn’t blowing across the heatsinks in a way that would maximally remove the heat. Eventually I threw out this shroud in favor of a shroud I created from some scrap ABS, a server fan and a bit of glue and epoxy putty. Even at full tilt, the motor drivers are kept well ventilated and they do well.