Basic Micro Studio Issue?

[tom_chang79]

I’m just getting back into the world of robotics again, so I loaded my old Hexapod code in Basic Micro Studio (was previous using 8.0.15).

Now the compile comes up with error:

hpulse var slong(6)		;pwm offset for the Hip Horizontal Servo

Error: FILE C:\...\PHOENIX.BAS(LINE 281) : [TOKEN SLONG] : Bad ALIAS definition

Does anyone know why the compiler is complaining on this variable declaration? I believe the compiler is thinking that I’m trying to assign an alias hpulse to a variable “named” slong.

But what I want is a 6-element array, named hpulse, type is signed long (slong).

???

I tried this too:

var slong hpulse(6)

It didn’t like it…

[tom_chang79]

Here is the excerpt from the manual after reviewing the syntax again:

Example
Suppose you want to store values for 5 temperature sensors in an
array. Each sensor requires a WORD value. Define the array as:
temp var word(5)
This sets aside 5 “words” in RAM for your array, numbered 0 to 4.
Note: Atom BASIC numbers arrays starting from 0, so the first value
is arrayname(0) etc. The last value is arrayname(4) in this case.6
You can access each value as if it was a separate variable, for
example you can access the third value as:
word(2)

6 If you find counting from 0 confusing, simply define your array to have one more cell
than needed, and ignore cell 0. This wastes one cell, of course.

This doesn’t make any sense. Does the author mean temp(2) holds the third value in this array?

[zenta]

Hi,

What Basic Micro Studio version are you using? I believe there was some issues with the slong variable. Make sure you are using the latest version. Check this thread: lynxmotion.net/viewtopic.php?f=4&t=5463&start=48

[zenta]

@tom_chang79

Does the author mean temp(2) holds the third value in this array?

Yes, temp(2) holds the 3. value.

[innerbreed]

My guess is, that there is a duplicate variable defined somewhere else in the code. Maybe not but worth checking.

[kurte]

Welcome back,

As Zenta mentioned, I had problems with SLONG not working in several builds, so it could easily be that. But Innerbreed could also be right.

Try compiling it, by changing SLONG to LONG. If that compiles then you know that you ran into my bug. Try downloading the latest studio…
downloads.basicmicro.com/downloa … 0-0-25.exe

Good Luck
Kurt

[zenta]

@kurte

Try downloading the latest studio…
downloads.basicmicro.com/downloa … 0-0-25.exe

1-0-0-25 ! I thought 24 was the latest, whats new with this release? Maybe the “build to build” thread should be updated?

[kurte]

@zenta

1-0-0-25 ! I thought 24 was the latest, whats new with this release? Maybe the “build to build” thread should be updated?

Yep, not much to report…

[tom_chang79]

Thanks for all the helpful suggestions guys!

It HAS to be the Basic Micro Studio’s compiler. Since I’m trying to compile the last base-line code that was working. I just wanted to compile it to make sure I clear out this “sandbox” code that is still resident in my hexapod, which makes my hexapod contort as it tries to destroy its own servos…

Just wanted to compile the last known working code so I can figure out what the heck was I doing with it…

Last I remember, I think I was correcting a flaw in my IK code, but this last baseline code has some basic functionality like allowing it to walk forward, back, sideways, etc…

I can’t wait til Basic Micro Updates their manual, there’s quite a handful of erroneous examples and mistakes in there. One of which was quoted above…

I wonder if Acidtech is reading this thread?

Yup it WAS the compiler, I was uninstalling the old BMS and installing the latest BMS and it compiled fine, with 0 errors… Now to fire up the servo power’s switch to see what it does…

[robotdude]

There is a new work in progress manual on the BM website…

[acidtech]

The SLONG variable problem should be fixed. Please confirm using the latest beta release. If it still happens let us know.

The BasicMicro forums always has the latest beta release in the News section.