Hello Guest it is April 23, 2024, 12:57:04 PM

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 - ftomazz

Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 »
41
General Mach Discussion / Latested 051 version charge pump problem
« on: November 09, 2011, 04:15:33 AM »
I have posted a similar post about this issue with version 50. This is still broken in my system.
The charge pump is not working with the version 50 and 51 (yestarday version). I run a couple more tests and found that it only works at 25KHz kernel.

Latest lockdown version have it working with all kernel speeds.
My set up is a C11 from CNC4PC driven from PCI parallel ports.

Filipe

42
General Mach Discussion / Re: JOG quality better than code movement
« on: November 08, 2011, 05:07:35 AM »
In the lastlock down version this does not happen. In my last post I have informed that it happens, but I probably did not removed the parallel port driver, so I suspect it is related with the parallel port driver that comes together with version 50.

43
General Mach Discussion / Re: Charge pump error in version R3.043.050
« on: November 08, 2011, 05:03:53 AM »
In my set up, reversing to the last lock down version this is solved. So I suspect that is a bug.

44
General Mach Discussion / JOG quality better than code movement
« on: November 07, 2011, 12:53:41 PM »
Both using the latest version as the latest lockdown version I notice a different behaviour from my machine movement at high speeds from jogging to some code. This happens in all axis.
For example, if I jog at top speed from X=0 to X=200 (more or less) and if I command G0 X200 from position X=0, the movement in MDI line (or running any gcode file) is always with a worst quality (seams at bursts). The computer is good hardware and the windows only have Mach3 installed. Kernel speed is 45000Hz, and this only happens at high speeds. If I lower the motors speeds to +- half this does not happen. I cannot test at lower kernel speed, because in that situation the top speed of the motors would be quite lower.

Can it be a BOB issue (should not be as in JOG the movement is smooth), or this is reported anywere - known issue?

Any ideia?

45
General Mach Discussion / Re: History button
« on: November 07, 2011, 12:12:45 PM »
Ups, it seams that the text editor must be on so that this works. I pushed the button and saw nothing ...
Thank you sir.

46
General Mach Discussion / Re: History button
« on: November 07, 2011, 11:46:12 AM »
Thank you,
Then there is no way to get the old status messages (not only error messages) ?

47
General Mach Discussion / History button
« on: November 07, 2011, 03:46:38 AM »
Hi, I would like to be able to read the last messages that went through the "status" line, as sometimes I have messages after messages and the user have no time to read them. Looking in the available resources of Mach, there is a button that is "History", that does not do anything - at least with my setup.

1) There is a way to have those messages available?
2) What does the history button do?

Thank you

48
General Mach Discussion / Re: Mach3 4.0 Rev Update
« on: November 07, 2011, 02:19:32 AM »
Mr Jekran,

About moving the Z while machine is moving, that can be done already. I have a machine like that in a plasma cutter. While the machine is moving the X and Y axis, you can control by hand (I assigned 2 keys, one for up other for down) and I can control the Z during cutting. I do not have to control the Z every piece:
When to start cutting the Z axis moves down until a sensor is reached - then I set Z=0 in that position - then you have control using the up and down assigned keys, and you have a DRO with the Z position, where you can control your Z position and as Z was set to zero, you know your relative position.
If I remember correctly I used brains and the torch height control.

Filipe

49
This is then a auto reply, as I tested with others versions and the result was the same.

It seams that Txxyy Mach3 only reads the X and Z offsets of of the tooltable in position yy, and not the tip and radius offsets (that uses from xx). This is not correct and does not follow "standard machine" rules, if this exist (Fanuc Siemens and so on)

When calling Txxyy, the yy should contain date entry for, at least, the following information: tool tip direction, radius, X and Z offset.

Filipe

50
Hello.
Using the latest version R3.043.050, and using the standard toolchange format Tyyxx, where yy is the toolpost number and the xx is the offset number, for example:

T0303 calls tool in post nº3 with offset number 3 (in my case 03 offset is direction 7 and radius 0.8mm)

but calling

T0903 calls tool in post nº9 (as expected) but it also calls the offset nº9 instead of offset number nº3 as it was suppose to, this is the offset that is being used by the DRO's and that appear on the toolpath display is always in relation, not with the offset asked, but it is in reference to the toolpost asked.

Can anyone inform me of a version that have this running ok? My machine only can work if this is corrected.

Thank you

Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 »