Register Account

Login Help


  • MAREA Q & A

    Select a question below about MAREA set-up and operation. Click on the question to expand for the answer.

  • Multiple MAREAs


    We are actually getting more than one MAREA in the room here in Atlanta and that is led me to consider the avoidance of conflicts when using packet.  With the XBee board I can create MAREA pairs.  For example the Mills Springs MAREA is on channel two and my MAREA is on channel four.  Each unit - a PC/laptop/2 meter packet rig is a complete unit.  The loopback test works fine with each unit and one does not interfere with the other as we are using different channels.  The challenge comes when we go to packet.  Both BoeBots are named MAREA.  When using packet UISS sends the line MAREAF50..etc, and the the local digipeater sends it right back with the message "You have been digipeated."  The loop back program then reads the line and sends to the local MAREA (mine) as well as the MIll Springs MAREA on the other end of the circuit.  Correct so far?  If so, not the desired behavior.  Especially if, as may happen, The Mills Springs students are driving the Lovett BoeBot while Lovett is driving the Mills Springs BoeBot

    Now I am guessing there is nothing unique about the name, MAREA.  The Mill Springs BoeBot could be MAREA and mine could be FRANK as long as the name in the code matches the name in the command string, I hope.  Are there any restrictions on the size of the name?  I am thinking an alternative is MAREA1, MAREA2, etc.  But that brings up the question of the loopback test.  I am guessing the name "MAREA' is hardcoded into the loopback <TEST> program?  If so, that could be handled by making some quick coding changes when going from test to production.  If all of the machines are on different channels, even if they are all named MAREA for testing at least the entire fleet should not take off all at once!  I suppose another answer is to simply turn off the BoeBot not being driven.  The kids this semester did have a great time naming the BoeBot - it made it "theirs."

    An better alternative if you ever get the inclination might be to modify the Loopback <TEST> program so that the BoeBot name is a user defined variable same as the comport.

    I have had a request to program in a delay to better simulate the time it takes a radio wave to get from earth to a distant MAREA.  I am planning to add a PAUSE 3000 at the appropriate place in the code to generate a three second delay between the receipt of the command string and its execution.  A bit of a cheat in that the transmission is instantaneous with the delay on the receiving end where in the real world it is the other way around but the effect is the same - a delay in time between sending a command and the execution of the command.

    Enjoying all of this greatly - by end of the school year I may have four schools here in Atlanta up and playing the MAREA game over the local packet repeater.

    Please advise,

    John Kludt, W4SQC



    Sounds like you guys are making the most of MAREA.


    To answer your specific question, the call sign of the robot is limited to 5 characters maximum.  I believe that they can be any combination of characters, but I am not sure of upper or lower case sensitivity.  You might try it and see what happens.  To change the call of the robot to make it unique, you need to change this line of code in the MAREA main program. Bs2:


    SERIN 15, 813,[WAIT ("MAREA") ]


    In your case change MAREA to FRANK or CUGAR or BEARS or CANDY or STARS or VENUS…there are bunches of 5 character calls that can be school unique.


    On the loop back program, I made a change to the program that has a field for entering the robot call sign.  It defaults to MAREA, but you can enter any 5 character call that you want.  But it has to match the call of the robot you want to control.  Because the program is an exe file, I put it in this DropBox location so you can download it:  Click here to view


    Just put it somewhere on your hard drive where you can find it and run it from there.  Just to make sure it works for you (it worked when I tested it here with FRANK), don’t over write the current loopback until you are sure it is okay.


    So you should be all set for multiple robots on at one time.  As you know, make the XBee modules paired up, and match the call sign of the robot with the call you enter in the loopback (for the loop test function) and in the UISS text fields, and it should all work okay.


    Let us know how it goes.

    Mark Spencer, WA8SME



Instragram     Facebook     Twitter     YouTube     LinkedIn