Forum Replies Created
-
AuthorPosts
-
fixxxer
MemberHey guys thanks for the quick replies as always! I’ve solved this halfway, at least I know the cause. It’s a finishing pass setting within F360. I turned off multiple finishing passes and it cuts the way you’d expect. I’d love to hear some insight on the matter if you have any but I understand it’s not really a synthetos problem.
Cheers.Memberg0 y100 moves about 60mm (reading with tape measure so it’s not bomber). However I changed $2pm and now =1. The motor responds immediately and moves the correct distance. My concern is, doesn’t $2pm= 1 essentially keep motors at freehold? I don’t know but I’ve heard that motors can over heat that way. Is there any truth to that?
I’m glad you mentioned the $2tr because I forgot to correct it to 24.9351. It’s a 3.2 reduction on a 1″ drive pulley via belt. http://www.cncrouterparts.com/pro-rack-and-pinion-drive-nema-34-p-226.html, down about half way.
Anyway the thing works now thanks to you. Will try running it through it’s paces after I get my limit switches configured.
Earlier you’d said “…but your CAM software(e.g. Chilipeppr) may barf on that value as the native (on-board) tinyGdrivers don’t accept $_mi=10.” Are you saying that the tinyG might send bad values to chilipeppr (that is what I use) even though it can send the drivers the right info?
For future reference, I talked with gecko tech support and they have a “daughter” board for the g203 v with a jumper selectable step configuration that modifies the step driver and turns it into the g213v that I should have probably purchased in the first place.
Here’s a link: https://www.geckodrive.com/g901x-stepper-multiplier.html
One would have to remove the cover and unplug something and then put this modifier board in essentially. But then I think you can select 1,2,5 or 10 micro.That’s the route I’ll go if chilipeppr gives me trouble.
MemberOne note regarding the specific performance issues. Besides the fact that motor doesn’t move the gantry the specified distance, the thing that really gets me is the pause. On the old machine, with no external drivers the machine would respond as soon as I hit enter on a G move. Now there are 1-3 second before I can detect any movement. I’m sure it’s just the incompatibility of the drivers with the tiny G but I wanted to be thorough. I’ll make another post asking about gecko drivers in general.
MemberOkay so right now I’m only communicating with motor group 2, mapped to y axis. The other motors are disengaged and the other motor drivers are not powered. I set the tr values to the machine as described by cncrouterparts.com. I’ve changed the $2mi from 1 to 10 and I don’t see any difference in performance. I didn’t read the documentation clearly enough on the gecko website. I assumed incorrectly that the 10 meant max, not default native hardcoded. I’m assuming I’ll have to exchange them but here’s a link to my $$ dump just in case you guys have a brilliant alternative:
https://gist.github.com/GregRobinson85/7a44f173506ed13655c4bec4c3c7b1a4#file-gistfile1-txtAs an aside, a new development when I power on my tiny g. There used to be just a red light that would flash on reset but now all four green motor lights flash along with the red one. Once it’s all reset and happy, it’s just the blue on LED. Are there more settings somewhere other than the $$?
MemberI’ll spare you the details but I’ve been running tests since your last post. Yes, I’m using the gantry as the ground lead for the circuit. why it works on the other switches I don’t know. I insulated a new ground from the gantry and aligned it in the same place to strike the pogo pin and it worked! Thanks, I feel like a dummy. noise accumulation?! =( I have a repeatable zero again! Thank you so much, you are a god send. I need to buy you a beer. This has been a thorn in my side for months.
MemberNo, 28.2 y and z are great. Not only that, if I change the max and mins around for x (so that it homes in the positive direction) the max switch works fine(this is with max as homing and limit and min as limit only). That is, it performs the backoff but at the other end of the machine.
Regarding LED, after the switch is hit, the PWM stays solid but other than the power light, there’s nothing flashing. Now the machine at this point says $posx= negative 5xx. When I enter g0 x10, as soon as it moves off the switch I get the “limit switch hit” error and the lights go on and all. I’ve been using the heck out of this remote reset switch.
I am running coolterm and chilipeppr, with the same results for each. I noticed the problem sometime after I started using chilipeppr, but I can’t point to it as the culprit.
Now in diagnostic land, this all points to the switch at the xmin. It’s obvious. Which is why I replaced it last week. Boy was I surprised to see that it wasn’t the problem.
The switches are spring loaded pogo pins soldered to wires.
Is there somehow an option to configure different switch types for different axes? It’s almost as if the xsn is configured differently. I’m baffled, this is a relatively new problem with zero hardware changes (until last week). I’ve been running the machine for at least 6 months.
MemberGood catch. I changed $st to NO, reset everything except for travel maxes, reset the TinyG, did an $$ and then tried to zero with the 28.2 x0. You can see what happens (after config).
{“r”:{“fv”:0.970,”fb”:440.20,”hp”:1,”hv”:8,”id”:”3Y2462-PPV”,”msg”:”SYSTEM READY”},”f”:[1,0,0,5179]}
$$
[fb] firmware build 440.20
[fv] firmware version 0.97
[hp] hardware platform 1.00
[hv] hardware version 8.00
[id] TinyG ID 3Y2462-PPV
[ja] junction acceleration 2000000 mm
[ct] chordal tolerance 0.0100 mm
[sl] soft limit enable 0
[st] switch type 0 [0=NO,1=NC]
[mt] motor idle timeout 2.00 Sec
[ej] enable json mode 0 [0=text,1=JSON]
[jv] json verbosity 5 [0=silent,1=footer,2=messages,3=configs,4=linenum,5=verbose]
[js] json serialize style 1 [0=relaxed,1=strict]
[tv] text verbosity 1 [0=silent,1=verbose]
[qv] queue report verbosity 0 [0=off,1=single,2=triple]
[sv] status report verbosity 1 [0=off,1=filtered,2=verbose]
[si] status interval 500 ms
[ec] expand LF to CRLF on TX 0 [0=off,1=on]
[ee] enable echo 0 [0=off,1=on]
[ex] enable flow control 1 [0=off,1=XON/XOFF, 2=RTS/CTS]
[baud] USB baud rate 5 [1=9600,2=19200,3=38400,4=57600,5=115200,6=230400]
[net] network mode 0 [0=master]
[gpl] default gcode plane 0 [0=G17,1=G18,2=G19]
[gun] default gcode units mode 1 [0=G20,1=G21]
[gco] default gcode coord system 1 [1-6 (G54-G59)]
[gpa] default gcode path control 2 [0=G61,1=G61.1,2=G64]
[gdi] default gcode distance mode 0 [0=G90,1=G91]
[1ma] m1 map to axis 0 [0=X,1=Y,2=Z…]
[1sa] m1 step angle 1.800 deg
[1tr] m1 travel per revolution 5.0000 mm
[1mi] m1 microsteps 1 [1,2,4,8]
[1po] m1 polarity 0 [0=normal,1=reverse]
[1pm] m1 power management 2 [0=disabled,1=always on,2=in cycle,3=when moving]
[2ma] m2 map to axis 1 [0=X,1=Y,2=Z…]
[2sa] m2 step angle 1.800 deg
[2tr] m2 travel per revolution 5.0000 mm
[2mi] m2 microsteps 1 [1,2,4,8]
[2po] m2 polarity 0 [0=normal,1=reverse]
[2pm] m2 power management 2 [0=disabled,1=always on,2=in cycle,3=when moving]
[3ma] m3 map to axis 2 [0=X,1=Y,2=Z…]
[3sa] m3 step angle 1.800 deg
[3tr] m3 travel per revolution 5.0000 mm
[3mi] m3 microsteps 1 [1,2,4,8]
[3po] m3 polarity 1 [0=normal,1=reverse]
[3pm] m3 power management 2 [0=disabled,1=always on,2=in cycle,3=when moving]
[4ma] m4 map to axis 2 [0=X,1=Y,2=Z…]
[4sa] m4 step angle 1.800 deg
[4tr] m4 travel per revolution 2.1166 mm
[4mi] m4 microsteps 8 [1,2,4,8]
[4po] m4 polarity 1 [0=normal,1=reverse]
[4pm] m4 power management 2 [0=disabled,1=always on,2=in cycle,3=when moving]
[xam] x axis mode 1 [standard]
[xvm] x velocity maximum 2000 mm/min
[xfr] x feedrate maximum 2000 mm/min
[xtn] x travel minimum 0.000 mm
[xtm] x travel maximum 290.000 mm
[xjm] x jerk maximum 5000 mm/min^3 * 1 million
[xjh] x jerk homing 10000 mm/min^3 * 1 million
[xjd] x junction deviation 0.0100 mm (larger is faster)
[xsn] x switch min 1 [0=off,1=homing,2=limit,3=limit+homing]
[xsx] x switch max 0 [0=off,1=homing,2=limit,3=limit+homing]
[xsv] x search velocity 2000 mm/min
[xlv] x latch velocity 100 mm/min
[xlb] x latch backoff 20.000 mm
[xzb] x zero backoff 10.000 mm
[yam] y axis mode 1 [standard]
[yvm] y velocity maximum 2000 mm/min
[yfr] y feedrate maximum 2000 mm/min
[ytn] y travel minimum 0.000 mm
[ytm] y travel maximum 320.000 mm
[yjm] y jerk maximum 5000 mm/min^3 * 1 million
[yjh] y jerk homing 10000 mm/min^3 * 1 million
[yjd] y junction deviation 0.0100 mm (larger is faster)
[ysn] y switch min 1 [0=off,1=homing,2=limit,3=limit+homing]
[ysx] y switch max 0 [0=off,1=homing,2=limit,3=limit+homing]
[ysv] y search velocity 2000 mm/min
[ylv] y latch velocity 100 mm/min
[ylb] y latch backoff 10.000 mm
[yzb] y zero backoff 2.000 mm
[zam] z axis mode 1 [standard]
[zvm] z velocity maximum 2000 mm/min
[zfr] z feedrate maximum 2000 mm/min
[ztn] z travel minimum -120.000 mm
[ztm] z travel maximum 0.000 mm
[zjm] z jerk maximum 50 mm/min^3 * 1 million
[zjh] z jerk homing 1000 mm/min^3 * 1 million
[zjd] z junction deviation 0.0100 mm (larger is faster)
[zsn] z switch min 0 [0=off,1=homing,2=limit,3=limit+homing]
[zsx] z switch max 0 [0=off,1=homing,2=limit,3=limit+homing]
[zsv] z search velocity 2000 mm/min
[zlv] z latch velocity 100 mm/min
[zlb] z latch backoff 10.000 mm
[zzb] z zero backoff 3.000 mm
[aam] a axis mode 3 [radius]
[avm] a velocity maximum 25920 deg/min
[afr] a feedrate maximum 12960 deg/min
[atn] a travel minimum -1.000 deg
[atm] a travel maximum -1.000 deg
[ajm] a jerk maximum 324000 deg/min^3 * 1 million
[ajh] a jerk homing 324000 deg/min^3 * 1 million
[ajd] a junction deviation 0.1000 deg (larger is faster)
[ara] a radius value 5.3052 deg
[asn] a switch min 1 [0=off,1=homing,2=limit,3=limit+homing]
[asx] a switch max 0 [0=off,1=homing,2=limit,3=limit+homing]
[asv] a search velocity 2000 deg/min
[alv] a latch velocity 2000 deg/min
[alb] a latch backoff 5.000 deg
[azb] a zero backoff 2.000 deg
[bam] b axis mode 0 [disabled]
[bvm] b velocity maximum 3600 deg/min
[bfr] b feedrate maximum 3600 deg/min
[btn] b travel minimum -1.000 deg
[btm] b travel maximum -1.000 deg
[bjm] b jerk maximum 20 deg/min^3 * 1 million
[bjd] b junction deviation 0.0100 deg (larger is faster)
[bra] b radius value 1.0000 deg
[cam] c axis mode 0 [disabled]
[cvm] c velocity maximum 3600 deg/min
[cfr] c feedrate maximum 3600 deg/min
[ctn] c travel minimum -1.000 deg
[ctm] c travel maximum -1.000 deg
[cjm] c jerk maximum 20 deg/min^3 * 1 million
[cjd] c junction deviation 0.0100 deg (larger is faster)
[cra] c radius value 1.0000 deg
[p1frq] pwm frequency 100 Hz
[p1csl] pwm cw speed lo 1000 RPM
[p1csh] pwm cw speed hi 2000 RPM
[p1cpl] pwm cw phase lo 0.125 [0..1]
[p1cph] pwm cw phase hi 0.200 [0..1]
[p1wsl] pwm ccw speed lo 1000 RPM
[p1wsh] pwm ccw speed hi 2000 RPM
[p1wpl] pwm ccw phase lo 0.125 [0..1]
[p1wph] pwm ccw phase hi 0.200 [0..1]
[p1pof] pwm phase off 0.100 [0..1]
tinyg [mm] ok>________________________________
g28.2 x0
tinyg [mm] ok>
posx:0.000,posy:0.000,posz:0.000,posa:0.000,feed:0.00,vel:0.00,unit:1,coor:0,dist:1,frmo:1,stat:9
posx:-15.389,feed:2000.00,vel:2000.00
posx:-31.716
posx:-48.042
posx:-64.202
posx:-80.530
posx:-96.857
posx:-113.017
posx:-129.344
posx:-145.671
posx:-161.997
posx:-178.153,vel:1998.25
posx:-178.884,vel:1.75
posx:-310.000,feed:0.00,vel:0.00,coor:1,dist:0,stat:3It’s gradually moving in the -x direction until it hits the switch, where it jumps up to -310. It isn’t doing any of the homing sequence. It doesn’t do latch or backoff OR try to zero the machine. $posx still says -310. Any ideas?
MemberThanks for the reply, I have read that page several times but I’ve missed the $xJH command. I haven’t adjusted those values and they’re set “[xjh] x jerk homing 40 mm/min^3 * 1 million.” I can play around with the parameters but out of curiosity what do you guys use? I’m assuming that the higher the number, the quicker the machine will stop.
MemberI figured it out…and yes I can interact with the tinyg from coolterm in line mode. Problem was file extension type. I resaved using a text editor as a .txt instead of .gcode and it worked fine. I’ve looked into Chilipeppr but haven’t had a chance to use it yet. Maybe now’s a good time to learn it. I have another question but I’ll create a new topic. Thanks for the responses.
-
AuthorPosts
