Introduction: IOT BIT (Formally Known As PiAnywhere V1.31) 4G & LTE Hat for the Raspberry Pi

Picture of IOT BIT (Formally Known As PiAnywhere V1.31) 4G & LTE Hat for the Raspberry Pi

IOT BIT 4G & LTE Hat for the Raspberry Pi


4G (100 mbps down/ 50 mbps up) – Ultra fast internet connectivity for your raspberry pi, excellent for large downloads and video streaming.

TheIOT BIT 4G & LTE Hat for the Raspberry Pi Beta provides 4G mobile data for the Raspberry Pi mini computer. Our intelligent HAT module provides your Raspberry Pi with mobile data, GPS positioning information and battery support. This is the perfect module for hackers, scientists, and creators as it gives your Pi powerful connectivity wherever you are. Simple plug out module into your Raspberry Pi and start playing.

Find out more & order at https://altitude.tech/shop

The HAT can integrate easily with the software on your operating system giving you access to general internet data through the mobile network. Using our API this hat gives you the ability to send SMS (text) messages. We also give easy access to the GPS onboard which exposes location data.

HAT Features

  • Supports any nano sim. Slot your sim card in and get going
  • 4G Mobile Data for the Raspberry Pi
  • Easy set-up, with a single terminal command setup our software to streamline Pi Anywhere with your Raspberry Pi.
  • Wake up your Pi or trigger events with text messages.
  • Optional external antenna for better reception.
  • High-efficiency power regulation up to 3 amps.
  • Use for external projects with a solar panel and battery pack.
  • It can be used in conjunction with our Sensly gas monitoring HAT

Step 1: Whats in the Box?

Picture of Whats in the Box?

Step 1: Parts in the box

  • GPS Antenna
  • 1 4G antenna,
  • 1 3G antenna.
  • USB cable to connect to the Raspberry Pi.

Step 2: Put PiAnywhere Together With the Raspberry Pi

