Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COHardware flow control is being used. The local XBee may have sent the stop character, but it's going through rxtx and then xbee-api before it reaches my code. xbee-api appears to have management for this, but the point of my using the library is to avoid knowing about things like which control bytes are sent at what time - what I'm saying is I know very little at this level. I'm in the process of setting up a test to gather exactly what data is being sent to and returned from the local XBee on each request. I'll update here once I have usable data. Thanks for the suggestion.
      singulars
    2. COYou don't need to worry about start/stop characters in the serial stream -- that would be software flow control. You're right that the libraries should be taking care of all of that. It will be helpful to know if there are additional packets coming from the XBee that aren't making it through the library to your code for some reason.
      singulars
    3. COI was able to capture the data being sent to the XBee and the XBee's response. Although the information I've read on xbee-api and S1 XBees indicates hardware flow control is used by default, the data reveals a constant start byte is being used. By removing xbee-api and using rxtx directly I found that when a request is sent to the XBee, the serial input appears to interrupt the serial output before it's even done sending - and the response is just a -1 indicating end-of-stream. I'll be continuing to investigate over the weekend.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload