Dynomotion

Group: DynoMotion Message: 13039 From: Moray Cuthill Date: 3/31/2016
Subject: UserData allocations
Hi,

is there a list anywhere showing what UserData addresses are used by KMotion/KMotionCNC?

I'm finally getting around to installing the new computer on my lathe, and spent a while trying to work out why I couldn't get a valid value to transfer via Modbus to my toolchanger PLC, and after much head scratching, I finally realised that UserData[6] was being updated by something else. Meaning as soon as my C program updated it, it got changed to another value (something starting with 2 with about 7 or 8 digits).
Now the same UserData was used with Mach, so I'm guessing something related to KMotionCNC that is causing the problem?

I went through all the programs I use, and couldn't see anything else using UserData[6], and I have my own header file where I declare all the constants I use to ensure I don't use any duplicate UserData or Bits.

Thanks,
Moray
Group: DynoMotion Message: 13041 From: Tom Kerekes Date: 3/31/2016
Subject: Re: UserData allocations
Hi Moray,

No sorry there isn't.  There shouldn't be any mysteriously used variables by KMotion or KMotionCNC.  Only ones that you have configured to be used one way or another.

Regards
TK

On 3/31/2016 2:46 PM, Moray Cuthill moray.cuthill@... [DynoMotion] wrote:
 
Hi,

is there a list anywhere showing what UserData addresses are used by KMotion/KMotionCNC?

I'm finally getting around to installing the new computer on my lathe, and spent a while trying to work out why I couldn't get a valid value to transfer via Modbus to my toolchanger PLC, and after much head scratching, I finally realised that UserData[6] was being updated by something else. Meaning as soon as my C program updated it, it got changed to another value (something starting with 2 with about 7 or 8 digits).
Now the same UserData was used with Mach, so I'm guessing something related to KMotionCNC that is causing the problem?

I went through all the programs I use, and couldn't see anything else using UserData[6], and I have my own header file where I declare all the constants I use to ensure I don't use any duplicate UserData or Bits.

Thanks,
Moray
Group: DynoMotion Message: 13042 From: Moray Cuthill Date: 4/1/2016
Subject: Re: UserData allocations
Thanks for the reply Tom.
Turns out I'd put a couple errant ampersands in my diagnostic/status printfs, so I was getting the address not the value, and the actual problem was a couple missing curly brackets in my tool changer program.

Thanks,
Moray

On Fri, Apr 1, 2016 at 12:32 AM, Tom Kerekes tk@... [DynoMotion] <DynoMotion@yahoogroups.com> wrote:
 

Hi Moray,

No sorry there isn't.  There shouldn't be any mysteriously used variables by KMotion or KMotionCNC.  Only ones that you have configured to be used one way or another.

Regards
TK



On 3/31/2016 2:46 PM, Moray Cuthill moray.cuthill@... [DynoMotion] wrote:
 
Hi,

is there a list anywhere showing what UserData addresses are used by KMotion/KMotionCNC?

I'm finally getting around to installing the new computer on my lathe, and spent a while trying to work out why I couldn't get a valid value to transfer via Modbus to my toolchanger PLC, and after much head scratching, I finally realised that UserData[6] was being updated by something else. Meaning as soon as my C program updated it, it got changed to another value (something starting with 2 with about 7 or 8 digits).
Now the same UserData was used with Mach, so I'm guessing something related to KMotionCNC that is causing the problem?

I went through all the programs I use, and couldn't see anything else using UserData[6], and I have my own header file where I declare all the constants I use to ensure I don't use any duplicate UserData or Bits.

Thanks,
Moray