Picture of Put PiAnywhere Together With the Raspberry Pi
  • Raspberry Pi wall plug Into IOT BIT to power both IOT BIT and Raspberry Pi. ( You don't need to also plug in the Raspberry Pi).
  • Put the 2 antennas and the GPS antenna into IOT BIT.
  • Sim card into the IOT BIT (which you can buy from any major sim provider )
  • USB into the modem to connect to the Raspberry Pi.

Step 3: Setting Up the Raspberry Pi

Components needed for the Raspberry Pi to be operational:

  • Raspberry Pi 2 or 3.
  • Monitor.
  • Mouse and keyboard.
  • HDMI Cable.
  • Raspberry Pi Charger.
  • SD card (more than 8GB is required) with the latest version of Raspbian Jessie.

The guide to setup the Raspberry Pi software can be found at https://www.raspberrypi.org/learning/hardware-guide/

The latest version of the Raspbian Jessie can be found at https://www.raspberrypi.org/downloads/

Step 4: Connect the IOT BIT With Your Raspberry Pi

Picture of  Connect the IOT BIT With Your Raspberry Pi
  • Connect the 40-pin of the IOT BIT with the 40-pin of the Raspberry Pi.
  • Connect the USB from the modem of the IOT BIT to the USB Slot of the Raspberry Pi.
  • Connect the Raspberry Pi charger to the power pin of the IOT BIT, the IOT BIT will power your Rasberry Pi.

  • For the IOT BIT to power, the Raspberry Pi, press the button that states PWR (power) in the IOT BIT.

Step 5: IOT BIT Easy Setup

There are multiple ways to get this up and running. The first is to download the disk image and flash it using Win32 Disk Imager. You will need an SD card that is 8GB or bigger. The link for the download is below:

https://download.altitude.tech

To use turn on the IOT BIT by plugging in the power cable to the USB port labeled 5V Power. Next, we press the button marked btn to turn on the modem. We then connect the other USB port to the raspberry pi and finally turn on the raspberry pi by pressing the pwr button.

Also, you can use IOT BIT on a windows system. All you have to do is use these drivers and install them: https://drive.google.com/file/d/0B4StAjolU_LeVjRx...

Step 6: Downoad and Install the Software.

Picture of  Downoad and Install the Software.

Once the 2 boards are connected successfully and the power LED is on. The next task is to download the correct software for the IOT BIT to work with the Raspberry Pi. Using the latest version of Raspbian Jessie is recommended.

Open the terminal and type:

This should take around 30 minutes to complete as installing the kernel headers takes a long time. But once this is completed and your IOT BIT is connected via USB to the Raspberry Pi you should be able to run

  • lsusb | grep Qualcomm

And see a Qualcomm device connected. As a final check you can also run

  • ls /dev/ttyUSB*

And see 5 usb devices connected these are the virtual com ports for the modem.

.

Step 7: Set Up Wvdial and Connecting to the Internet

Picture of Set Up Wvdial and Connecting to the Internet

One of the important features of the IOT BIT 4G is its ability to connect to the internet using the mobile network, but for that, it needs to be configured to do so. This step will cover the link between the IOT BIT and the internet using the sim card information.

Now we need to configure the wvdial.conf file to enable IOT BIT to connect to the internet using your sim card. You will need the USSD code used to fetch the sim cards registered number. For example, on giffgaff this code is *99#. Or you can just use the sim cards phone number if you can't find the USSD code but just remember you will have to edit the file to change the number if you change the sim.

So we will need to open the file found in the iotbit_Install folder called wvdial.conf using a text editor of your choice.

  • sudo nano /home/pi/iotbit_Install/wvdial.conf

Then add to the file your USSD code or phone number in the 'Phone =' field. Then save and exit the file by pressing ctrl+x then y

We now need to move this file to the correct place to the system can find it.

  • sudo mv /etc/wvdial.conf /etc/wvdial.conf.bak
  • sudo mv /home/pi/iotbit_Install/wvdial.conf /etc/wvdial.conf

  • sudo wvdial

This last step takes around 30 seconds. If successful, you should be connected to the internet with your Raspberry Pi. Congratulations!


Step 8: Setting Up the Network Interface to Use the Modem Automatically

Picture of Setting Up the Network Interface to Use the Modem Automatically

To enable the Pi to connect IOT BIT to the internet using the mobile network automatically, we use the following steps.

First, open the file called interfaces using:

  • sudo nano /etc/network/interfaces

Then add the following lines at the bottom of the file:

  • auto ppp0
  • iface ppp0 inet wvdial

Then reboot the Pi, ensuring that the PiAnywhere is on and the Modem USB port is connected to the Pi.

  • sudo reboot

If successful when the Raspberry Pi boots you should be able to connect to the internet using your IOT BIT.

Step 9: Enable the GPS

The IOT BIT has the GPS feature, but it needs to be activated. First, minicom needs to be installed in order to test the GPS. This is done by using the following command:

$sudo apt-get install minicom

This is a terminal that operates in the command window, enter the minicom terminal using:

minicom –D /dev/ttyUSB2

In order to operate the minicom press CTRL+A and then Z, this will show all the different options that can be used. The echo local will need to be enabled. This is done by pressing CTRL+A then E. Once this is enabled you can enable the GPS this is done by typing inside the minicom terminal:

AT+CGPS=1

It will show a message of Ok!
The to get the information of the GPS location use the following command:

AT+CGPSINFO

Step 10: Congratulations!!!!

You have now gotten IOT BIT working, and you can do some amazing experiments with it. We are also running competitions for Instructables. If you buy an IOT BIT from us Pianywhere.com and you write an instructable about your project then we will give you up to 100% of your money back depending on the quality.

When you finish just tag us in it so we can take a look.

Comments

cbaquol (author)2017-08-24

I purchased this device under the impression that it would work on any US carrier (because it says that it does in the product description) and after countless hours of setup, and countless more communicating with the Verizon rep, and a week of waiting for approval, I was told this cannot be added to the Verizon Wireless DMD and is NOT approved to be used on their network. I have reached out to Altitude for support while I was troubleshooting and never heard a peep once. I would stay away until this is further developed and the product description is updated to reflect accurate information. Please refund my money ASAP.

J. Félix OntañonP (author)2017-06-23

My unit isn't working and PiAnywhere (Altitude.pw) isn't helping. They stop responding my emails 10 days ago.

This instructable steps didn't worked. The vendor states the firmware need to be upgraded but it isn't working too.

I feel my money has been wasted.

$ dmesg | tail

[ 30.287958] usbcore: registered new interface driver usbserial

[ 30.288013] usbcore: registered new interface driver usbserial_generic

[ 30.288060] usbserial: USB Serial support registered for generic

[ 30.302848] usbcore: registered new interface driver Gobi

[ 30.302910] usbserial: USB Serial support registered for GobiSerial

[ 30.302922] GobiSerial: 2011-07-29-1026

root@raspberrypi:/home/pi/PiAnywhere_Update# ls /dev/ttySO /dev/ttyAMA0

/dev/ttyAMA0 /dev/ttySO

root@raspberrypi:~/PiAnywhere_Update $ ./Update.sh

Enter the path to the update file e.g /pi/Pianywhere.binary or if it is in the same folder use Pianywhere.binary with the path

/home/pi/PiAnywhere_Update/PiAnywhere-10-05-17.binary

Can't init. Ensure that BOOT0 is enabled and reset device

Traceback (most recent call last):

File "stm32loader.py", line 436, in <module>

bootversion = cmd.cmdGet()

File "stm32loader.py", line 118, in cmdGet

if self.cmdGeneric(0x00):

File "stm32loader.py", line 115, in cmdGeneric

return self._wait_for_ask(hex(cmd))

File "stm32loader.py", line 91, in _wait_for_ask

raise CmdException("Unknown response. "+info+": "+hex(ask))

__main__.CmdException: Unknown response. 0x0: 0x1

I got erros from the usb port everytime, pianywhere was delivering a broken usb cable :(

But with a right one everythings is working (i hope) :)

ZachB70 (author)ThomasB4252017-08-22

My cable just had the same issue. It worked fine for a couple months and then failed. The symptoms were overheating and high current draw on the Pi as well as kernel faults and hard locks of the pi. If anyone experiences these symptoms do check the usb cable!

ZachB70 (author)2017-08-21

Has anyone else noticed that the download site is down? I have also not received any responses from their support email address.

ThomasB425 (author)2017-08-20

They send the wrong RF Adapter Cable SMA Female Connector to ipex for the GPS Adapter. Thats very annoying, because you did not get any answer if you contact the support. I've bought some cable by my one, but that must not be a option when ordering something.

John Doe Junior (author)2017-08-18

Raspberry Pi 3 does not detect 4G HAT when connected to USB. Several different OSs are tested, but with the same result. All USB ports in RP3 are tested OK with other hardware.

The same documentation is available on all pages, as in this guide. Neither RP3 nor 4G HAT has the "pwr" or "btn" buttons.

There are very very long response times from the support. I feel left to myself.

ZachB70 (author)2017-08-14

Does anyone know whether its possible to query the power state of the device? I would like to be able to determine whether the device is on battery power or ac.

ZachB70 (author)2017-06-16

Just got mine up and running. The clocking of the SIM card is a factor I think for some and is not obvious. When the sim is installed correctly the blue network light flashes as opposed to being constantly lit.

I found for AT&T (US) that adding a APN init line was required to make a connection.

I have also got the GPS running ( downing the Modem and issuing the init command worked for me) and plan to use gpsd and traccar to do location tracking.

Thus far I am only seeing 10Mbps/3Mpbs speeds, but it likely is my locale.

In general a very nice HAT. I would LOVE to hear from @Altitude Tech on how to bypass the buttons and do auto startup for both the network and the PI. This is going to present a real challenge for a remote box. I did read about the microcontroller option below, but that seems like a horribly complex solution to what can likely be solved in firmware.

slayracker (author)2017-04-10

* Gps module everytime needs to be activated.
for myself, i fixed the issue by adding the following line to crontab.
echo "AT+CGPS=1" > /dev/ttyUSB3

* Another poor thing, PiAnywhere always must be activated by manually pushing 'btn' button and then 'pwr' button. Its not useful for remote installation instances.
I hope there is a way to make it manually on power up. ?

* I bought pre-installed SD card. On advertisement, it was written that ''SAMPLES'' but there were no sample on it. No script. I couldn't find anything?

* GPS initiliazing very fast. As given instructions on the page for different model i see. For 4G/LTE, /dev/ttyUSB1 is GPS Echo for NMEA stream. You can see the stream basicly with " $ cat /dev/ttyUSB1 " command (without quotes) easily. ttyUSB2 is Modem, ttyUSB3 is GPS terminal for AT+ command/query.
Tested with gpsd and initialstate, works well.

* Preloaded SD card comes with hostapd and isc-dhcpd-server.
You can easily use it as WiFi - 3G/4G dongle by adding a conf file for hostapd and modify dhcpd.conf. Default on dhcpd.conf gateway written like 192.168.42.255, don't forget to change this otherwise you wont able to route default traffic trough raspi.

I am planning to write useful tutorials for the product.
But need more information about few things ;
- Auto boot/start option as i mentioned above ?
- Modem AT+ set, or at least more specific details about chipset to find out full list of commands. To enable disable 4G/3G function.
- More information about all virtual interfaces /dev/ttyUSB0,1 etc.

Also have few advice ;
- A housing for sale might be good.
- Given USB cable is simple ugly cable. A slim and nice one (as pictured above) would be more useful and looks nice.




MaximeA7 (author)slayracker2017-05-03

I would also love to find a way to automatically boot up the Pi and start the modem. Having to press on the buttons is a pain in the ass and prevent me from initializing it remotely. If you find a way to do that, that would be greatly appreciated.

ZachB70 (author)MaximeA72017-06-16

I second this. Is there a alternate firmware or some AT command way to bypass the button?

EE_Rob (author)MaximeA72017-05-07

So auto power up is actually pretty simple if you don't mind adding a little micro controller in your box. what you do is solder some wires to the resistors next the buttons, use a DMM to figure out which side is directly connected to the switch. Then you just write a quick sketch for the Arduino if that is what you want to use which does this every time it boots up:

pseudo code:

Void setup

digital pins for almost all arduinos default to low

Digital write the modem switch pin high for 250ms

Digital write the modem switch pin low

wait 10 seconds for the modem to boot up

Digital write the pi pwr button high for 250ms

Digital write the pi power switch pin low

Note that the modem needs at least 10 seconds to fully boot up and connect to the network, if you don't allow 10 seconds before turning on the Pi the auto connect code you added in the steps above will not work.

If you purchase a 3.3V micro controller than you can literally solder the wires from the micro digital pins to the button resistors on the piAnywhere. If you use a 5V micro then you will need to use a logic level converter like the one offered on spark fun P# BOB-12009.

Please note that soldering onto the piAnywhere could cause damage if you don't know what you are doing, so do the above at your own risk.

As you probably guessed from the sketch above the modem and the pi pwr buttons go high when you press them, and are low otherwise. Soldering onto the side of the resistor that is directly connected to the button is very important, otherwise if you solder onto the ground side of the resistors you will short the microcontroller digital pin to ground.

One final note, you must tie the ground on the PiAnywhere to the Arduino ground so that they are at the same reference level. This is done by simply running a wire from the piAnywhere header (they have the same pinout as the Pi it plugs into) to the Arduino GND pin. So basically you just need a GND wire, a wire for the modem power, and a wire for the Pi Power that go between the PiAnywhere and the Arduino.

I've been using this method to turn on the modem and Pi remotely for a few weeks now without any issues.

PhilippE9 (author)slayracker2017-05-03

Did AltitudeTech get back to you? I've successfully set up the modem, it works perfectly with a Taoglass antenna after I've disabled the SIM PIN and switched off wifi network access. It was even a breeze to set up a wifi hotspot using the LTE connection. However, as I'd like to install the RPi with this hat in remote location automatic power up is crucial. AltitudeTech unfortunately didn't get back to my support request yet.

MaximeA7 (author)2017-05-14

Regarding the ATZ command issue, ensure your SIM car is correctly inserted and facing the outside of the shield and be sure to remove its PIN code in order to work. For me *99# was then the trick rather than my phone number. Only thing I can't make work is the GPS. I have correctly enabled GPS with the AT+CGPS=1 which returns OK. However AT+CGPSINFO returns the following everytime:

+CGPSINFO: ,,,,,,,,

OK

The antenna is well plugged to the shield but I get no coordinates. Does somebody have some info about it? Do you guys get coordinates successfully?

QuentinD22 (author)MaximeA72017-06-11

Hi,

I have the same issue ...

Did you succeed in making it work ?

Quentin

Silviu12 (author)2017-06-01

I recently bought a PiAnywhere and connected it to a Raspberry Pi 3 Model B and it looks like the Raspberry start automatically without pressing any button from the PiAnywhere. The problem is that the OS of Raspberry does not finish to load and restarts unexpectedly. Has anyone ever encountered this problem or could you know what the problem is ?

QuentinD22 (author)2017-05-31

Is there is a way to avoir the buttons usage (start on power up ?)

Thank's in advance,

Quentin

EE_Rob (author)2017-05-26

If anyone is having problems getting wvdial to dial correctly (ie you fail to connect to the internet) you may need to add a line to the wvdial.conf file.

I am using straight talk here in the US and in order for it to work I had to add the following line after Init2

Init3
= AT+CGDCONT=1,"IP","tfdata","",0,0

The "tfdata" is the access point name for straight talk, as can be found here.

https://zoomtel.zendesk.com/hc/en-us/articles/212403243-Mobile-broadband-service-provider-settings

Hope that helps.

todroda (author)2017-05-22

No response to either of my prior emails after almost a month. I am having the same errors as the people two months ago on this site.

I understand AT commands and have been using them for 20+ years. When I follow the sim7100 application notes and AT command guide, I get the CME Error for SIM not present. Based on the social media posts I have the SIM inserted with the angled corner pointed towards the USB ports on the RPI3. (I have tried two different SIMs and have confirmed the SIMs as good in a cell phone).

The device is properly responding to other AT commands for querying LTE state but is not connecting to the carrier and any SIM related return the sam error.

Did you have a bad batch of boards with the SIM carrier?

GPS is working properly if that helps in troubleshooting.

Seeking any assistance.

EliyahHavemann (author)2017-03-06

Hi. I got the device to work (USB serial interfaces present), but the wvdial refuses:

pi@raspberrypi:~ $ wvdial
--> WvDial: Internet dialer version 1.61
--> Cannot set information for serial port.
--> Initializing modem.
--> Sending: ATZ
ERROR
--> Bad init string.

Where can I find more information about supported AT commands and is it possible to use it without the USB (with lower speed)?

todroda (author)EliyahHavemann2017-05-22

The AT Command set document is available on the PiAnywhere site. They use the sim7100 modem. So, you could also search for the document "simcom_sim7100_atc_en". I was able to use this to test the modem and confirm some functionality. I too am having the same errors as many people here.

For me, it appears the PiAnywhere LTE board isnt reading the SIM regardless of orientation or SIM card. Have tried emailing PiAnywhere support multiple times. About to post a copy of my latest email here.

EE_Rob (author)2017-05-17

Has anyone been able to send an SMS using the API yet? Not really sure where to find information on how to do it.

MaximeA7 (author)EE_Rob2017-05-19

@EE_Rob: Please check this documentation:

http://www.pianywhere.com/wp-content/uploads/2015/...

MaximeA7 (author)2017-05-14

Also wanted to know if anyone can confirm that a lipo battery is going to be charged when plugging the micro USB power cable?

MaximeA7 (author)2017-05-14

I just encountered another issue. For an unknown reason when downloading data, the board cease working and turns off. It's really weird because it is not even consuming the 2.1A available but only 0.6. Any suggestions?

84gls84 (author)2017-02-21

Hello,

I have bought the HW and connected to both raspberry pi 2 and 3 and I have downloaded the operating system image you have suggested in the guide. Unfortunately, it does not work because when I do "sudo wvdial" I have an error from the beginning with the simple command "ATZ"

AltitudeTech (author)84gls842017-02-24

Hi,

Could you please send us a screenshot so we can debug the problem.

ndelaet (author)AltitudeTech2017-03-14

Hi, any news on this? Also have the same problem.
Thanks!

MatsH8 (author)ndelaet2017-05-11

Hi! Did you get this to work?

mohoganogan made it! (author)AltitudeTech2017-03-11

I too see the error with the newest pre-built image (March 5, 2017)

unx made it! (author)mohoganogan2017-04-11

I have the same issue with PiAnywhereDriversInstalled-05-03-17.img pre-built image.

MatsH8 (author)unx2017-05-11

Hi! Did you get it to work?

MatsH8 (author)mohoganogan2017-05-11

Hi! Did you get it to work?

MatsH8 (author)AltitudeTech2017-05-10

Hi!
I have the same problem. Did you find a solution to this?

I have tried flipping the sim-card (which is activated, Ive actually tried 3 different sim cards all activated, I use them in other equipment) so that the slanted side is facing away from the RPI but no luck.
Ive tried a bunch of different chargers, no luck.
RPI is not connected through any wifi device, still no luck.
All antennas are connected.

MatsH8 (author)2017-05-05

Yay! They replied.. Finally! Saying that they will ship my things. When/if I receive my order, I will remove these comments.

le Wrench (author)MatsH82017-05-06

I had the same thoughts when I ordered from them. Got very little communication other than a couple of confirmations and a completed order notification. But I did finally get the hardware! Took about a month with Paypal check clearing and shipping from the UK to California.

They could use some improvement on their order confirmation and shipping confirmation. Otherwise I'm pretty excited!

EE_Rob (author)2017-04-16

Got the hardware setup today and was getting the same error as a couple other comments "Error bad init". After flipping the Sim around that fixed the error bad init problem. Now I'm just getting a NO CARRIER over and over. Not sure why. I'm just using my T-Mobile SIM, so maybe that is why. Anyone have a list of carriers/plans that are currently working with this modem in the US?

EE_Rob (author)EE_Rob2017-04-17

So I finally got my modem working. A few things.

First I just use my t-mobile unlimited sim card, I also bought a pure internet sim card (just data like what you would buy for a tablet) and that did not work. The normal cell phone sim worked, while the internet sim did not.

Second, the command sudo
nano /home/pi/Pianywhere_Install/wvdial.conf should be sudo nano /home/pi/PiAnywhere_Install/wvdial.conf (notice the capitalized A), but even with that the file was empty, I used the image provided by piAnywhere, so not sure why this was empty. So I just ran sudo nano /etc/wvdial.conf and that file had the dialer defaults as seen above. I changed the *99# to my phone number ##########, and then after saving ran sudo wvdial. This resulted in the No Carrier error again and again.

So I went back into the wvdial.conf file and change the phone = line back to *99# and after saving I again ran sudo wvdial and this time the modem connected almost immediately. I tried to use the internet browser on my Pi , but nothing seemed to load. So after exiting using cntrl+c I tried unplugging the wifi dongle I had plugged in and executing the sudo wvdial again, this resulted in the browser working.

So if you are having some trouble try some of those hints. Hope it helps.

Tachyon (author)2017-02-10

I wouldn't mind that this is really just a big product ad if there were at least some details on the product. Like what frequencies does it support? (ie will it work with my carrier in my country? )
And the menus on the linked website, at least on the mobile site, are nearly unviewable being they are white text on nearly white menu bars. So if the specs are hidden on the site somewhere, they're mighty hard to find.

GarethH34 (author)Tachyon2017-04-03

Has ANYONE got this to work recently? Working on a Raspberry Pi remote sensor project & this product looks perfect. But there are too many "don't work" comments above to be confident.

JeremyD112 (author)GarethH342017-04-10

Got mine working and connected last night! Used Google project Fi free data sim card. At first I had the sim in backwards, thanks to @ndelaet for posting troubleshooting steps below!

Baoguo_Wei (author)2017-04-04

If anyone want better LTE module, you should check out www.blink-r.io. Blink'r smart LTE module is a affordable feature packed 4G module with powerful ARM A53 CPUs, WiFi, BLE, GPS and much more.

AltitudeTech (author)Baoguo_Wei2017-04-04

Hi, Baoguo_Wei We would love to test our product and yours together. Would you like to send us a sample unit. Hope you do well in your Kickstarter.

Tecwyn Twmffat (author)2017-02-26

Looks like a nice piece of kit. I might want to use it in my next project.

How many digital I/O pins does it use ... or more precisely ... how many are still available?

Which QUALCOMM chip does it use?

Thanks!

Most pins are still available. The only one's that are reserved are the UART pins, GPIO 5 and GPIO 6. The I2C line is also used but you can connect multiple devices to this.

Delhaze (author)AltitudeTech2017-03-23

Can you tell me what signals the GPIO pins 5 and 6 are user for?

ndelaet (author)2017-03-14

Hi everybody,

Regarding issue with ATZ command: following reply from PiAnywhere (thanks guys): checklist to solve the issue:

Answer to all the followings topics must be "yes":

1) are you using the official raspberry
pi charger to power the pianywhere and the pi?

