Hello Guest it is April 19, 2024, 04:24:25 AM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - CDyckes

Pages: 1 2 3 »
1
Competitions / Re: ******Guess and win a G100 Grex******
« on: May 22, 2007, 10:59:41 AM »
My 'count' is 2467846   :)

Colin

2
General Mach Discussion / Re: Feed rate override
« on: May 14, 2007, 11:15:27 AM »
It was the "No FRO onQ" override that I remember possibly being the default in days of old as it did take until the next g-code item or so for the FRO to take effect.

I assume the new 250% will still apply if I set "No FRO onQ" :(   Hope I don't need to resort to binary patching :(

Colin

3
General Mach Discussion / Re: Feed rate override
« on: May 14, 2007, 10:20:14 AM »
Are we talking at cross purposes, or am I missing something?

Doesn't the FRO just adjust the feed rates as set in the g-code file? I didn't think it had any affect on the defined acceleration or maximum motor speed so can't see why it would cause an axis fault.

All I'm looking for is the ability to compensate for the fact that say I've made a stupid error in the g-code file from Lazycam which was maybe last used to cut a piece of carbon steel at maybe 5mm/min and am actually cutting MDF (or doing an 'aircut') on this job so just want it to cut 10 times faster.

Art did make this manual adjustment of percentage override available before. I was hoping it could be done again on a 'manual XML edit' basis as I can't see any downside.

Colin

4
General Mach Discussion / Re: Feed rate override
« on: May 13, 2007, 06:43:01 AM »
Consensus from the 'big boys' was just that, but Art implemented an override in the config file for those of us with small hobby machines who wanted it to have our own specified max override.

250% is even worse :(

PLEASE can we have an XML entry to override it by editing the XML manally as before?

Colin

5
General Mach Discussion / Re: Config Fonts Doesn't Appear to Work
« on: May 12, 2007, 03:57:39 PM »
I don't want to re-raise what is obviously a touchy subject, but is there a solution to the 'large fonts' problem?  I know it can be done from the 'appearance' tab rather than 'advanced/large fonts' but this is horribly clunky and really not the way to do it for best overall results in Windows.

Most modern screens are both big and  have a lot of pixels (my Dell 2407's are 1920 x 1200) and REALLY need large fonts set to be readable. Windows provides a mechanism to handle this if all screens are coded using "dialog units" whereby it calculates the display font and display element size based on dialog units and a multiplier/divider calculated from the dpi setting (I've written several screen designers that do it this way and it works well (though not quite perfectly in all cases)).

Just wondering if there was a solution to this other than using 'appearances' which isn't acceptable. Has anyone designed a screenset using 'large fonts'?

Thx

Colin

6
General Mach Discussion / Feed rate override
« on: May 12, 2007, 03:41:21 PM »
There used to be a way of overiding the 300% max limit on feedrate override for those who wanted to take the risk (as a config file setting) .  I can't find this anywhere. Does it still exist as I often do want to bump the speeds way up if I've poorly coded a job with say Lazycam?

Thx

Colin


7
Mach3 under Vista / Re: Getting up and running in Vista
« on: May 08, 2007, 10:46:15 AM »
You may well have a point about the 3.3v issue, especially as I ordered an PCMCIA parallel port card and it was only on the despatch email that the the vendor said it may not be suitable for Dell Inspiron notebooks as they 'didn't supply 5v to the PCMCIA card slot'. However, the card runs a Laserjet 5000 perfectly, and appears to run the Bob Campbell interface board OK, though I can easily solve the 3.3v to 5v level shift if that proves to be an issue.

I suspect though that it's a Mach3 pulse driver/Vista interaction because I'm getting VERY variable rates in the diagnostic test program and in the diagnostics screen of Mach3. The motor movement suggests that the pulse driver is getting its timeslice interrupted as I get short bursts of smooth and then jumpy movement.

I've only got the Dell 9300 on Vista so far (Only willing to go so far along the 'bleeding edge' as all other machines are work critical). The old AJP 300MHz PIII notebook that used to drive Mach2 perfectly seems no longer adequate for Mach3 (and that did drive its built-in parallel port perfectly), so I wanted to try the Dell as I don't use the CNC often (1st time in three years after a house move and renovation), though want to get back to using it more.

Would like to help get Vista running (and have full DevStudio installed and can do any level of debugging if Art will trust me with driver code and test program). In the meantime, I've got nearly all the bits for another PC, so am putting together a 3GHz P4 to run XP.

Colin


8
Mach3 under Vista / Re: Getting up and running in Vista
« on: May 03, 2007, 10:28:07 AM »
Anyone else managed to get Mach3 (latest build) running on Vista?

I can get drivertest and Mach3 to run, but the pulse timing is VERY erratic and makes it unusable.

I'm running on a 2.13GHz Dell Inspiron 9300 Notebook with 6800Go graphics.

(I've just ordered an ncPod - is this the way forward for Vista usage?)


9
LazyCam (Beta) / Re: Possible bug in Lazycam?
« on: April 30, 2007, 03:56:09 PM »
Ran the test loop some 50 times in total, manually cranking the z-axis down every 10th pass to allow for pencil wear. Got this:-



Picture was slightly out of square and I haven't photo adjusted, but actual result looks a good rectangle to me.


10
LazyCam (Beta) / Re: Possible bug in Lazycam?
« on: April 30, 2007, 09:11:45 AM »
Brian,

I'll try and rig up a pen and try that after work.

For what it's worth, all the holes measure correctly from the lower edge to within .02mm (which is amazingly accurate). RH portion of the top cut is now straight.

Wouldn't the top righthand cut slope upwards if backlash was the problem (it did slope down before the Mach3 fix whilst the left portion of the top cut was straight and parallel to the bottom cut).

Pages: 1 2 3 »