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?

Some people are just so hard to please! I'll try to elevate myself to your standards! Thanks for your input though it certainly shortened the tuning process. I've got motors roughly tuned, axis homing, limits working sort of. It's been several decades since I was in school and received my education on numbering systems. As such I'm trying to figure out how to set my I124. My bits, 0-23 are 100000000001100100000001 which should be 108908 or 809801? I also have a problem with my pendant for the advantage 900. The NC program boots up and I'm able to cause motion, homing etc via the terminal screen. However no LED's light on the pendant and the keys don't seem to function.

So both axis working as above plot. However, when I attempt an open loop move on the second axis I get an error message saying FE error. When I check the motor status screen it does not show. Hmmm

Starting to get there. Here's a plot from a parabolic move of X. Still having trouble with the second axis though. I'd noted that I forgot to change my I272 when I corrected the direction for motor and encoder increment. I guess I need to go through that axis completely once again. I was able to change my I213 which is strange? http://i1087.photobucket.com/albums/j464/PEERPSI/Work/th_xplot.jpg' alt='th_xplot.jpg'>

I had looked at those and wasn't sure. Thanks for setting me straight.

I7000?

Counts are quite high and I expect to sort that out with further tuning. Typically on our older lathes we look for 15 counts max at 7MM travel rate. On the newer, less then 5. Of course we struggle to make sure ports are clean, lifts are correct, way covers are not dragging, hoses and cables are in good repair. Then the operator fails to balance the spindle correctly! Argh! The machine uses hydrostatic bearing system. It floats well and the way covers are not yet reinstalled. The lathe was easily able to achieve less then 15 counts FE before tear down. Problem is the ball nut was isolated via the hydrostatic system to prevent vibration transfer. That system was tough to get working right and didn't seem to stay right. This of course means that the stiffness numbers were quite low. Linear motors have been installed which should correct that part of the problem. Today I managed to confirm that the lathe is seeing it's index mark, set up the limit switches and figured out how to get it travelling and incrementing in the correct direction. However, some how I've managed to inadvertentlly cause the second axis to have a positive limit fault. Won't even phase. It's not the hardware limit as I can see the limits toggle in a watch window. When I try and disable the soft limits, I213 it will not accept my input. I try setting it to zero to disable it but something is over riding it. Shouldn't be the PLC as I've not touched that yet. Axis did work yesterday. FE error is hardware or software counts? I'm thinking hardware same as what the position window displays. Hopefully tomorrow I can have homeing and limits working right so I can start getting serious about tuning and get the FE counts down. Again gentlemen thanks for your input. I'm learning lots!

signal period is .00013792999 mm. I calculate as follows: 1/.00013792999*4=29000 hardware counts per mm. 1/.00013792999*128=928007 software counts per mm. 1/.00013792999*128*60.96=1767853 hardware counts per motor cycle With an I122 of 5000 I see about max 4000 cts FE on the position screen. Yet with I111 set to 4000000 I get an FE error when trying to do the maximum step size in the Pro Tune application.

Thanks again Jeff. I went through your steps listed above and I was able to confirm that the counts were close to what I calculated for my scales. In the case of X 1767853 with a comp value of 2999. For this one the procedure above returned values with in 1 or 2 of I171. In the case of Z 1767811 with a comp value of 3331. For this one the procedure above returned values with in +/- 44 of I271. Axis jog and will pass the open loop test and step tests seem okay. However I seem to be having trouble with following error. If it is enabled, even with a very high value I get FE every time. When jogging and watching the FE seems to go no higher then 4000. I'm wondering if I have some feedback address wrong as to where it reads the following error. I've tried homing and then does not work yet either. I need to confirm that the control is seeing the index signal from the scale but I'm not sure where to look for that.

Jogged both axis last night. Next step make them home and then more tuning with the loads on board. Pretty soon we'll have ourselves a lathe! Thanks.

Roger WILCO. I'll try and keep my on going saga to just this thread. Thanks.