PEERPSI

Solved this tonight. My var.dat file had a number of undefined entries represented by #0. I went through the list of vars, 500-599, that we use in the program and set those without values or those that represent a logical 1 versus 0 to defined 0 values. This means that their entries in the var.dat file are now represented by a 0 instead of a #0.

@SET_ON(CS_STATUS3_M, CS_CLNT_FLOOD) ;<<<<<<<<<<<<<<<<<<<<< these are not used @SET_ON(CS_STATUS3_M, CS_CLNT_MIST) ;<<<<<<<<<<<<<<<<<<<<< for M07 substitute S_CLNT_M = SEL_CLNT_FLOOD for M08 substiture S_CLNT_M = SEL_CLNT_MIST for M09 substiture S_CLNT_M = SEL_CLNT_OFF This solved my active M-Code issues.

Deltau Tau tells me there is a Pcomm server update that is going to resolve this issure. Thanks Steve M.

Sorted this out. In the registry there are settings for inch and mm. There are also axis specific settings under NC0. If you change the axis specific settings it messes up the display.

Found the settings in the registry for correcting this. Under the section Code I needed to change the Default and SetOnReset values to the code I wanted to be set on startup.

I found this in the NC functions manual: GetCoolantSelect GetCoolantSelect() Returns Collant select as a string. The return value can vary depending on the following: If Collant Select = NC_COOLANT_MIST: Return Val = 7; If Collant Select = NC_COOLANT_FLOOD: If Collant Select = NC_COOLANT_BOTH: Return Val = 8; default: Return Val = 9; Should the NC_COOLANT_* variables be in one of my *.h files? Should their status be set in the *.M file?

According to the manual certain G-codes are supposed to be default startup. I'm finding that is not the case for instance I need to command G63 Radius mode as it defaults to diameter. I'd also like to set G01 as the default rather then G00. What is the recommended method of setting default G-codes and what could be the reason mine is not going to what the manual states. Any ideas?

My active M-code window does not update when an M7 or M8 is issued. M09 stays in place despite M7-8 being commanded. I did not change the lathe.m file to operate my outputs I made an accessory PLC instead. Any ideas?

I'm having troulbe sorting out why my program position and DTG windows are not showing the right number of decimal places. I've set them for 3.6 in inch, 3.5 in mm. They only show 4 decimal places. When I call up the "all" position window they show 6 in inch, sometimes. It seems to change if you try a reboot. Also my Program position window is not titled Program position buy absolute? Stranger yet is the fact that it was all working right. I had an incorrect value for maximum feedrate so I reran auto pilot making the change I needed. Since doing that it has not worked right. Any ideas?

I'm attempting to run a parametric program used on an older A600 system. The program executes to a certain block and then just stops. The number of lines versus lines in the program starts to increase rapidly and the program window shows no text with just a yellow bar. I've stripped out the parts that the program should run based on what the parameters are and when I just run that part in a seperate program it runs fine. Any ideas?

So almost there, feedback configured, axis movement, limits working, home routine working, I/O working and custom M-codes functioning. What I'm having trouble with now is having the active M-code window show what is actually active. For instance I've edited my Lathe.M file so that my M7 and M8 turn mist and flood coolant on. However M9 remains in the active M-code window and M7-M8 do not appear. There is a section in the NC-Pro2 manual for working with the M-codes but it does not cover this. Any ideas?

I'll look closer at my variable. I believe I have the cause of the drift resolved. The #xo0 was required in the manual phasing routine example in the brick manual. I'm going through the fine phasing setup that is listed in that manual which calls for manual phasing first.

I've been trying to follow the manual phasing routine in the Brick manual preceding the fine phasing example. I have set a variable to display the phasing register but when I attempt to zero it it does not respond. M1000->=X:$078001,1,24,S is what I have set. Any ideas? Also I've noted that with a #xO0 command on my first axis it drifts for a fail bit before it stops. My drive has no balance setting when using dual differential analog input and I've used a DVM to set I129 and I179 so that my DACS are as close to zero as possible. Any ideas?

Thanks the Geo manual does give some better notes.

Okay pendant working, MDI mode in NC Pro working, responds to G codes as expected and homes from the pendant. I need to figure out fine phasing next as I've noted the base FE seems to change dependant on phasing which must mean I'm not accurate enough on that yet. Any advice?