Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[SOLVED] Accessing macro slave variables above i1000
#1
Hello,

I am new to Macro, so please excuse my terminology.

I need to set a parameter on a macro servo drive, which, from what I understand is done with MacroSlave0,i1024 type commands. It seems that anything above i999 gives me an error on the terminal of:

MacroSlave0,i1000
stdin:28:1: error #21: ILLEGAL PARAMETER: MacroSlave0,i1000

So is this an error of the command processor, or are these parameters not accessable? Our variables on our drives start at i1024.

Also, am I able to access these from C calls? the routine I'm using is programmed in C so I could use this as a workaround if it is possible. Is there an example of this available?

Thanks,
KEJR
Reply
#2
(02-09-2011, 02:25 PM)KEJR Wrote: I need to set a parameter on a macro servo drive, which, from what I understand is done with MacroSlave0,i1024 type commands. It seems that anything above i999 gives me an error

KEJR - what firmware and IDE rev are you using? In the past I have used IDEs/firmwares ranging from the July release on up with MACRO. I am not seeing the problem with MACRO i vars with any of these releases.

We have used the Command() function to get/set variables across MACRO.


Davis

Reply
#3
(02-09-2011, 05:22 PM)DavisG Wrote: KEJR - what firmware and IDE rev are you using? In the past I have used IDEs/firmwares ranging from the July release on up with MACRO.

I am using:

IDE 1.1.2.45 (9/28/2010)
Firmware: 1.2.1.5

Note: I can access macro ivars, just not anything after i999. Unfortunately the Copley amp parameters for macro start at i1024.

Thanks,
KEJR

Reply
#4
(02-10-2011, 07:33 AM)KEJR Wrote: IDE 1.1.2.45 (9/28/2010)
Firmware: 1.2.1.5
You could try moving to the February release firmware and IDE - MACRO support is getting better. The one caveat is that if you bgcplcs you may need to change the typecasting in your code to make it compile - I had to. The new IDE has gone to a C++ compile of the bgcplcs rather than a C one.

It may be that the ppmac is doing something like querying the macro device, and setting what commands are allowed based on that. If so, the Copley amp may not be accurately mapped. I'll ask.

Reply
#5
Hello,

Where is the Feb release? I went to the link in the "latest versions" thread and the latest version I can see is July 2010.

Are you saying that the "Background programs" are now compiled with g++ instead of gcc? I've been wanting OOP on this thing since I've started with it but couldn't justify ditching the IDE to get it. If so I am pretty happy!!!!!

Thanks,
KEJR
Reply
#6
(02-10-2011, 02:47 PM)KEJR Wrote: Hello,

Where is the Feb release? I went to the link in the "latest versions" thread and the latest version I can see is July 2010.

Are you saying that the "Background programs" are now compiled with g++ instead of gcc? I've been wanting OOP on this thing since I've started with it but couldn't justify ditching the IDE to get it. If so I am pretty happy!!!!!

Thanks,
KEJR

because they are listed in alphabetic order, January 2011 comes before July 2010 in the latest release lists - look again.

Yes - g++ now.

Davis
Reply
#7
Davis and KEJR,

We are passing the Background C Programs through C++ complier since it provides better syntax checking. The Background C programs in the end are complied with GNU C compiler and we don't have C++ support for Power PMAC yet.

On reading MACRO slave variables, using MacroSlave commands, released in firmware version 1.3 you can access MI variables numbered up to 1999.

Regards,
Sina Sattari
Hardware Engineering Manager
Delta Tau Data Systems, Inc.
Reply
#8
(02-10-2011, 04:37 PM)Sina Wrote: On reading MACRO slave variables, using MacroSlave commands, released in firmware version 1.3 you can access MI variables numbered up to 1999.

Firmware from 2/10/2011 can access up to 4095 MI vars.

Reply
#9
(02-10-2011, 04:14 PM)DavisG Wrote: because they are listed in alphabetic order, January 2011 comes before July 2010 in the latest release lists - look again.

I am at home now and can see the Feb 2011 folder. I'm 99% positive that the folder was not there this morning from my work computer. Not sure if permissions apply or if the folder went missing for a while, or I am crazy.. maybe all of the above.

Thanks,
KEJR
Reply
#10
Just to confirm, Feb2011 folder still not visible in FTP in internet explorer 8. It is visible from my FTP client built into windows file manager, so I am not sure what is going on there. Just wanted to mention it in case others have the same issue.

At least I know I'm not crazy now... well... in that regard at least.

KEJR
Reply
#11
(02-11-2011, 08:17 AM)KEJR Wrote: Just to confirm, Feb2011 folder still not visible in FTP in internet explorer 8.

Ummm - I am seeing it in IE 8.0.7600.16385. Maybe you've got the old directory in the cache? Try refreshing to see of it comes up?

Davis
Reply
#12

(02-11-2011, 09:11 AM)DavisG Wrote: Maybe you've got the old directory in the cache? Try refreshing to see of it comes up?

Yeah, it must have been the cache. I hit refresh and it came up. Anyhow, I'll be using the FTP client from now on!

Thanks,
KEJR
Reply
#13
Just an update for anyone reading this, the macro I vars above i999 are now accessable. Feb 2011 release worked. Thanks!
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)