Closed SketchThis closed 1 year ago
Hope I am clear.
Ok, that sounds reasonably simple. I didn't know that you couldn't configure afterwards like you do on GRBL, or that the motors are disabled by default... I get why, but that would have taken me a while to figure out!
I'm assuming the compiling errors I was getting in the screenshot were because I didn't have the motate directory downloaded? (I thought I did as I see some of the motate settings in there...)
Most probably the compile errors may be due to empty motate directory. Remember to use gshield option for compiling. Optionally, you can also use command line for compiling in mac. Rest, you are on right path. All the best...
Ok, I figured out the empty Motate directory, running the X Code file that was in the G2 directory, not the main directory of G2. I made a little progress, but I'm still really stuck on this compiling thing... I tried to compile a stock Gshield version from the master branch just to see if I could get it to compile and this is what happened:
https://drive.google.com/file/d/1zYeSXztFbKogHjmHGWCbOCyDb_mphR-n/view?usp=sharing
Hopefully that video explains much better what I'm failing at. I fully realize that the problem is very likely me, I just don't know where I'm going wrong... Is X Code even the right utility to do this?
Ok, bit of an update, I got it to compile, I'm not sure how but I did!
I'm assuming this is the setting(s) I'm looking for.
I see that there are settings for different machine types, ShopBot, Ultimaker, etc... If I change the default settings, how do I know that when I do a build it's going to pull those default settings? Is there another "settings for my settings" somewhere?
Also, while I do have a pinout diagram, it does note that the pins are changing a lot. The latest diagram is a lot older than this build. I feel like it's a good idea to check which pins are assigned when I build.. I looked through and found a "Motate Pins" file.. Is that what assigns the pins? I couldn't really tell from the file...
You have almost done it. Have you flashed it to due?
Sorry, forgot to mention that the settings you are in as per screenshot is right.
I haven't flashed it just yet, but I'm going to take a crack at it this afternoon. I'll post the results!
Ok, I'm getting a little closer, I was able to alter the settings.config.h file and enable the X motor, and when I compiled it worked. I also used the command line tool to flash to the DUE, so that's working as well. I'm using CNCjs to connect to the DUE to control it, when I connect, that also works (I can do the $$ command to see all of the settings, etc so I know it's working)
However, I'm still getting no motor movement. On top of that, when I issue move commands, (X1 X2, etc) the DRO isn't changing.
So for some reason it's not taking the move commands.
I see in these settings files there are a bunch for different machines. How do I know that when I compile it's using the settings file I altered? Is there a way to check/change that? I'm thinking that this might be my problem...
BTW I'm using X Code to compile...
I checked the "makefile" and I saw that it's referencing the file I've been editing:
But it sounds like from the comment above that there is an exception to this rule, with certain boards it could be pulling different settings?
You figured it right. compile time file selection is as per "makefile". For time being, please don't experiment with other settings. "Motors not moving" is the problem of settings file only as I feel. Your compiling and flashing process doesn't have any issues what I can understand from your description. Kindly share your settings_default.h so I can see if there can be any problem with it.
There's my settings file.
First I started with ONLY changing the motor_disabled value, and that didn't give me anything. Then I added some random numbers to microsteps/steps per unit just to see if I could get some reaction.
Still nothing.
I have a feeling like this is a configuration problem and not a wiring problem because I'm not seeing any movement on any axis in the DRO. Once I see that, hopefully I'll get some physical motor movement, and if I don't at least seeing it in the DRO will convince me that the board is likely putting out steps...
OK. Got it. Please replace AXIS_DISABLED with AXIS_STANDARD for x, y and z axis and use AXIS_RADIUS for a, b and c axis if you want to use any of them. Rest seems ok. Compile and flash with this changes done and share the results..Hopefully you will get the axis moving. I suggest to enable all 3 axis (motors and axis both) in one go and then compile and flash. Best of luck.!!!
Ok that worked! I can now connect to the board and get "movement" in the DRO!
THANKS!!
However I'm still not getting physical motor movement. I know my bench setup works because I can use other controllers with it. Is there a way I can verify that the pins I'm using are accurate? I'm following the posted pinout PDF, but that PDF says that there are likely pin changes. Can I see in the firmware build where the pin assignments might be so I can make sure I'm using the right ones?
I'm successfully using g2 with a Due on a milling-machine for quite some time now. I could probably check and send you some information in a few days. (But note that I'm using my own G-code-sender, since none of the GUIs I've tested worked well with g2. But this may have changed since then.)
Regards, Roland
I'm successfully using g2 with a Due on a milling-machine for quite some time now. I could probably check and send you some information in a few days. (But note that I'm using my own G-code-sender, since none of the GUIs I've tested worked well with g2. But this may have changed since then.) Regards, Roland
That would be awesome. Mainly what I'd be interested in knowing is how you have the axes wired (specifically what pins you're using).
Right now I can't tell if I'm using the wrong pins, or if I'm not getting any outputs at the pins. I suppose what I really need is a scope to check the pins on the board, but barring that making sure I've got everything setup properly seems like a prudent first step.
I'm using some basic open loop stepper drivers (cheap Chinese ones I got on Amazon for bench testing). For Step+ and Dir+ I've got them connected to pins 2 and 5 respectively. (I used this: https://github.com/synthetos/g2/wiki/Arduino-DUE-Pinout-for-g2core as a guide)
You are using right pins for x axis. So no worry. Still you can check the pulse with multimeter as you can be able to see the meter display some random numbers when the pulses actually being sent.
One thing to double check is the ENABLE_POLARITY. Depending on how your hardware looks it might be backwards. I went thru a similar situation, scoped out the signals and then as it turns out it was simply that my enable was backwards.
Does that matter if I'm not using the enable pins on my stepper drivers though? Right now the way they're setup on the bench is that I don't need to hook up the Enable positive or Negative at all.
On Thu, May 9, 2019 at 7:16 AM mhlong10 notifications@github.com wrote:
One thing to double check is the ENABLE_POLARITY. Depending on how your hardware looks it might be backwards. I went thru a similar situation, scoped out the signals and then as it turns out it was simply that my enable was backwards.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/synthetos/g2/issues/412#issuecomment-490861720, or mute the thread https://github.com/notifications/unsubscribe-auth/ABMSBPIRX3JVVZYUTUJBXE3PUQBX3ANCNFSM4HHIL2OQ .
-- Eric Schimelpfenig www.ericschimel.com
I didn't realize you are not using the enable pins. It shouldn't matter in that case.
Ok, I was worried that beyond the actual enable pins that the software looked at that setting... I'll continue to poke around at the hardware to see if I can work this out...
High jacking thread.
Roland would you share your GUI sender? Also CNCjs works with G2. Thanks for helping us out on the issues.
Riley
You should be able to make this work in the end. Running here a WorkBee with g2core on a DUE and LaserWeb4 as the gui. The DUE has been complimented with a rather trivial shield to allow easy connection to stepper drivers and end switches.
Below my config file. It's a bit long and could be cleaned up, nvertheless it;s the version that compiles without complains makes my machine move.
Regarding Laserweb4 I had to make some changes as this didn't work out of the box. Let me know in case you want the details.
`/*
// ***> NOTE: The init message must be a single line with no CRs or LFs
//* // GLOBAL + GENERAL SETTINGS ** //*
// *** Machine configuration settings
// Communications and Reporting Settings //
// Alternate SRs that report in drawable units //#define STATUS_REPORT_DEFAULTS "line","vel","mpox","mpoy","mpoz","mpoa","coor","ofsa","ofsx","ofsy","ofsz","dist","unit","stat","homz","homy","homx","momo"
// Gcode Startup Defaults //
//*** //* Motor Settings ** //*****
// MOTOR 1
// MOTOR 2
// MOTOR 3
// MOTOR 4
// MOTOR 5
// MOTOR 6
//*** //* Axis Settings * //***
// X AXIS
// Y AXIS
// Z AXIS
// U AXIS
// V AXIS
// W AXIS
/***
***/
// A AXIS
// B AXIS
// C AXIS
//*** //* GPIO Input / Output Settings **** //*****
// DIGITAL INPUTS // Set to allow the board to function if not otherwise set up // (least disruptive settings)
/* Legend: IO_MODE_DISABLED IO_ACTIVE_LOW aka NORMALLY_OPEN IO_ACTIVE_HIGH aka NORMALLY_CLOSED
INPUT_ACTION_NONE
INPUT_ACTION_STOP
INPUT_ACTION_FAST_STOP
INPUT_ACTION_HALT
INPUT_ACTION_RESET
INPUT_FUNCTION_NONE
INPUT_FUNCTION_LIMIT
INPUT_FUNCTION_INTERLOCK
INPUT_FUNCTION_SHUTDOWN
INPUT_FUNCTION_PANIC
*/
// Xmin on v9 board
// Xmax
// Ymin
// Ymax
// Zmin
// Zmax
// Amin
// Amax
// Safety line
// DIGITAL OUTPUTS - Currently these are hard-wired to extruders
//Extruder1_PWM
//Extruder2_PWM
//Fan1A_PWM
//Fan1B_PWM
//SAFEin (Output) signal
//Header Bed FET
//Indicator_LED
// PWM Settings //
// Heater Settings - relevant to 3dp machines //
// DEFAULT COORDINATE SYSTEM OFFSETS
// Tool Table Defaults //
// User-Defined Data Defaults //
`
Not sure where you're at in this, but you should change the power level to your motors.
Change that too M1_POWER_LEVEL 1.0 and all other motors of course M2 etc... That should give you motor movement.
Hey all, I'm graduating myself from GRBL and looking to build a 5 axis system.
I've built several control systems before, GRBL included, but this is my first G2 system. I was drawn to it after using (and owning) a Handibot that's got G2 on it.
My setup right now is a bench test where I've got 5 stepper drivers, 5 steppers, some limit switches and a relay board. I've also got a Due, and will be using CNCjs on a PC/Raspberry Pi.
Here's where I'm stuck: I flashed the Due with this: https://github.com/synthetos/g2/releases/download/101.03/g2core-TestV9-g2v9k-101.03.bin
I used Chilipepprs online hardware fiddle to do it (because it was so easy) I've got the Due connected to CNCjs and they're talking just fine.
I used the pinout diagram I found here: https://github.com/synthetos/g2/wiki/Arduino-DUE-Pinout-for-g2core
When I wire in any of the steppers I'm not getting any movement of any kind.
I suspect that it's because I flashed something that wasn't configured.
I've got the repository cloned, and I have X Code installed and I'm looking through the files to see if I can figure out what the stock setups/pin assignments are, and I can't seem to figure it out. I've also looked all over this github, and I just can't find the information I need to compile a version for my needs.
I tried doing a test build with X Code and I'm getting build errors even when I haven't made any changes to anything:
I'm either missing something obvious, or because I'm not actually a developer it's just not making sense to me.
Could someone head me in the right direction?