Jogging (either specifying a distance or using the mouse jog) works. I see activity in the console and the activity LEDs on the drivers are blinking.
Ah, some good news.
Can your run the chillipepper logo Gcode (in air)?
Perhaps the toolchain does not like your Gcode?
… Nevermind. This is turning into a endless circle. I’ll switch back to GRBL.
Sorry to see you go, but then when you need to get something done, you use what you know works; been there before.
The good news for me is that 75.02 now builds on Linux, at least for DUE.
I realized during this discussion that the Linux compiler issues may be specific to the device used in tinyGv9, which is a variant on the part used in DUE; it was not 100% clear.
Heh after all that it turn out to be a setting in CP. ‘When Playing or Stepping send gcode commands to > Serial Port (Default). For some reason it was set to ‘3D Viewer’. Dunno why. It was set that way as 5mins ago was the first time I’ve even seen that pref. pane.
@y_milord Wow, maybe I should throw up some kind of alert if you’re in that mode because it’s such a rare mode for folks to use these days.
Is there a way in CP to jog a 4th axis (A)? Or do I have to fire manual gcodes at it?
Sadly no way to jog 4th but could be easy to add keyboard shortcuts in the axes widget if you want to fork it
Ah okay. Thanks for the quick reply.
One last question and after this I should be good to go.
I have all the axis configured with-in TinyG2. X, Y1, Y2, Z & A. When I run my gcode everything works great. In the TinyG config (with-in CP), It only shows Motor 1-4 and not number 5. I know this is superficial. As I can manually config motor 5 via the console or re-compiling the FW- But is there a way for it to pull the config data for it and populate/create Motor 5 (with-in CP)?
I think you’re referring to Kevin Hauser’s config popup modal window that is reached from the cog wheel icon in the TinyG widget. If so, I suggest you fork his widget by using the upper right corner menu of that modal dialog. Then add the motor 5 tab (i’d add a motor 6 tab as well) and send Kevin your changes. He could integrate. I would suggest though that you only show these tabs if you detect that a user is on the v9 platform so it doesn’t confuse normal v8 users. You are now one of the more advanced users out there. BTW, we could really use a video tutorial on getting the Due going. Even I have not done this yet.
I’ll document what I did when everything is installed (as in move this mess of wires off my desk to the unit in the garage)
Now the noob question of the day. I’ve made the changes in jsfiddle. How do I get that to CP? (Sorry, Hardware guy)
Send me the link to your JSFiddle and I’ll merge.
http://jsfiddle.net/ymilord/utondrh3/
I’ve added all 6 axis as suggested and added/created a ‘b” axis.
Oh, you changed the config modal. @Kevin_Hauser will have to be the guy that merges the changes. Kevin, you up for adding the additional tabs?
Was that not the one I needed to change?
Oh, I thought you were going to add jogging for ABC axes to the Axes widget and possibly a DRO readout mimicking the A axis.
Ah. I can still do that. But before I was talking about the config section.
I’ll give this a try tonight … do we know it works with “regular” tinyg’s as well?
Is there a way to add this to my environment?