Okay, first: Ashes on my head! Before I tried to post my code, I compared your 485sendms and 485receivems with my code.
In my Sender Programm where no kind of this:
Code: Select all
while(HSOutputBufferOutPtr() < HSOutputBufferInPtr())
Wait(1);
and in my Receiver Programm where no kind of this:
Code: Select all
while (mlen == 0)
mlen = HSInputBufferInPtr();
I noticed how important these 2 lines are. The situation is now much better, but there are still problems.
In 100 messages up to 5 messages will be lost. Also sometimes the message won't arrive successfully.
I check this with my code, but also with your example programms 485sendms and 485receivems. Same results!
If you activate the last "wait" command in the 485sendms and set it up to 500 or 1000ms, than you can see it with your own eyes. "Goofy" will be crippled! I think the receiver will read the string while the sender writes it!?
My
Sender
Code: Select all
//Master Programm
byte laengenachricht;
string versenden, empfangen;
int i = 0;
sub SendeNachricht(string versenden)
{ //Sendevorgang
laengenachricht = ArrayLen(versenden);
SetHSOutputBuffer(0, laengenachricht, versenden);
SetHSOutputBufferOutPtr(0);
SetHSOutputBufferInPtr(laengenachricht);
SetHSState(HS_SEND_DATA);
SetHSFlags(HS_UPDATE);
}
void WaitForMessageToBeSent()
{
while(HSOutputBufferOutPtr() < HSOutputBufferInPtr())
Wait(1);
}
task send()
{
versenden += NumToStr(i);
SendeNachricht(versenden);
WaitForMessageToBeSent();
i++;
Wait(1);
}
task connect()
{
SetSensorType(IN_4, SENSOR_TYPE_HIGHSPEED); //Verbindung zum zweiten NXT
SetHSState(HS_INITIALISE);
SetHSFlags(HS_UPDATE);
SetHSInputBufferInPtr(0);
}
task main()
{
int laststate = 0;
versenden = "";
empfangen = "Nichts bekommen";
SetSensorTouch(IN_1);
start connect;
while(true)
{
if(SENSOR_1 == 1)
{
versenden = "WASSERER";
laststate = 1;
}
else
{
versenden = "wasserer";
laststate = 0;
}
start send;
WaitForMessageToBeSent();
Wait(500);
}
}
My
Receiver
Code: Select all
//Slave Programm
byte laengenachricht;
string versenden, empfangen;
int i = 0;
task connect()
{
SetSensorType(IN_4, SENSOR_TYPE_HIGHSPEED); //Verbindung zum zweiten NXT
SetHSState(HS_INITIALISE);
SetHSFlags(HS_UPDATE);
/
SetHSInputBufferInPtr(0);
while(true)
{
laengenachricht = 0;
while (laengenachricht == 0)
laengenachricht = HSInputBufferInPtr();
GetHSInputBuffer(0, laengenachricht, empfangen); //empfangen der Nachricht
Wait(2);
SetHSInputBufferInPtr(0);
Wait(1);
TextOut(0, LCD_LINE2, empfangen);
}
}
task main()
{
int laststate = 0;
versenden = "";
empfangen = "Nichts bekommen";
SetSensorTouch(IN_1);
start connect;
}
If you press the touch sensor, the the string will be changed to upper case. Sometimes just some of the letters will be changes. Same behavior like goofy.
I think it's practicable to intercept this errors inside the program. But maybe it is possible that the Firmware takes care of some of this problems? Some error correction or useful errorcodes. A stable concept of token based protocol. In most cases an unidirectional communication won't be useful.
With NXC have you done a great job! But maybe you would be able to improve it even more with this feature.
Thank you very much.
alphasucht
