Bot Board 2 Serial Port Controll

I will control my CH3-R via Serial Port. I upload the Powerpod program on the controller but the Serial Tool doesnt respond. The connection via PC and Bot Board Works but the robot doesnt move. The PS2 controller cabel is plugged on the BotBoard and the connection to SSC-32 is also plugged on Pin8. Is it necessary to remove the PS2 controller cabel before control the robot via Serial Port an wich master.pmp file is needed? I download the H3 VX.43 - Master.pmp file and use it to program the controller.

Greatings

Hi ExMachina,

This probably should be in the multileg forum and not here, but…

If I understand your question, you have created a new basic program using powerpod configured for serial communications. You have sucessfully compiled and downloaded it to your bot board. Not sure from description if you are using an Atom or an Atom Pro.

The real question is. What are you using on the PC side to send commands to your hex? Do you have a program that is generating the appropriate command packets?

Kurt

Hello Kurt,

okay let me explain my issue. I create a custom Serial Port Control Program with Powerpod to control the robot with my PC. To communicate with the Bot Board2 and the BasicAtomPro 28 I use the tool that is included in the powerpod tool. (shown in the Powerpod PDF Manual last page) I can connect to the BB2 via COM4 but the robot dont respond. I think the reason for this is the plugged PS2 cable on PIN 12,13,14 and 15 also the connection between the BB2 and SSC-32 on Pin8. I hope that clarifys the situation.

Greatings

Hi again,

Look at the program that was generated by powerpod. Look for the line that looks like:

SSC32 con p15

Change this line to P8 and recompile and download.

I hope that helps.

Kurt

You mentioned you are using the SSC-32. Is the green light on? if yes, does the green light go out and blink when receiving commands? Also, check that the proper baud jumpers are set for TTL serial communications on the ssc-32. Perhaps you did not switch it back to TTL comms so that it can be controlled by the bot board. Check manual for proper jumper settings for BBII comms.

If you want PC control, then The SSC-32 needs to have the baud jumpers set for PC control, again that is in the manual. If you are trying to control things via the PC and you have the cable connected to the BB2, this is wrong, you want the cable to be connected to the SSC-32 serial port with the appropriate baud jumper settings.

Hi Kurte,

I think that was the mistake. The Pin 15 on BB2 is reserved by the PS2 controller cable. I check this and let you know.

Thanks
Matthias

@SN96

The jumper configuration is set for PC control 38.4k Bauts and the Power Pod manual explains that the cable is plugged at the DB9 of the BB2 not the SSC-32. If that is a mistake by my side let me know.

I did not see kurtes post, the BB2 does use P8 instead of P15. Sorry, I was not clear about your question.

Hopefully I won’t confuse things further.

I’ve just been running the serial_CH_H3 program to control a 'bot built with a BB2 (Basic Atom) and SSC-32.

You should be able to leave the PS2 connected to to the BB2. 9600 baud (default on the serial_CH_H3 program).

You’ll have to disconnect from the serial_CH_H3 program when you want to program the Basic Atom.

You should have this line in the header of the BAS file generated by PowerPod:

;---- Serial Port Control (Bot Board / PC) ------

use pin 8 for SSC-32, but you should have had that already from a PS2 build.

If PS2 is not connected, then pin 15 works. It’s still bit-bang, so I don’t know if there’s any advantage.

Alan KM6VV

I removed the PS2 cable and connect the data cable on PIN 15 BB2 side. The connection works without problems but one short question. It seems that the walking abilities are better with serial port communication. Is this related by the code created by powerpod or related by the connection typ and direct controll via cable from PC?

Greatings
Matthias

Hi Matthias,

I think you are saying that the walking is better now with the serial connection than it did before with the PS2? The main portion of the code that powerpod is the same regardless of which input method is used. There was an issue recently with powerpod on an Atom Pro and there is a new powerpod control file up on the lynxmotion website to address that issue.

Glad you have it working now.

Kurt

Hi Kurte,

I use two separate .pmp files in PowerPod to create the custom AtomPro codes.

1st
vX.43 Temp Fix.pmp for PS2 controll mode
lynxmotion.com/Product.aspx? … #downloads
Webside advised this is only applicable for PS2 controll

2nd
vX.43.pmp for the serial port controll mode

The tutorial advised that the vX.43 Temp Fix.pmp file fixed the AtomPro bug.
lynxmotion.com/images/html/build99c.htm

The 2nd .pmp file makes the robot walk better but the actual file is the 1st one that make the robot walk a little bit choppy in PS2 mode. Which file is to use for the AtomPro equipped robot in general?

Greatings
Matthias

Hi again,

I think the main difference between the two files was to help a problem when the powerpod program was generating commmands to send to the SSC-32 to fast and not allowing the previous command to complete. So the walk was looking choppy.

The fix was to add a timer that remembered when the last SSC-32 command was issued and not to transmit a new one until enough time has elapsed. I don’t know if there is any reason why it is PS2 only. Maybe it was only tested on the PS2 as it is a temporary fix. In theory the fix should work in all three modes. But the short answer is to use whichever gives you the best results.

Kurt

I want the botboard II to receive commands from the pc (serial) and the ssc32 receives/transmits to the botboard II.

How do i set this up and is it at all possible? I.o.w. Does the botboard II has 2 serial ports?