Project to automate IP connections on the Raspberry Pi with the Sierra Wireless HL76

The scripts are installed in folder ~/pilot/

The scripts are executed from ~

Pilot board 000-586-02A Module WP7692 BHL769x.2.11.154401.201611011730.x7120m_1 HL7692 HL769x.2.11 x7120m FUSED 2016-11-01 17:32:04 r6274

RHL769x.2.23.172400.201706231140.x7120m_1 HL7692 HL769x.2.23 x7120m FUSED 2017-06-23 11:44:41 r9909

uname -a Linux raspberrypi 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux

Pi 2 model B v1.1

File commandPort.cfg contains the path to the tty to use for commands. Edit commandPort.cfg to change the port used.

. ./pilot/pilotRestart.sh

. ./pilot/pilotIp.sh

. ./pilot/pilotOn.sh

Note that ttyACM0 has been used in this example. This is because with if ttyACM2 is used the AT+CGDATA="M-RAW_IP",3 fails or crashes the HL device. All FW versions tested

There is no error handling

FW 2.23 - the restart script seems to break something AT+COPS doesn't respond after the pilotIp.sh. It looks like there are responses in the stream (OK or ) which are upsetting the pilotIp.sh sequence.

Note the . or source is needed because variables are globally shared by some of the scripts