Forum Rule: Always post complete source code & details to reproduce any issue!

Search:

Type: Posts; User: defragster

Search: Search took 0.01 seconds.

  1. Not sure what the question is? Or if this...

    Not sure what the question is? Or if this presents a usable answer :)

    serialEvent1() is not based on interrupts - just called on each exit of loop() or use of delay() in user code. The Teensy...
  2. This seems like a very robust platform where the...

    This seems like a very robust platform where the underlying library gives a great user friendly 'interrupt' driven utility without the hazards of rolling your own - as long as you respect the buffers...
  3. As a [contrived] demo of the potential and use of...

    As a [contrived] demo of the potential and use of serialEvent() - this worked well with 2 ports on one Teensy. I just cross wired two 220000baud ports from 3.1 to LC and they work as it was written...
  4. This was just a proof of concept and example for...

    This was just a proof of concept and example for the Serial Event. There isn't much on it - but it works amazingly simply and amazingly well so not much to say.

    The \n is stored In the string and...
  5. Jp3141 - This was my first sighting of that...

    Jp3141 -
    This was my first sighting of that code construct :: inputString += inChar; and it apparently works to treat the indicated memory as a null terminated string. You'll note that after...
  6. High Speed serialEvent() loop back

    I took two wires on EACH an LC and 3.1 from 0:RX1 to 8:TX3 and 1TX1 to 7:RX3 to make a loop from Serial1 to Serial3 [ I want to use SPI so Serial2 and #9&#10 were used ]

    Using the above info I...
  7. Good Info duff. Both the impact/value of yield()...

    Good Info duff. Both the impact/value of yield() and the ease of use of serialEvent1(). Based on the .cc/tutorial it has a more complete example showing you don't have to be afraid of doing work in...
Results 1 to 7 of 7