As I am trying to understand how to set the parameters of the crossConnect() method, I noticed that included scripts like McastCounter do not call the function and work with Connect applications as well as Snappy scripts only.
If I upload the script McastCounter to the Snapstick and then run the sample application provided in the Connect Python Package Manual I can establish communication and everything works as expected. I though that in in order to do that, the call to
crossConnect(DS_UART1, DS_PACKET_SERIAL) needed to be present in the code uploaded to the Snapstick so it can comunicate and call RPCs in the Connect app.
Does this mean crossConnect(DS_UART1, DS_PACKET_SERIAL) is the default state? Is it possible to upload the McastCounter code to a remote node and have a "blank" Snapstick acting only as a bridge or relay, passing messages received over the air to the UART to be read by the Connect app?
What would be the default arguments if I were to invoke the crossConnect() method in this case in the stick?
If I upload the script McastCounter to the Snapstick and then run the sample application provided in the Connect Python Package Manual I can establish communication and everything works as expected. I though that in in order to do that, the call to
crossConnect(DS_UART1, DS_PACKET_SERIAL) needed to be present in the code uploaded to the Snapstick so it can comunicate and call RPCs in the Connect app.
Does this mean crossConnect(DS_UART1, DS_PACKET_SERIAL) is the default state? Is it possible to upload the McastCounter code to a remote node and have a "blank" Snapstick acting only as a bridge or relay, passing messages received over the air to the UART to be read by the Connect app?
What would be the default arguments if I were to invoke the crossConnect() method in this case in the stick?
Comment