Could you develop the advantage of your solution compared with the bitlash one ?
Well it is not a shoving match against messenger and bitlash that's for sure! If you read the start of the thread, you will see I was looking for a light weight communication solution. Bitlash is not lightweight (takes up almost all the memory on a tamega168) and is not a simple communication protocol but a complete shell. Messenger is lightweight and very simple to implement.
Excellent library I must say. Thanks for it. I am having some troubles trying to use Serial1 on the Arduino Mega. I basically took the example that is provided and changed Serial to Serial1. Can anyone take a look at my code below and help me please?
#include <Messenger.h>
// Instantiate Messenger object with the default separator (the space character)
Messenger message = Messenger();
// Create the callback function
void messageReady() {
int pin = 10;
// Loop through all the available elements of the message
while ( message.available() ) {
// Set the pin as determined by the message
digitalWrite( pin, message.readInt() );
pin=pin+1;
}
}
void setup() {
// Initiate Serial Communication
Serial1.begin(9600);
Serial.begin(9600);
// Attach the callback function to the Messenger
message.attach(messageReady);
}
void loop() {
// The following line is the most effective way of using Serial and Messenger's callback
while ( Serial1.available() ) message.process(Serial1.read () );
}
oops sorry I should have explained.. Well really it just doesn't work. when i used the default Serial it did light up the LED on pin 13 upon entering the following text
"1 1 1 1 1 1 1 1 1 1 1 1 1" followed by Enter. However as soon as i switch the Serial to Serial1. nothing happens. I can enter a million "1 1 1" followed by enter but the LED does not light up. I hope i have explained myself well. if you need any further details please do let me know
Well, the way you set up your code, Messenger processes messages comming in through Serial1. You therefore have to send the messages to Serial1 instead of Serial. What external circuitry are you using to do so?
When i change my code to serial then it uses the on board FTDI chip and it works. however on the other port i have a MAX233 chip which works fine because when I run the monitor I can see what the Arduino Mega is sending out(Serial.println). it just doesn't seem to pick up what I send to it through the serial monitor
I am sorry, I still do not understand your configuration.
The Arduino Mega is plugged into your computer's USB (that is Serial).
You have a MAX233 plugged into RX1, TX1 (Serial1). So you generate RS-232 level communication with the chip and that is plugged where? What is connected on the other side of the MAX233?
MAX233 chip which works fine because when I run the monitor I can see what the Arduino Mega is sending out(Serial.println)
Which monitor? The Arduino IDE's? Doesn't it only work with RX,TX and Serial? Do you mean you are echoing something like:
The second serial port is connected to the Serial port of a Computer. and I am running tera term pro(as a serial monitor). eventually I would like to have Processing(www.processing.org) send out stuff to the Arduino but that would be at a later stage. so for now I have connected Serial1 to the computer via a MAX233 chip. My apologies for not explaining myself well.
Ok, so you are sending messages from tera term pro to Serial1.
You know the link works because you have tested it with some code like:
while (Serial1.available() ) Serial.print(Serial1.read());
that lets the Arduino IDE's Serial Monitor echo whatever you send from tera term pro.
Are you sure that tera term pro is sending carriage returns? Carriage returns must be sent to terminate a message.
Please test the following code. Send either a "0" or a "1" followed by a carriage return to either Serial or Serial1. A 1 will turn on the LED at pin 13, a 0 will turn it off. Also, all data received by Serial will be echoed to Serial1, and the opposite is also true.
#include <Messenger.h>
Messenger message = Messenger();
Messenger message1 = Messenger();
void messageReady() {
while ( message.available() ) {
// Set the pin as determined by the message
digitalWrite( 13, message.readInt() );
}
}
void messageReady1() {
while ( message1.available() ) {
// Set the pin as determined by the message
digitalWrite( 13, message1.readInt() );
}
}
void setup() {
// Initiate Serial Communication
Serial1.begin(9600);
Serial.begin(9600);
// Attach the callback function to the Messenger
message.attach(messageReady); // Serial
message1.attach(messageReady1); //Serial1
}
void loop() {
int data;
// Serial1
while ( Serial1.available() ) {
data = Serial1.read ();
Serial.print(data,BYTE); // Echo data on other port
message1.process(data); // Process data
}
// Serial
while ( Serial.available() ) {
data = Serial.read ();
Serial1.print(data,BYTE); // Echo data on other port
message.process( data ); // Process data
}
}
Please report any and all error messages that this code generates. Please also include what is received by both serial monitors.
I tried the code that you posted. The results were:
No error message
So i had 2 monitors open. One was monitoring "Serial"(USB) and the other was monitoring "Serial1". When i type into "Serial" it turned the LED on and off the way it was supposed to. and the "Serial1" monitor would also echo back whatever i typed with absolutely no problems. however when i type into "Serial1" nothing happens to the LED and Nothing is echoed back on the "Serial" monitor
to me this confirms that the problem is not with Messenger but with your input/output of Serial1.
The echo is not part of Messenger and should work without it. Check your connections and make sure that whatever you send to Serial1 is echoed to Serial. Once you have a solid bi-directional communication between both (that both monitors echo the other), you can try to add Messenger.
Thanks a lot for your help.. it turns out that the MAX233 was just working one way the other direction was faulty.. i replaced the chip and it works awesomeee!!!
Thanks again for the help and thanks to whoever made the library..
thanks for the lib,
the example supplied with ver 1.4 is for outputing values from the arduino which if i understand not what messanger is about, right?
"Messenger only provides methods for incoming messages. The internal Serial.print() functions work just fine for outgoing messages."
You are right.
Messenger only provides methods for incomming messages. The examples demonstrates how to receive messages with Messenger's messageCompleted() callback function but also demonstrates how to send messages so they can be parsed with the matching Messenger libraries for Max or Processing.
i might be missing something there, the comment of the example im refering to is
This example parses a message that contains the values
of an Arduino's analog inputs and displays them as rectangles.
The message must be composed of the readings of the 6 inputs.
Each readingis separated by a space (' ') and terminated
by a carriage return and line feed
is there somehwere an example with processing>arduino communication. i tried using the simpleMessage examples but that didnt work. those messanger support the simpleMess protocol
r a -> read analog pins
r d -> read digital pins
w d [pin] [value] -> write digital pin
w a [pin] [value] -> write analog pin
as a matter of fact i thinkn all this software protocols between arduino and the computer are bad education. i searched for serial.flush() and was directed to Arduino Serial protocol design patterns – todbot blog, i think this is the direction should go.
tommorow i have to explain conditions to a seeduino mega and a processingxp
this looks so shinny, waht does it do?
Beside the 2 following improvements:
1. define the variables as unsigned char
unsigned char rx_buffer_head = 0;
unsigned char rx_buffer_tail = 0;
2. use the following code to wrap the values
rx_buffer_tail = rx_buffer_tail + 1;
rx_buffer_tail %= RX_BUFFER_SIZE;
3. Tweak buffer size for your application.
what else can be done to improved the performance of Hardware Serial? I am stuck using 4800 baud
thanx
Mart
I will try to understand your posts as best as I can.
The Processing example supplied with the Messenger library works very with the Arduino example provided.
I might be missing something there, the comment of the example im refering to is [...] is there somehwere an example with processing>arduino communication. i tried using the simpleMessage examples but that didnt work. those messanger support the simpleMess protocol
As stated in Messenger's documentation: All of your host software code that you designed for SimpleMessageSystem should still be compatible with Messenger. You will simply have to modify your Arduino code.
So you need to modify the Arduino code to match the software code.
I think the simplest solution for you would be to use Firmata (try my version here)
im using a mega, which is unsupported (the changelog tells it does, everyone else it doesnt).
thanks for your support, i will have to warp my head around bytes eventually. i think its for the best.
i used some code from the previous link i mentioned and from this megaServo example.
you can try the following code (I can not test it):
#include <MegaServo.h>
#include <Messenger.h>
#define NBR_SERVOS 12 // the number of servos, up to 48 for Mega, 12 for other boards
#define FIRST_SERVO_PIN 2
MegaServo myServos[NBR_SERVOS] ; // max servos is 48 for mega, 12 for other boards
Messenger message = Messenger();
// Define messenger function
void messageCompleted() {
int i = 0;
while ( message.available() && i < NBR_SERVOS ) {
myServos[i].write(message.readInt());
i++;
}
}
void setup()
{
Serial.begin(115200);
message.attach(messageCompleted);
for(int i=0; i < NBR_SERVOS; i++)
myServos[i].attach(FIRST_SERVO_PIN +i);
}
void loop()
{
while ( Serial.available( ) ) message.process(Serial.read( ) );
}
From you host software, send something like the following ascii message (they are not bytes but string representations of the numbers):
"123 84 39 128 274 50 100 543 83 43 100 101"
Where each number corresponds to the position for the servo at that index (first number for first servo, etc). Do not forget to terminate the message with a carriage return!