OK here are some specific criticisms - while (Serial.
ARDUINO WHILE LOOP TIMEOUT SERIAL
There is a code issue.įor non-blocking timeout - I suggest you look at timing your serial reception with millis(), and give up after the appropriate period as needed. If Serial1 makes your program run worse, then you have a completely different problem than the choice of serial implementation. If you have hardware serial - it is a complete waste of cycles and reliability to implement a bit-bashing 'soft' serial interface. These suggestions weren't specifically to address your program symptoms. So, if any part of your code uses a delay (), everything else is dead in the water for the duration. The delay () ties up 100 of the processor. During a delay () call, you can’t respond to inputs, you can't process any data and you can’t change any outputs. Serial.println("Input timeout from slave") The problem is that delay () is a 'busy wait' that monopolizes the processor. Incoming = mySerial.readString() //Read slave While (Serial.available() 50000) break // Timeout NOTE: The serialEvent () feature is not available on the Leonardo, Micro, or other ATmega32U4 based boards. When loop () never returns serialEvent () is never called. On (at least) Arduino Uno we find that serialEvent () simply runs sequentially with loop (). Try this: /*-( Import needed libraries )-*/Ĭonst int cx = 8 //DE/RE Controling pin of RS-485 This code is based on Tom Igoes SerialEvent example. The code would be easier to follow if the 'ok' variable was local to each function and not global. The output shown in "here is the image that not work properly:" can't be from the sketch you posted so you must have changed something between the two pictures. Arduino milis() is an interrupt driven function meaning that it is always operating in the background while your code is working. Serial.println("There is something wrong ") Incoming=mySerial.readString() //Read slave Serial.println("Please enter the slave ID ") //Prompt User for input Do not expect to read more than one character once available () is true. MySerial.begin(9600) //Using mySerial Port You should never use delay () in loop (). String incoming //Declare a String variable to hold your name SoftwareSerial mySerial(10, 11) // RX, TX
Int cx = 8 //DE/RE Controling pin of RS-485 Here is the complete code: /*-( Import needed libraries )-*/ So a typical way millis() is used to track time is, in setup, to store it's current value into a variable and add your timeout period value to it: // timeoutAmount is defined at head of program. It will response to the last slaveID instead of the current Id I type in the serial monitor. It works fine if I don't have the timeout function in the while loop. There are two ways to know how long each iteration of loop will take: Profiling: Actively time each iteration of loop, though be warned, the act of timing will affect the amount of time taken. And waiting for the right slave to respond. The more code you put in loop the longer loop will run. I get slave ID from MEGA serial monitor and send it to slaves via rs485 bus from softserial port. I suspect that you're missing a #include for the DFR_LCD_Keypad.I setup MEGA 2560 as master and have 3 slaves. The line #define btnSELECT 4) should not have a semi-colon at the end. If i use the "if/else" function it works fine. buttonState = digitalRead(buttonPin) īuttonState = digitalRead(buttonPin) // read the button In other words you have to read buttonState each time through the loop to detect the change. That won't work because there is no way for buttonState to change once in the loop.
0 kommentar(er)