2) The simcard you are using has been
activated?

3) Your pi isn't connected to the
WiFi? (that was my issue nb1)

4) You sim is connected with the corner
that is slanted facing away from the pianywhere. (that was my issue nb 2)

5) Are both the main and auxiliary
antenna attached?

--> For me, id worked! PiAnywhere now fully functionnal :)

ndelaet (author)2017-03-14

Hi,

I've tried several methods to make it work, but no success so far (still have the issue with the ATZ command)

Scanning serial ports, the system actually cannot detect any modem:

pi@raspberrypi:~/PiAnywhere_Install $ sudo wvdialconf /etc/wvdial.conf
Editing `/etc/wvdial.conf'.
Scanning your serial ports for a modem.
ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyUSB0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyUSB0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 9600 baud
ttyUSB0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyUSB1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyUSB1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 9600 baud
ttyUSB1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyUSB2<*1>: ATQ0 V1 E1 -- ERROR
ttyUSB2<*1>: failed with 2400 baud, next try: 9600 baud
ttyUSB2<*1>: ATQ0 V1 E1 -- ERROR
ttyUSB2<*1>: failed with 9600 baud, next try: 9600 baud
ttyUSB2<*1>: ATQ0 V1 E1 -- ERROR
ttyUSB2<*1>: and failed too at 115200, giving up.
ttyUSB3<*1>: ATQ0 V1 E1 -- ERROR
ttyUSB3<*1>: failed with 2400 baud, next try: 9600 baud
ttyUSB3<*1>: ATQ0 V1 E1 -- ERROR
ttyUSB3<*1>: failed with 9600 baud, next try: 9600 baud
ttyUSB3<*1>: ATQ0 V1 E1 -- ERROR
ttyUSB3<*1>: and failed too at 115200, giving up.
ttyUSB4<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyUSB4<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 9600 baud
ttyUSB4<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyUSB20<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyUSB20<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyUSB20<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Sorry, no modem was detected! Is it in use by another program?
Did you configure it properly with setserial?
Please read the FAQ at http://alumnit.ca/wiki/?WvDial

--> what can we do?

Thks to come with a solution quickly

br

mohoganogan (author)2017-03-11

Have you been able or thought of using "gpsd" as the software to speak with the gps module? It provides lots of gps tools.

About This Instructable

16,288views

79favorites

License:

Bio: Altitude Tech LTD is founded by professionals and students in the area of robotics, electronics and product design, which makes the team the heart of ... More »
More by AltitudeTech:IOT BIT 4G, 3G & GSM V1.5 Hat for the Raspberry PiPlotly Graph for Sensly The Raspberry Pi HatIOT BIT (Formally Known As PiAnywhere V1.31) 4G & LTE Hat for the Raspberry Pi
Add instructable to: