Thanks so much for the speedy and informative reply. Yes, I realized that running any Hologram command would make the /dev/ttyUSBs appear. I just wanted to provide a concrete example. But now you have shown me how to load the drivers–that’s a great help.
I also understand that “Hologram network connect” creates a ppp session. I’ve only been working with the Nova for about a week and I have been using that command to set up ppp sessions.
I have, however, run into two problems using the CLI. First, I created shell script for setting up ppp:
hologram network disconnect -v
hologram modem reset 0v
hologram network connect -v
I found that without the ‘sleep’ delays the script would not work reliably (though I’m not sure what sleep values are optimal). It makes sense that delays are need to allow the CLI commands to complete.
That script usually works. The (verbose) output from the ‘network connect’ command end with:
PPP session started
followed by a prompt. However, sometimes the the script seems to hang after displaying “PPP session started” and no prompt is produced. In this case it appears no ppp session is established.
The second issue is that when I start a ppp session using the above script, I am not able to open /dev/ttyUSB2 to interact with the Nova. I want to be able to open /dev/ttyUSB2 so that I can query the Nova for various status conditions using AT commands. My main concern here is that if I cannot interact with the Nova it is difficult to determine accurately if the ppp connection has dropped.
Using the Python SDK and Hologram CLI would be fine if I could connect reliably connect and accurately determine when the ppp connection is lost (so I can initiate a reconnect).
Any advice you can offer will be much appreciated.