Machsupport Forum
Mach Discussion => Mach Screens => Machscreen Screen Designer => Topic started by: Oldraven on March 01, 2015, 07:41:08 AM
-
Hi,
I encountered a strange behavior of Mach3 Tool number DRO 24.
If I execute this; SetDro(24,x) the the Z- and Z- DRO's (on my lathe screen) also changed value at random.
I made a new profile, in fact copying the one in use and this problem was gone. The SetDrO(924,x) functioned fine and both the X- and Z-axis were OK.
But, AFTER using Machscreen the situation was back as before.
Machscreen, on loading the .lset) reported a corrupted file.
Saving the .lset after changing a Button, caused the SerDro(24,x) the malfunction again.
Working on the .lset file, that causes Machscreen to report as Corrupt File, and after saving the .lset again throws the DRO functions into a faulty behavior.
I do not know why the .lset is reported corrupt. Machscreen gives me no clue.
Any insight in this?
Would using Screen4 be a better choice ?
Thanks,
Jos
-
Hi Jos,
When MachScreen is loading a screenset it checks the file structure. If it recognizes a difference between file size specified in screenset and the real file size, it reports a corrupted screenset. Mach3 obviously ignores this. If the screenset is saved, before closing MachScreen, the filesize is truncated to the correct size. Next loading screenset shouldn't report a corrupted file. If you'd send me your screenset, I could have a look at it.
Klaus
-
Hello Klaus,
Thank you for responding.
I am running Mach3 Ver.R3.043.066
Attached is a .rar file with the info.
If you need specific files let me know.
Thanks again,
Jos
Holland
-
Hi Jos,
Your screenset file doesn't report a corrupted state on my machine. Is this the screenset making problems? In your previous posting you are using different code numbers, 24 and 924. I assume 924 was a typo and you meant 824. 824 is an OEM-code, where 24 can be OEM or Standard. I compared your profiles with MachProfile and couldn’t find weighty differences. What button did you change?
Regards
Klaus
-
Hi Jos,
Your screenset file doesn't report a corrupted state on my machine. Is this the screenset making problems?
Yes Klaus , it is.
In your previous posting you are using different code numbers, 24 and 924. I assume 924 was a typo and you meant 824. 824 is an OEM-code, where 24 can be OEM or Standard.
Indeed it should be OEM-Code 824.
I compared your profiles with MachProfile and couldn’t find weighty differences. What button did you change?
The " TURRET 1x " button. I do the testing of the anomaly with this button.
On executing SetDRO(24,x) both X- and Z- DRO's are randomly changed.
This change happens also when the EMCO5 lathe has no power. Noise from the lathe electrics seems no problem.
If I comment the SetDRO(24,x) or SetOEMDRO(824,x) out , the X- and Z_ DRO's are fine.
Today I found that the profile I created yesterday (it worked OK) now is faulty again.
I use Windows XP on a mini HP PC.
Maybe I must delete the entire Mach3 folder and start again.
This has been almost a two month hunt for finding a solution.
thanks,
Jos
-
UPDATE !!
Klaus,
I have erased the Mach3 folder on my PC completely.
After saving relevant files like Screensets, Bitmaps, XML's and others.
Re-installed Mach3 Ver. R3.043.066.
OK, it seems that my special Turn screen is fine now.
After testing the "Turret 1x " button many times, even after re-starting the PC the problem is gone.
Testing the Machscreen worked also fine. I did not get the Corrupt File message.
It seems the a complete new install of Mach3 cured everything.
Thank you for looking into this,
Kind regards,
Jos PA0AMX
Netherlands
-
Hi Jos,
that's good News.
nog een prettige dag
Klaus
-
The problem with the Mach3 VB command " SetDro24 or SetOemDro 824 " turned up again and stayed.
Nothing I have done changed this.
I have worked around this by assigning my own UserDRO(1500, x) Address 1500 is arbitrary chosen by me.
The command in my macro now is; Call SetUserDro(1500, x)
I wanted to set the Tool# in the DRO.
To set a tool# I looked at the ToolAngle DRO; GetDro(3)
A bit of VB commands;
CurrentAngle_A = GetDro(3)
CurrentAngle = CInt(CurrentAngle_a)
If CurrentAngle = 0 or 360 Then Current_Tool_# = 1
If CurrentAngle = 60 Then Current_Tool_# = 2
If CurrentAngle = 120 Then Current_Tool_# = 3
If CurrentAngle = 180 Then Current_Tool_# = 4
If CurrentAngle = 240 Then Current_Tool_# = 5
If CurrentAngle = 300 Then Current_Tool_# = 6
With the Current_Tool_# I can work and set the UserDro(1500 , x)
The only thing is the the TOOLDESC label does not work with my UserDro .
Maybe this is a confusing story, but I do not know what else to do.
Jos
-
I have found what is happening with the command " Call SetOemDro(824, x) "
the jumping of the content of the X- and Z- DRO's is related to the Tool-table.
With a "fresh" tool-table, all zeroes, nothing happens. The DRO's keep their Zero content.
However, a "filled" tool-table with different values for the X- and Z- offsets reflects in the values of the X- and Z- DRO's .
This had me confused for a very long time !!!
No bug in Mach3 , just me not understanding what the relations are between the tool-table and the DRO's .
Jos