The memory for the number of keystrokes is likely in your software somewhere. Unless you are really talking about a press on a key of the actual keyboard. (Some generations of computer users would deem this an archaic mode of operation.) A keyboard has a chip which will hold some number of keystrokes. This buffer holds on to them until the computer asks for them.
This is why some programmers flush this buffer before they trust the input to be actual. They just ask for X number of inputs (and throw those away) before using the next input. X is the size of the buffer in characters//bytes. About 32 or so.
sorry for any confusion, but i meant that there is a button hooked up to my arduino which is sending “hello” over the xbee to my receiving xbee which is plugged into my computer and is printing to the arduino ide serial monitor.
Could be that the loop to send out the data is getting stuck somewhere. Do you have any way to show an indication of data being sent from the xbee and receiving on the other side? If not, just as a thought, you could use a pnp hooked up to an led on the serout pin to see when it gets sent to the xbee. add the same thing to the serin. so when it sends to the second arduino, you’ll know it’s got it. You can trace the delay from there.
yeah, power and rssi from what it says. I don’t think that the rssi would work for what you need. I still suggest you use the pnp(ex. 2n3906) connected to a the serial pins I mentioned. This will give you a transmit indicator. Hello will be long enough to register a few blinks on the led. It’s simple enough to set up. 1k res to the pnp and a 470-1k res for the LED. It should be simple enough to connect.
I’m not familiar enough with the xbee or the tool to config it, but do you know if iti has a buffer read that waits for a certain amount of data? That could something to look at.
"Next we’ll set the Packetization Timeout. This is what determines how long to wait before sending the characters over. We’re doing some ‘bulk transfer’ when sending 10K programs over, so you’ll probably want this number high like 10"
This could potentually cause an issue and if as you say it looks like an xbee thing then something like this setting would do it.
Very interesting, so what you’re saying, is that keyboards have a buffer in them and thus remember what you’ve typed? How cool would it be to hack into this buffer
I had a similar problem and this is what they told me on the arduino forums: "One possible issue i see is you don’t have a delay in there to help ensure the buffer has all the data that was sent. "
