Hello World Response from SerialCloud

Hardware (and firmware) Dash
1

I uploaded the Hello World Arduino sketch and connected TTL Uart Cable to DashPro.

I am able to send and receive with Serial2…via keyboard and terminal program.

This is the response from SerialCloud.read
I tried two different DashPro’s.See IMEI’s Connected to 5v 2 amp Power Supply via GND and VIN
Ideas?

DEBUG: Boostrapping (1/14): Init modem (can sometimes take several minutes).
DEBUG: Boostrapping (2/14): Init event handling.
DEBUG: Boostrapping (3/14): Config modem.
DEBUG: Boostrapping (4/14): Init SIM card.
DEBUG: IMSI loaded:
DEBUG: 234507093104234
DEBUG: ICCID loaded:
DEBUG: 8944501003151042347
DEBUG: IMEI loaded:
DEBUG: 358683062633830
DEBUG: Boostrapping (5/14): Locate carrier signal.
DEBUG: Boostrapping (6/14): Establish operator link.
DEBUG: Boostrapping (7/14): Config network.
DEBUG: Boostrapping (8/14): Config APN.
DEBUG: Boostrapping (9/14): Config IP address.
DEBUG: Boostrapping (10/14): Link up (1 of 2).
DEBUG: Boostrapping (11/14): Link up (2 of 2).
DEBUG: +CME ERROR: Unspecified GPRS error
+EVENT:LOG,44,4,CRIT,34,+CME ERROR: Unspecified GPRS error

DEBUG: Boostrapping (1/14): Init modem (can sometimes take several minutes).
DEBUG: Boostrapping (2/14): Init event handling.
DEBUG: Boostrapping (3/14): Config modem.
DEBUG: Boostrapping (4/14): Init SIM card.
DEBUG: IMSI loaded:
DEBUG: 234507093104234
DEBUG: ICCID loaded:
DEBUG: 8944501003151042347
DEBUG: IMEI loaded:
DEBUG: 358683062634994
DEBUG: Boostrapping (5/14): Locate carrier signal.
DEBUG: Boostrapping (6/14): Establish operator link.
DEBUG: Boostrapping (7/14): Config network.
DEBUG: Boostrapping (8/14): Config APN.
DEBUG: Boostrapping (9/14): Config IP address.
DEBUG: Boostrapping (10/14): Link up (1 of 2).
DEBUG: Boostrapping (11/14): Link up (2 of 2).
DEBUG: +CME ERROR: Unspecified GPRS error
+EVENT:LOG,44,4,CRIT,34,+CME ERROR: Unspecified GPRS error
+EVENT:LOG,44,4,CRIT,34,+CME ERROR: Unspecified GPRS error
DEBUG: +CME ERROR: PDP activation rejected
+EVENT:LOG,45,4,CRIT,35,+CME ERROR: PDP activation rejected
DEBUG: +CME ERROR: PDP activation rejected
+EVENT:LOG,45,4,CRIT,35,+CME ERROR: PDP activation rejected
DEBUG: +CME ERROR: PDP activation rejected
+EVENT:LOG,45,4,CRIT,35,+CME ERROR: PDP activation rejected
DEBUG: +CME ERROR: PDP activation rejected
+EVENT:LOG,45,4,CRIT,35,+CME ERROR: PDP activation rejected

2

Is your antenna connected? Maybe it’s getting a weak signal

3

As Reuben mentioned, that’s most commonly an antenna/signal issue.

Basically, your Dash has detected a carrier signal (although it could be a very weak one), and then was unable to establish a data link with the carrier.

Could you try again and indicate the time of your most-recent attempt? We can take a look on our end and see if the cellular tower heard your Dash’s attempt to establish a data session (pretty cool, no?)

Thanks,
Pat

4

Hello Konekt,

Yes, very cool.

Most recent attempt 9:09 pm EST.

Antenna has been on during all attempts. Same SerialCloud .Read Output.

Regards

5

Please find information from another Lisa-U200 board.
Ublox c027 using Konekt Sim.
Output gives additional information. Signal Strength…etc
using SMA type connected antenna.

