Forum Replies Created
-
AuthorPosts
-
niklasMember
Thanks a lot for the links. Got everything running by reading through the discussions.
The problem turned out to be that the regular touch plate widget in Chilipeppr uses machine coordinates and I had machine coordinates limited with to 0 on Zmax. When it tried to move upwards, the widget zeroed the Z axis, tried to move upwards from Z0 to outside of the machine limits, and in return g2 went in to shutdown mode.
This I got past by using the super touch plate widget instead and changing the coordinate system to G54. That way I could use the machine coordinates but still use touchplate leveling for milling.The auto-level widget also seems to use machine coordinates. To get a proper probe, I had to zero the Z coodrdinate a few millimeters over the PCB, and also remember to zero the G54 coordinates accordingly. If these were not done properly, chilipeppr sometimes moved downwards instead of upwards after touching the plate, or just went in to shutdown mode. I am glad I was doing the testing with foam under the copperclad board.
There was also another problem to fix for auto-leveling, sometimes the G2 crashes during process. To fix this, I read on github issues that commenting out colums 120-125 and 135 in gpio.cpp helps. This disables testing the pins with something called “lockout timer”. In the future, I should propbably try to fix the problem instead of disabling it, or maybe disable it only for the probing pin.
niklasMemberTurned out to be a faulty Arduino DUE. I got a new one and its working now. Feel free to remove this post since its not useful for others. And thanks for the help 🙂
niklasMemberRight, and the shield takes uses the IOREF to choose the voltage rating. I am also testing with stepper drivers that work with 3.3V, so that is not the issue. As far as I understand, all the hardware should be ok. I’m a little afraid that I got a faulty DUE, but its hard to know since I don’t have another one to test with.
Does it seem like everything else is ok? Should return it and change it to a new one?
niklasMemberAn external power source for the DUE did not help.
I installed everything to an old Windows 7 computer, flashed the bin file there. I’m getting the same version details in the log and no output to the motors.
Getting kinda puzzled and not sure what more I could try.
niklasMemberThanks for the answer, heres the answers.
You have a ‘known good’ Gshield that works with Uno and perhaps GRBL(?)
I’m using GAUPS 1.1, and what i’ve read, it should work with TinyG2.The pinout seemed to be the same as gShield. Found some people confirming that it works, but they didn’t write about any modifications.
Where did you get $fb=78.02 ?I’ve tried some different precompiled ones and compiled different versions myself. The one on that link actually does give me 78.02 for some reason. Just tried downloading and flashing it again with same result. Doing that on OSX btw.
What pins are you referring to when you write “there are no changes in the digital pins.” ?
Are you measuring at the inputs to the gShield stepper drivers? H
ow are you measuring, Multimeter?Yes, the inputs on the shield and with a multimeter. that might be the problem. But the drivers are not activated so there must be something wrong. I think I have a logic analyser somewhere and could try that out.
Do you have steppers connected to Gshield?Most of the time while testing to see the results directly, but nothing is getting powered.
How are you powering Due and Gshield?
The GAUPS board is powered with 12v and Due with USB power, do I need an external power source for the DUE?
Can you dump your parameter set to a cloud file (dropbox, etc.) and provide a URL?
Heres a paste from a fresh build.
http://pastebin.com/CwEE0LNHniklasMemberwriting {me:10} changes the voltage of the pin 8 from 3.26V to 2.99V for 10 seconds
-
AuthorPosts