Here is a link to my 100.26 gshield build last July. https://drive.google.com/open?id=1gXrVtmXIs3ykIp8mBbOicUGUq1q93CUg
Have a look here, https://plus.google.com/108078671773315527328/posts/eoQT6tYGpkx
Wow! That one works!
Very interesting. You built this on a linux box?
Strange. The Macintosh Xcode project builds without error yet produces a binary that doesn’t work.
Is anyone here successfully building a 100.xx branch from the Xcode project?
@cmcgrath5035
Correct, the binary was built in July using gshield-pinout.h (after the Issue 272 revert) and https://github.com/synthetos/g2/blob/edge/g2core/settings/settings_shapeoko2.h because my typical machine is close to this setting file.
I see no obvious reason why it would not build the same today.
Yes, my builds all using Linux.
Did you remember to ‘make clean’ before your build? The Synthetos Devs typically work on MAC, so I would be surprised that there would be a hidden build issue there.
By the way, here is the ‘?’ response I got back in July $
{“r”:{“sys”:{“fb”:100.26,“fbs”:“100.26-1-g3a7f7”,“fbc”:“settings_shapeoko2.h”,“fv”:0.99,“hp”:3,“hv”:0,“id”:“0084-e739-18c6-08c”,“jt”:0.75,“ct”:0.01,“sl”:0,“lim”:0,“saf”:1,“m48e”:1,“mfoe”:0,“mfo”:1,“mtoe”:0,“mto”:1,“mt”:2,“spep”:1,“spdp”:0,“spph”:1,“spdw”:1,“ssoe”:0,“sso”:1,“cofp”:1,“comp”:1,“coph”:0,“tv”:1,“ej”:1,“jv”:2,“qv”:0,“sv”:1,“si”:250,“gpl”:0,“gun”:1,“gco”:1,“gpa”:2,“gdi”:0}},“f”:[1,0,2]}
I agree with you that Issue 272 appears to have been resolved back in Sept and have flagged that to the Repo owners.
I’ll try a ‘make clean’ and report back.
A clean make results in what is reported as a successful build. When I flash this to the Due and connect it to CP, CP sees it and can talk to it, but movement commands do nothing. I connected LEDs to the step, direction, and enable pins, and the Xcode build always leave those pins low.
When I flash your build to the Due, the LEDs all behave as I would expect, and when connected to my stepper drivers can run the motors.
So the problem appears to be with the build process on my machine. I’d love any suggestions as to how to proceed with debugging this issue.
For Build Debugging I suggest you open an Issue at https://github.com/synthetos/g2/issues
Be a specific as you can as to process you used including your make command line
On Linux, the make process will check your resources and download components, such as compiler version as part of the build process.
I do see a couple other “tweaks” made to the repos on GitHub since I built. Perhaps they introduce an issue?
Thanks! I’ll try there.
Well that was a little maddening. So it turns out that the “gShield” Xcode build target is some kind of test configuration with the motors disabled, and not a target that can drive a gShield. I think that’s confusing and I don’t understand why it would be set up that way.
Creating my own CONFIG that enables the motors has now got me a working g2core 100.26 build that can drive my mill.