Modem::wakeup
Modem::init
Modem::devStatus
Device: LISA-U200
Power Save: Disabled
SIM: Ready
CCID: 8944501003151042339
IMEI: 352648063790596
IMSI: 234507093104233
Manufacturer: u-blox
Model: LISA-U200
Version: 22.90
Modem::register
Modem::netStatus
CSD Registration: Roaming
PSD Registration: Roaming
Access Technology: 3G
Signal Strength: -95 dBm
Bit Error Rate: 43
Operator: AT&T
Location Area Code: 11C7
Cell ID: 0D9AE2E4
STATUS: Initializing AMMP configuration
STATUS: Initializing device ID
Modem::join
DEBUG: Attempting to create headers
DEBUG: Transmission sent, Waiting for response
DEBUG: response received
DEBUG: Starting parse of
DEBUG: HTTP/1.1 200
DEBUG: body present

6

So that looks like it worked. Were you able to send a message?

7

Pmjackson,

When you say “another Lisa-U200 board”, are you referring to another Dash Pro, or are you talking about a U-blox brand dev kit?

8

Hello DD,

Ublox Dev Kit C027 …uC connected to LISA-U200 modem.

Using some Mbed based firmware.

I noticed that about 48k of Data Usage happened while doing some Http page fetching and other test using Konekt SIM: 8944501003151042339 installed on the C027 board.

So I was able to connect and transfer data with the C027 whereas the DashPro would not get past Boostrapping (11/14): Link up (2 of 2).

I included signal and Network information from the C027 noted above.

I hope this is helpful.

9

Pmjackson,

This is very helpful.

Do you have an SMA to U.FL adapter to move the antenna from the C027 to the Dash Pro? I want to rule out damage to the antenna on the Dash Pro. Can you verify which antenna you’re using on the Dash Pro? The first batch of antennas should say Taoglas FXP14 Hexa Band Cellular Antenna 850/900/1700/1900/2100 MHz. We’re switching to Sinbon antennas, but they should be functionally equivalent based on maths and lab equipment.

We test all of our boards before shipping them out, but I’m very curious to see what is causing this.

10

Also, have you tested all 4 of the boards we sent you? We’re just wondering if it’s an issue with one or two of them.

11

I only have U.FL to RP-SMA…Looking for adapter…

Taoglas FXP14 came with DashPro

Testing other boards…

12

All boards using Taoglas FXP14 tested the same.

13

Pmjackson,

Can you verify whether you are using a 2A / fast-charge USB power supply on the Dash? Are you connecting a battery to the Dash? We’ve been shipping the Betas with jumpers configured for direct USB 5V power with no battery connection.

The units work in our lab connected to a PC (5V@500 mA), but you might be on a network that needs a higher current power supply. Some of the network modes need peaks of 2A. (Most of them use far less current). It could be that the supply is peaking at 500 mA and the U-Blox doesn’t have enough current to boost the signal.

14

I have not connected a battery to the Dash Pro yet

I am using a 5v 2 amp switching power supply connected to 5VIN and GND pins.

The USB cable for uploading is also connected.

15

Okay. Don’t connect the battery. It would quickly charge and then overheat in the current jumper setting. We’re still puzzling out what could be causing this. Thank you for your patience.

16

Hey, Thanks for getting a device like this to the market.

Note: ATT service here on 3G phones is about 3-4 out of 5 signal.
T-mobile Sim not as strong. but works on Ublox C027 board.

I tried USB 500ma cable (upload cable) and Battery connected. Still doesn’t get past 11/14.

I am going to order a U.FL to SMA cable to use with the Ublox Antenna. Should have it Monday.

If the ATT signal was lower, I would go mobile, closer to a tower. But 3-4 out of 5 should be more than enough.

Regards,

Pat Jackson

17

Please unplug the battery. It’s connected to 5V in the beta configuration. The battery will just charge and charge. You can enable the battery by soldering in R26, removing the topside jumper, and switching the jumpers on the bottom side. The newest boards (not yet out) don’t require soldering. I’ll whip up some documentation, but you risk setting the battery on fire by connecting it right now without changing the configuration.

18

Sorry, I misunderstood…I thought you meant if the 2 amp 5VIN was connected…

I did run the DashPro with just the battery…no USB or 5VIN and still had same results.

Also, I sent an email with some additional information.

Thanks

19

FYI Battery Jumper Config:

Konekt Dash Jumpers.jpg1473×1503 265 KB