Lynxmotion Tech Support

I'm glad I asked... In this same topic, post 46 you came up with the idea about how to connect the extra command buttons. The only thing is that the drawing shows an extra column on P17. And the commend in the code (like above) shows an extra row on P9. This got me confused.
But row it is then. A row doesn't need an extra resistor though.

A Arduino Mega would be cool to try. But since you guys are still in the prototype stage I'm thinking of a solution for in the meanwhile.

Thanks for the help!

Xan

_________________
[b]Share, Use and Improve![/b]
Digging trough: [i]Theory of Applied Robotics: Kinematics, Dynamics, and Control[/i]
Xan's YouTube Channel
http://www.youtube.com/xanore

Yep, Zenta moved the extra row to P9 so he would have the Analog capable pin P17... Yep, did not need extra resistor.

As you mentioned, the Arduino version is a prototype, but aren't they all As I mentioned, it should not be hard to to convert to Arc32, but have not tried.

Kurt

Hi Kurt,

I've got the buttons connected and am able to scan, and actually find, the other modules.

I'm still a bit confused about the function of the buttons and the structure of the menu. But I'm sure you (or Zenta) can clarify it for me

The 4 buttons are marked X, Y, Y and Z. If I got it right the layout is:
bit 0 = W = esc
bit 1 = X = enter
bit 2 = Y = down
bit 3 = Z = up

Here come my noob questions:
If I'm in the home screen and push the down button I loop trough the following entries
home -> Cal Joystics Move Full Ranges -> Current My: 0000 -> Current DL: 0003 THEX New: -> Select By Name -> Right: 128 128 ->home

home
Home screen showing normal values

Cal Joystics Move Full Ranges
How does this work? I can move all joysticks, buttons but nothing happens. Only if I hit X (enter) I get *** Error ***s

Current My: 0000
This screen is a bit mixed up. I've got a lot of non-ASCII chars in there. No idea why. Maybe it is reading something for memory which is corrupted?

Current DL: 0003 THEX New:
This shows the current selected XBEE module. Can it do something else? What's the "New:" for?

Select by name
This is where I can scan for modules and select the XBEE module
A - Scan modules
D - Delete
RJoy - scroll found XBEE modules
Enter - Select XBEE module

Right 128 128
What does this menu item do? It seems to show the left or right joystick values. Both my left and right joysticks are not totally stable in the home position so this screen keeps jumping between left and right.

Thanks! Xan

_________________
[b]Share, Use and Improve![/b]
Digging trough: [i]Theory of Applied Robotics: Kinematics, Dynamics, and Control[/i]
Xan's YouTube Channel
http://www.youtube.com/xanore

Hi Xan,

Note the Esc, button I don't think has been used...

Calibrate... You need to move both joysticks to their sort-of max extents in both X and Y directions. Note: I often don't diagonalsnals here as I want the straight up top to be the maximum value... You also need to move the sliders to their minimums and maximums. The code checks to see if all of these values are above or below some certthresholdsolds.

Current My: is whatever 16 bit hex value you want. If you are seeing corrupted characters on this display, it is probably because the interrupts are screwing up the text... Will need to look sometime. Note: 0 usually works fine.

Current DL: This was originally the only way to choose a robot. You had to know it's hex MY value and then enter that into the keypad. But for the most part, I use the Select by Name for the majority of the time.

Right 128 128 - Is often the standard display. That is, if you move the right joy stick you will see values for the right joy stick. If you move the Left joystick, the word right will turn to left and show the values for the left joystick. Likewise for sliders. This freed up the 2nd line of the display to show things, that are sent back from the robot, like what the new gait is or the like.

Kurt

Hi Kurt,

Thanks for the extreme quick answers!

Calibrate: If I got it correctly I only need to move both joysticks to the maximum positions to calibrate them. No need to confirm the movements then. Can you tell me why enter gives me an error?

Current my: Clear, this is the XBEE MY setting (16-bits source address). Need to check the interrupt stuff for the display mixup

Current DL: Clear, works like a charm!

Right 128 128: this doesn't work for me since the display is still blinking to "left". This might need a threshold.

Awesome work! I will try to get THex to walk now

Xan

_________________
[b]Share, Use and Improve![/b]
Digging trough: [i]Theory of Applied Robotics: Kinematics, Dynamics, and Control[/i]
Xan's YouTube Channel
http://www.youtube.com/xanore

Calibrate, you do need to hit enter, if it is saying error, than one of the Analog inputs has not been moved through enough for it to be happy. Usually I forget to do the Sliders.

A quick look at the code, it expects that thanalogog inputs on pins:
AtoDOrder bytetable 3, 2, 1, 0, 19, 18

have been moved through the range. It sort of assumes the first 4 are the joysticks of our DIY controls and don't have a full range 0-1024, so it assumes the minimum for these must be < 450 and the maxs must be > 575. It assumes the sliders have a larger range and the min must be < 50 and the max > 975. These should be table driven, but...

If the Right ... is not working, how about the amain page, do all of the values appear to change properly?

Got to run
Kurt

Hi Kurt,

I've got the communication running with help of your XBEE THex version you've posted. I left something in for the PS2 remote which caused all the problems.

Now, when I turn on the THex it will start walking automatically. So I started to dig deeper in to your DIY remote XBEE code. While fiddling around with the code, I got the strangest compiler error of all...

When I enable the DEBUG = 1 variable in the "diy transmitter.bas" file. (remove the ') The compiler gives an error

Build
When I double click on the error line, the Workspace opens an extra file "ld.exe" with the text "MZ" in it. When disable the DEBUG variable again, the program builds like a charm.

Did you see this behavior before?

Thanks, Xan

_________________
[b]Share, Use and Improve![/b]
Digging trough: [i]Theory of Applied Robotics: Kinematics, Dynamics, and Control[/i]
Xan's YouTube Channel
http://www.youtube.com/xanore

Hi,

I'm not sure but I think I've seen something similar. You are not running out of memory space on the BAP28? Just a guess..

EDIT: http://www.lynxmotion.net/viewtopic.php?f=4&t=5463&p=62063&hilit=region+text+is+full#p62063

_________________
[b]Kåre Halvorsen, Zenta[/b]
-----------------------------------------
Zenta's blog
http://zentasrobots.com/
Zenta's YouTube channel
http://www.youtube.com/ZentaOlbaid
-----------------------------------------

Ah I see, This explains a lot.

Thanks!

Just sucessfully calibrated the remote. Nice Piece of programming work Kurt!
The THex still is walking on it's own. I'll hook up my logic analyzer Thursday to see what's going over the "line". Now it's time to go to bed (23:20 alread )

_________________
[b]Share, Use and Improve![/b]
Digging trough: [i]Theory of Applied Robotics: Kinematics, Dynamics, and Control[/i]
Xan's YouTube Channel
http://www.youtube.com/xanore