Arduino while loop multiple conditions serial#
Serial.println("Now reading serial input") While (Serial.available() = 0) // Wait for serial unput Serial.println("Waiting for serial input (in setup)") So it broke again! The loop is terminated after the 1st character. intill I removed the debugging (Serial.print) statements. So, as a workaround I retrieved the 1st character separately and then checked if still more character are available to continue the while loop. In setup() as in loop() it retuns always 1 (or 0), regardless of the number of characters entered. Update: Some more debugging showed that the problem is in the Serial.availble() function.
} //void fParseSerial( void * parameters ) XSemaphoreGive( sema_ReceiveSerial_LIDAR ) XEventGroupSetBits( eg, evtParseLIDAR_ReceivedSerial ) XQueueOverwrite( xQ_LIDAR_Display_INFO, ( void * ) &sSerial ) If ( xSemaphoreTake( sema_ParseLIDAR_ReceivedSerial, xTicksToWait0 ) = pdTRUE ) // wait on semaphore The > is used to kick you out of the serial loop for further processing.Īs an example: void fReceiveSerial_LIDAR( void * parameters )ĮventBits_t xbit = 圎ventGroupWaitBits (eg, evtReceiveSerial_LIDAR, pdTRUE, pdTRUE, portMAX_DELAY) With the issue you reported, One time through you'd receive the. If, in the serial buffer their is a, such a scheme allows you to separate your sentences. So you do not start to save any data till a. Now if you get 345> you have a trigger to reject the sentence. If you sent, you have the beginning and end of a sentence. Consider you sent 12345 but, depending on where the Arduino is you get 345, which is not what you sent, so you'd want to reject 345. I like to think of my Serial statements as sentences.
0 kommentar(er)
