System hotkeys

[corydoras]

I know there is now support on Q yet, but has anyone tride to change the system hotkeys on up and down arrow?

Just wanted to change direction because of computer placement, but when I change y+ from  oem code 38 to 40 and  y- from 40 to 38, I get a problem, and that is when i press the up arrow the g-code window inprogram run screen becomes active instead of jogging y axis.

When I try to change them back the same thing happens.

This doesnt happen with mach3

I have restarted Q and tried again and AGIN.

Best reg
Cory

[Chaoticone]

Hey Corey, sounds like you have assigned a hot key to the G-code list too. See pic.

Brett

[corydoras]

Hi Brett, how are you doing?

You got it dude, absolutely correct....I did something stupid, not even sure I wanna put it in writing here.

I thought that Code list was a field for trying out what oem code each hotkey had....well you learn as you live.

On the other hand I am really starting to loose faith in my newest machine.....not sure it will ever run smooth......

I´ve spent well over 300 hrs on it now and just assembled it today with new linear bearings and blocks, but still there is not a perfect cut

I´m starting to think that mabye my servo amp just cant handle the motions I want, but the Y axis is running on the same motor and gearing, also belt driven, and runs smooth.

Iv tried all possible combination of  speed loop gain, Integration time constant of the speed loop, and position loop gain, but still get circles as the one in the attached photo.

Any ideas would be greately appriciated.

Best reg
cory

[corydoras]

Brett

Mabye this is not the correct thred for this problem, but my problem is similar to this dudes problem

If you can and will, plz move this to a better suited place on the forum:)

http://www.artsoftcontrols.com/forum/index.php?topic=2969.10

always in the same spot, when the X axis turn "over the hill",

It gets better if i reduce the speed from 5000 mm/m to 1000mm/m

Best reg
Cory

[Chaoticone]

Hey Corey, I think you suffer the same problem he had too. It looks like backlash to me. possibly machine twist too.   Have you checked your backlash with a dial indicator? Also, you can try backlash comp., in the config tab. If you try it, you will want to set youe shuttle accel. to .1 or lower I think. it is the the top middle of general config. You have to exit and reenter mach for those to take.

Hey,
    Checking your backlash should be no problem if you have an indicator. Put the indicator on something solid. Jog your axis until you move the indicator to a reading of about half of its travel. Write down the reading on the indicator. Jog the axis in the other direction by a set amount, say .010" and see how much difference the indicator shows. If the indicator says you moved .005 and Mach says it has moved .010 then you have .005" backlash.  You can check check your steps per. with your indicator also. Set up as before., only this time run the axis in until it just starts to move the needle on the indicator. Write down your reading. Going in the same direction give the axis a move with Mach. If Mach thinks it moved it .010" and your indicator says it moved .010", your steps per are right.
 
Brett

[corydoras]

Hi Brett and thanx for the tips, I found that the motor mount twist a little under rapis movements, I´ll secure that permanently on monday
For now I just fixed it with a vice clamp.

I have a dial inicator at work that I will bring home after work on monday.

I made an interesting discovery right now,playing with the kernel speed, and that it when I override the system FRO cutting a circle in air, the Y axis maxes a stop in the same position that I have the mark, especially at 6 oclock.


When i turn down the speed it gets better at least what I can see with the naked eye.


I also look at the kernel speed in the diag page and it is stable without running any g-codes, but falls about 10 when starting to cut the circle, but if I increase the speed, it starts dropping more at a good override it drops 20-25, is this to much.

Could this be the case of the stop in the Y axis?, mabye not getting  enough pulses?

Best reg
Cory

[corydoras]

Did another test at 25K, it doesnt drop more than 5 now, but it still makes a stop at 3/4 of the circle.

I have drawn several circle, and they all act the same.

I have attached the g-code if somone would like to try it

Best reg
Cory

[corydoras]

Here is a list of last errors, dint know if it means anything, but the watchdog kicked in, and a couple of buffer errors

Sun - 00:27:45 ---Program Startup
Sun - 00:27:56 ---
Sun - 00:28:01 ---Sunday. July 08. 2007
Sun - 00:28:02 ---Sunday. July 08. 2007
Sun - 00:28:09 ---Sunday. July 08. 2007
Sun - 00:28:14 ---Sunday. July 08. 2007
Sun - 00:28:18 ---Sunday. July 08. 2007
Sun - 00:28:38 ---Sunday. July 08. 2007
Sun - 00:28:42 ---Sunday. July 08. 2007
Sun - 00:28:46 ---Sunday. July 08. 2007
Sun - 00:28:50 ---Sunday. July 08. 2007
Sun - 00:29:41 ---Sunday. July 08. 2007
Sun - 00:29:45 ---Sunday. July 08. 2007
Sun - 00:29:49 ---Sunday. July 08. 2007
Sun - 00:30:02 ---Press Cycle Again to start program..
Sun - 00:30:13 ---Sunday. July 08. 2007
Sun - 00:30:17 ---Sunday. July 08. 2007
Sun - 00:30:21 ---Sunday. July 08. 2007
Sun - 00:30:25 ---Sunday. July 08. 2007
Sun - 00:30:29 ---Sunday. July 08. 2007
Sun - 00:30:33 ---Sunday. July 08. 2007
Sun - 00:30:37 ---Sunday. July 08. 2007
Sun - 00:30:41 ---Sunday. July 08. 2007
Sun - 00:30:45 ---Sunday. July 08. 2007
Sun - 00:30:49 ---Sunday. July 08. 2007
Sun - 00:31:48 ---Sunday. July 08. 2007
Sun - 00:31:50 ---Sunday. July 08. 2007
Sun - 00:32:01 ---Sunday. July 08. 2007
Sun - 00:32:28 ---Sunday. July 08. 2007
Sun - 00:32:29 ---Sunday. July 08. 2007
Sun - 00:32:36 ---Sunday. July 08. 2007
Sun - 00:32:41 ---Sunday. July 08. 2007
Sun - 00:32:45 ---Sunday. July 08. 2007
Sun - 00:32:50 ---Sunday. July 08. 2007
Sun - 00:32:55 ---Sunday. July 08. 2007
Sun - 00:33:06 ---Sunday. July 08. 2007
Sun - 00:33:11 ---Sunday. July 08. 2007
Sun - 00:33:16 ---Sunday. July 08. 2007
Sun - 00:33:21 ---Sunday. July 08. 2007
Sun - 00:33:26 ---Sunday. July 08. 2007
Sun - 00:33:31 ---Sunday. July 08. 2007
Sun - 00:34:32 ---Sunday. July 08. 2007
Sun - 00:34:46 ---Sunday. July 08. 2007
Sun - 00:35:04 ---Sunday. July 08. 2007
Sun - 00:35:09 ---Sunday. July 08. 2007
Sun - 00:35:13 ---Sunday. July 08. 2007
Sun - 00:35:18 ---Sunday. July 08. 2007
Sun - 00:35:49 ---Sunday. July 08. 2007
Sun - 00:35:54 ---Sunday. July 08. 2007
Sun - 00:35:58 ---Sunday. July 08. 2007
Sun - 00:36:03 ---Sunday. July 08. 2007
Sun - 00:36:08 ---Sunday. July 08. 2007
Sun - 00:36:12 ---Sunday. July 08. 2007
Sun - 00:36:17 ---Sunday. July 08. 2007
Sun - 00:36:21 ---Sunday. July 08. 2007
Sun - 00:36:25 ---Sunday. July 08. 2007
Sun - 00:36:29 ---Sunday. July 08. 2007
Sun - 00:36:34 ---Sunday. July 08. 2007
Sun - 00:36:39 ---Sunday. July 08. 2007
Sun - 00:36:43 ---Sunday. July 08. 2007
Sun - 00:36:48 ---Sunday. July 08. 2007
Sun - 00:36:48 ---command killed due to buffer error.
Sun - 00:37:00 ---Sunday. July 08. 2007
Sun - 00:37:02 ---Sunday. July 08. 2007
Sun - 00:37:29 ---Sunday. July 08. 2007
Sun - 00:37:45 ---Sunday. July 08. 2007
Sun - 00:37:56 ---Sunday. July 08. 2007
Sun - 00:38:11 ---Sunday. July 08. 2007
Sun - 00:38:11 ---Sunday. July 08. 2007
Sun - 00:38:24 ---Sunday. July 08. 2007
Sun - 00:38:35 ---Sunday. July 08. 2007
Sun - 00:38:46 ---Sunday. July 08. 2007
Sun - 00:38:57 ---Sunday. July 08. 2007
Sun - 00:39:08 ---Sunday. July 08. 2007
Sun - 00:39:16 ---Sunday. July 08. 2007
Sun - 00:39:22 ---Sunday. July 08. 2007
Sun - 00:39:27 ---Sunday. July 08. 2007
Sun - 00:39:33 ---Sunday. July 08. 2007
Sun - 00:39:38 ---Sunday. July 08. 2007
Sun - 00:39:38 ---command killed due to buffer error.
Sun - 00:39:46 ---Driver Watchdog Triggered
Sun - 00:40:54 ---Sunday. July 08. 2007
Sun - 00:41:05 ---Sunday. July 08. 2007

[Chaoticone]

Hey Corey, you don't need to set the Khz mode any higher than it needs to be to run your machine. Any more than that will only hurt you. I think you have back lash and maybe trying to push your motors too fast, as well as your PC faster than they can do reliably. Are you runnnig in CV mode or exact stop? Try CV mode if you haven't allready. Also, try turning down your motor tuning and in general config, Check to make sure the no FRO on Que is checked.

Brett

[corydoras]

Hi

Did some more testing today, and the result gets better with slower speeds.
first photo is made routing with a feed of 5000mm/m and acc set to 500
second photo is made routing with a feed of 1000mm/m and acc set to 500

This should mean that there are some movement in the gantry while doing rapid change of direction or something like that, although is is poorest on curves and angeled cuts.

The no FRO on Que was not checked, i tried it, but no significant change of result, btw, what is this function?

I have another question, are there any q version out yet that has the wizzard functioning?

I have Version R2.0.024, and nothing happen when i press the wizzard button, so i cannot try the same writing with the path smoothing function

Best reg
Cory