Re: [robocup-rescue-s] new kernel

Dear Utku and all,
In addition to what Mr.Saboorian said, you should remove the zero that in
previous versions ought to be inserted as termination mark at the end of
ID's list.
There are some other points that should be mentioned,

- In page number 4 of the documents released with 0.49.4 ver there is an
example for string encoding, that the first value should be changed to 0x0C
instead of 0x0D

- the property type of building appexes -which is a list of integers- is not
specified in the documentation that is 37.

- I think there is no need to insert zero bits in last bits of messages. -i
am not certain-

 Kindly Regards,

On 5/1/06, Mohammad Mehdi Saboorian <saboorian@gmail.com> wrote:
>
> Dear Utku,
> Although it has not been specified in new protocol documentation, you
> have to insert a length field before path plan, I mean if your route
> is 100, 101, 102 you should submit
> 3 100 101 102. If you're using yab api, you should only change akMove
> method to include this new field.
>
> Have fun,
> Mohammad
>
> On 5/1/06, Utku Tatlýdede <utkutatlidede@gmail.com> wrote:
> >
> > Dear All,
> > I can work with 0.49.3 but 0.49.4's kernel is when my agents sends move
> > command. Is there any team that uses 0.49.4?
> > _______________________________________________
> > robocup-rescue-s mailing list
> > robocup-rescue-s@mailman.cc.gatech.edu
> > https://mailman.cc.gatech.edu/mailman/listinfo/robocup-rescue-s
> >
> >
> >
>
> _______________________________________________
> robocup-rescue-s mailing list
> robocup-rescue-s@mailman.cc.gatech.edu
> https://mailman.cc.gatech.edu/mailman/listinfo/robocup-rescue-s
>
>
>

--
Hossein Azizpour,
Member of S.O.S team,
Robocup Researches Center,
Amirkabir University of Technology,

_______________________________________________
robocup-rescue-s mailing list
robocup-rescue-s@mailman.cc.gatech.edu
https://mailman.cc.gatech.edu/mailman/listinfo/robocup-rescue-s
Received on Mon May 01 12:24:30 2006