Forum Replies Created
-
AuthorPosts
-
ehrichweissMember
Ok, I’m a bit further along. I still can’t seem to get it to compile on Linux but I got AVR Studio 6.2 working in Windows(thank goodness for VirtualBox) and it’s successfully compiled the code as-is.
Now for my next big question, if I’m attempting to debug the code, is the Atmel-ICE(or MKII) device 100% necessary?
ehrichweissMemberNever mind. I think I get it. I’ve been working with G1 code and if I’m understanding correctly V8 hardware is now included in G2.
ehrichweissMemberI have a V8 though, how do I use the V9 instructions? Merely change any “V9” references in commands to “V8”?
- This reply was modified 7 years, 10 months ago by ehrichweiss.
September 10, 2016 at 12:39 pm in reply to: hangs due to attempted use of touch plate during program #9908ehrichweissMemberI have ran other programs with M6 in them(actually they also had a G43 in the tool macro as well even though I didn’t use it). ChiliPeppr pauses, I do my tool change and jog everything manually where it needed to be, then hit pause and it ran fine. It didn’t seem to be affected by the M6 at all in that regard. It’s only when I try to use the touch plate that everything locks up. I just looked again and I think I may have seen “G28.2” and written “G38.2” because I don’t see G38 now at all but that’s beside the point I think.
I read that thread and I was wondering if I wouldn’t be forced to run each part of the program separately. If it would be possible to make it so that the touch plate sequence can run in the middle of a program after some form of pause, that would be great. Otherwise I guess I’ll just do separate programs for each tool for now.
September 9, 2016 at 10:52 am in reply to: hangs due to attempted use of touch plate during program #9906ehrichweissMemberOh, I should also emphasize that this all happens in the middle of a program. If I do it before a program or after it, there aren’t any problems that I’m aware of. Also, jogging, and the like work just fine when I hit an M6. It’s just the touch off command, or that’s what it seems to be.
ehrichweissMemberHi, I’m using a couple of tools: Aspire and CNCWrapper because apparently Aspire doesn’t actually output code for the A axis(or if it does then I can’t find the correct post-processor). Have you made any progress on this? What post-processor are you using for the A axis? I’m willing to assist you in creating and testing a post-processor for this.
When I use CNCWrapper I get what looks like a single line across my display that doesn’t actually represent what my model looks like in the least so I have no clue if it is accurate at all. I’m certain it’s showing how the cuts are made, etc. along the line that the spindle will be cutting but without any form of representation, I can’t tell.
Any hints appreciated.
ehrichweissMemberSolved it!!
First thing, I watched this https://www.youtube.com/watch?v=K_r8y_T8rsY which got me to thinking maybe I’d been setting my $afr and $avm waaaay too low. So I tried that and it moved stronger but still the same nonsense. Then I realized that I’d never actually verified that I had matching pairs of windings for A. I’d verified X, and Y&Z worked with the same color scheme so I assumed A was correct as well. I remembered that I had some issues out of A with Mach3 and LinuxCNC but I had other issues out of both of those so I just figured it was also with them. I think someone wired my stepper connector wrong because there’s no way that the driver for A is wired that differently.
Sorry to drag you through something that I should know is a n00b error. They swore they tested this thing at the factory, I’m not convinced of that.
ehrichweissMemberoh, forgot to answer that last bit. I’m planning on cutting wood and metal.
ehrichweissMemberI tried adjusting $ajm and $ajh down to close to that of $xjm/$xjh and noticed something that I hadn’t noticed before, and not sure whether it was like that with the previous setup. The green LED for A blinks as the motor tries to move. It’s almost as if it’s not getting a full signal. Is that a product of $ajm/$ajh, or something else?
Yes, I have tested that it will move unloaded. That was one of the first things I checked because I thought maybe it had a lock that I was unaware of. The stepper is connected to the lathe chuck via a belt system. Not sure of the ratio but looks like about a 2:1 or 3:1.
Anyway, here’s the current config. I re-tested adjusting $avm and definitely if I drop it to 500, TinyG stops responding if I send any commands involving the A-axis. If I reset it back to 1000, it works just fine.
https://drive.google.com/file/d/0B2ghArPdVqfecUw2b01ROWg2am8/view?usp=sharing
- This reply was modified 8 years, 7 months ago by ehrichweiss.
ehrichweissMemberI tested it again and it has to be getting enough current or really close to it because once the motors are energized, it is incredibly hard to turn by hand. Just to make sure I wired it right, I switched 2 of my wires and it started to turn but very slowly and sometimes it would reverse mid-movement. Adjusting the pot didn’t make it go any faster. It also seemed a bit weaker so I’m guessing I wired it correctly the first time.
I read somewhere that it might have something to do with the step pulse width. Any chance that’s a possibility? I’m definitely getting closer.
ehrichweissMemberNo, it’s a rotational axis like a lathe.
ehrichweissMemberI tested those and they didn’t seem to hurt anything but the A-axis is still just humming even after I upped the power. To see if it was something in my config causing A not to move, I switched the A and Z and the A started to try to move far more than it had before but still not quite. Any ideas why that would be the case even after accounting for having adjusted the pots?
Then I realized that this particular stepper is 3amp and it’s moving a HEAVY chuck so I will likely have to use an external driver for it. I have some from my old controller so I’ll see if I can dig up the wiring on them for the power.
ehrichweissMemberehrichweissMemberI reset all my settings and got back to square one at least. I restored everything except for the max velocity for each axis and I at least got humming out of A. Then when I changed $avm to 500, I got the same behavior as before where nothing worked. When I changed it to 1000 it started working again. I don’t know if there’s a hardwired lower limit but that seems like strange behavior, and maybe a bug somewhere. I’ll investigate it later. My next step is working on the power that’s likely causing the humming motor.
ehrichweissMemberNope, didn’t fix it. I still have to reset the TinyG and at least the json server to get it to work again after that. And I might clarify that there is zero response from ANY gcode OR using the TinyG $ commands at that point.
Just in case it helps, all this is running on Linux.
-
AuthorPosts