[Bryan Tran]

Hi Jim,

Would you pls reboot your CDP and then ssh back into your CDP and type the following commands, post your output.

microcom /dev/ttyUSB3[Enter]

AT[Enter]

ATI[Enter]

AT+CSQ[Enter]

AT+CREG?[Enter]

AT+CPIN?[Enter]

I am not very sure why you would get an “Error” message response after typed in AT[enter].

The USB port will ignored the serial baud rate settings.

Regards,

BT

[Bryan Tran]

Hi,

1. What are the typical power consumptions of the device (while being idle, transmitting/receiving data via 2G, etc)?

Answer:

http://www.multitech.net/developer/products/multiconnect-ocg/hardware/multiconnect-ocg-d/hardware-specifications-r1-0/

2. Does it support any low-power modes?

Answer:

Yes. standby and mem mode.

Ex:

An example of how to put your MT100EOCG/MTCDP in a standby mode and wake it up using the serial port console (ttyS0).

*Plug in your 3pin debug cable and at the prompt type:

echo enabled > /sys/devices/platform/atmel_usart.0/tty/ttyS0/power/wakeup[Enter]

*Enable ttyS0 port to wake up.

echo standby > /sys/power/state[Enter]

*Put the processor in stand by mode.

Now, you can just hit a space bar or Enter key to wake it up.

Another example, you can wake up using the rtc timer by typing at the prompt:

echo “” > /sys/devices/platform/at91_rtt.0/rtc/rtc0/wakealarm[Enter]

*Clear the value.

echo “+30” > /sys/devices/platform/at91_rtt.0/rtc/rtc0/wakealarm[Enter]

echo mem > /sys/power/state[Enter]

*Put the processor in “mem” mode.

*Now, the device will wake up after the timer is expired (30secs).

3. According to the specification it has an ARM9 CPU – can anybody specify an exact make?

Answer:

AT91SAM9G20-CU

4. Is it shipped with a schematic?

Answer:

No.

Regards,

BT

[Bryan Tran]

Hi Jim,

1. The correct port for the H4 is: /dev/ttyUSB3 and /dev/ttyUSB4.

http://www.multitech.net/developer/products/multiconnect-ocg/hardware/multiconnect-ocg-d/accessing-hardware-interfaces/

2. As a test, would you please ssh into the CDP device and issue the following command:

microcom /dev/ttyUSB3 -s 115200[Enter]

AT[Enter]

Do you get any response ?

*Note: If you do not see what you are typing, try: ATE1[Enter]

If you do get response on the above command, then it likely there is something in your C program.

Regards,

BT

[Bryan Tran]

Hi Steven,

Can you try to do: modprobe asix[Enter]

See if it helps.

Regards,

BT

[Bryan Tran]

Hi Lucas,

When you go into the U-boot prompt using the 3pin serial debug cable. Do you see your Ethernet LED still lit up ? If so, then you can do as follow:

a. Go to your Development PC machine and Type:

– source env-oe.sh

– bitbake corecdp-base-image.

*Create a corecdp-base-image. Also, if you have the line uncommented: export TFTPBOOT_DIR=/tftpboot – in the file env-oe.sh, then you should have a soft link to the image in the tftpboot folder.

b. Boot your OCG to the U-boot prompt and type: printenv[Enter]

*This will list out the environment variables that currently set on the OCG.

c. Look for:

-ipaddr <–This should set to the ip address of the OCG

-Serverip <–This should set to the IP address of your PC development machine.

*You would want to have them in the same network.

d. Type: run krb[Enter]

*If you have a TFTP server set up on your development PC, then it would upload both: kernel and rootfs to your OCG.

Regards,

BT

[Bryan Tran]

Hi Rashan,

1. Create a new script named: nat_enable.sh on your OCG and put these commands in:

#BT – Allow to have multiple PCs access the internet and allow forwarding rule

#into our NAT table.

iptables –table nat –append POSTROUTING –out-interface ppp0 -j MASQUERADE

iptables –append FORWARD –in-interface eth0 -j ACCEPT

#BT – Enable packet forwarding

echo 1 > /proc/sys/net/ipv4/ip_forward

2. Save it and then type: chmod +x nat_enable.sh

3. Then type: ./nat_enable.sh

*Run the nat_enable.sh file.

Regards,

BT

[Bryan Tran]

Hi Rashan,

I assumed you want to have a PC sitting behind the OCG and want to access to the internet via the OCG device from the PC.

Basic set up is as follow:

Notes: You can connect the ethernet port on the OCG to your PC machine and then ssh into the OCG to do the steps below.

a. You need to know your model number along with the device port for your OCG, and then modify the file /etc/ppp/options to include this info.

http://www.multitech.net/developer/products/multiconnect-ocg/hardware/multiconnect-ocg-d/accessing-hardware-interfaces/

Note: Under Select tty device option, comment everything out other than your device port. And leave other stuff as is.

b. You then need to modify either gsm_chat or cdma_chat file at /etc/ppp/peers/ depend on what modem you have (gsm or cdma modem)

http://www.multitech.net/developer/products/multiconnect-ocg/applications/ppp-peers/

Notes:

i. For the gsm, you need to modify the apn only.

AT+CGDCONT=1,”IP”,”internet” <–Only need to change “internet” to your apn. Your service provider should give you this info.

ii. For the cdma, you do not need to do anything, as the default file is fine.

c. Finally, issuing the command: pppd call gsm

Or: pppd call cdma (Depend on what modem you have).

d. Once connected, you can issue a ping to the internet:

http://www.google.com

If you are getting a reply then it is good to go.

e. You then can setup a gateway IP address and DNS ip address on the PC. Bring up your web browser on the PC and you should be able to access the internet.

f. If you still can not get it to work, I suggest go to http://www.multitech.com -> support and open up a ticket for further help.

Regards,

BT

[Bryan Tran]

Hi Nilesh,

I am not sure if I understanding the question correctly. But:

1. The GPS receiver is accessible at 9600 baud on /dev/ttyS3.

http://www.multitech.net/developer/products/multiconnect-ocg/hardware/multiconnect-ocg-d/accessing-hardware-interfaces/

2. You can also send the GPS data from /dev/ttyS3 to a remote TCP server by:

a. Make a ppp connection.

b. Writing a TCP client application (running on the MTCDP-G2) that will connect to your remote TCP server via the ppp connection, then read the GPS data on the /dev/ttyS3 and send it to the remote TCP server.

Regards,

BT

[Bryan Tran]

Hi Matt,

Pls, try Debian 5/6 because this has been tested here.

Regards

BT

[Bryan Tran]

Hi ConRad,

Can you try to dial the number as follow:

*99#

If it is still not working, try this number:

*99*1#

And see if it helps

Regards,

BT

[Bryan Tran]

Hi Dawid,

What version of your Ubuntu ? If your Ubuntu version is not 10.04 LTS, pls try Ubuntu 10.04 LTS or 11.04 LTS ? These are tested here and known to work.

The Ubuntu 11.10 is not currently supported.

Regards,

BT

[Bryan Tran]

Hi Alok,

1. Accessing the GPS:

a. At the # prompt: type: microcom /dev/ttyS3[Enter]

*You should see the GPS data displaying.

2. Accessing the GSM or the radio:

a. At the # prompt: type: microcom /dev/ttyUSB3 or /dev/ttyUSB4[Enter]

*Then type: AT[Enter]

*You should see an OK in response.

To exit out the microcom: type: Ctrl + x.

3. Connect the USB cable one end to the USB device port on the CDP and other end into your Ubuntu machine. Run the minicom on your Ubuntu machine and make sure you set the minicom to the right USB port.

Also, set the serial baud rate to: 115200, 8N1 and no flow control.

Power off and back on at the CDP, you should see a lot of messages scrolling up on your Minicom console. Then it will give you a CDP login prompt. Log in and perform the above two steps to look at GPS data and type AT command or send SMS message manually to the radio or GSM modem.

Regards,

BT

[Bryan Tran]

Hi JM,

Yes, it is.

http://www.multitech.net/developer/products/multiconnect-ocg/development/development-examples/

Regards,

BT

[Bryan Tran]

JM,

Issue the following command on your development machine:

sudo rm /home/jm/.ssh/known_hosts

Then try to ssh back into your device again. It should work.

Regards,

BT

[Bryan Tran]

Hi JM,

BTW, When you are issuing the mv command, make sure you separate the source and the destination file with a space. For example,

mv source destination.

Note: There is a space between the source and destination.

Regards,

BT

[Bryan Tran]

Hi JM,

1. -rw-r–r– 1 jm jm 78118912 2011-12-02 16:29 CoreCDP-corecdp-full-image-eglibc-ipk-2.0.2-mtcdp.rootfs.jffs2

*Rename this file to: rootfs.jffs2 by typing:

mv CoreCDP-corecdp-full-image-eglibc-ipk-2.0.2-mtcdp.rootfs.jffs2 rootfs.jffs2.

2. -rw-r–r– 1 jm jm 1936596 2011-12-02 09:59 uImage-2.6.35-r4.corecdp5-mtcdp.bin

*Rename this file to: uImage.bin by typing:

mv Image-2.6.35-r4.corecdp5-mtcdp.bin uImage.bin

3. Then copy these two files to your SD card under the folder /flash-upgrade. Do the ls command on your SD card

to verify that:

a. uImage.bin is about roughly 1.85MB

b. rootfs.jffs2 is about roughly 74.5MB

Regards,

BT

[Bryan Tran]

Hi JM,

So you go into this folder on your development machine:

/corecdp-2.0.2/build/tmp/deploy/eglibc/images/mtcdp/corecdp-full-image-mtcdp.jffs2

and rename the file above to the rootfs.jffs2 ?

And this folder:

/corecdp-2.0.2/build/tmp/deploy/eglibc/images/mtcdp/uImage-mtcdp.bin

to uImage.bin and it is giving you a sym link ?

Can you go into the above folder do a command: ls -l and paste the output to this post so that I can see what they are.

Regards,

BT

[Bryan Tran]

Hi JM,

After you have downloaded the source code: you then cd into the folder: corecdp-2.0.2 and do as follow:

a. source env-oe.sh

b. bitbake corecdp-base-image or bitbake corecdp-full-image

The result file will be in:

/corecdp-2.0.2/build/tmp/deploy/eglibc/images/mtcdp/corecdp-full-image-mtcdp.jffs2

Note: Rename this file to: rootfs.jffs2

and:

/corecdp-2.0.2/build/tmp/deploy/eglibc/images/mtcdp/uImage-mtcdp.bin

Note: Rename this file to: uImage.bin

From the Development machine, you ssh into your CDP device with the SD card plugged in. Then do: cd /media/card.

a. Create a /flash-upgrade folder on your SD card.

b. Copy the rootfs.jffs2 and uImage.bin from your Development machine to /flash-upgrade folder on your SD card.

c. Do: cd /media/card/flash-upgrade and then ls to make sure the rootfs.jffs2, uImage.bin files are there.

d. Do: touch /var/volatile/do_flash_upgrade

e. Do: reboot.

When the CDP is rebooting back up, it will upgrade your CDP to the newest firmware CoreCDP-2.0.2.

Regards,

BT

[Bryan Tran]

Hi JM,

1. You should not have to worry about the TFTP server.

2. Here is how to flash upgrade your device with CoreCDP-2.0.2

Procedure for how to flash them to your CDP device:

a. Create a /flash-upgrade folder on your SD card.

b. Copy the rootfs.jffs2 and uImage.bin to /flash-upgrade folder.

c. Insert the SD card into the CDP device.

d. Do: cd /media/card/flash-upgrade and then ls to make sure the rootfs.jffs2, uImage.bin files are there.

e. Do: touch /var/volatile/do_flash_upgrade

f. Do: reboot.

Regards,

BT

[Bryan Tran]

Hi Mohammad,

1. I would try to send a couple sms from the cell phone to the iSMS device and look at both – sms live log and the inbox to verify that the sms messages that you have sent are coming in to the iSMS device.

2. Once you have confirming this, then you need to run a wire shark on the PC that had the script posted running. Then look at the wire shark capture and see if it gives you any clues…

Regards,

BT

[Bryan Tran]

Hi Noah,

Would you pls post your Email address here so that I can send you some of the documentations that regarding more additional steps that required to perform prior to use your SIM.

Regards,

BT

[Bryan Tran]

Noah,

I am currently working on your problem. I will let you know a solution as soon as I have found one.

Thanks,

BT

[Bryan Tran]

Hi Noah,

Can you take out the SIM and put it into your cell phone and see if you are able to send the sms message or not ?

Regards,

BT

[Bryan Tran]

Hi K,

Yes. It is in v1.47. http://www.multitech.com/en_US/SUPPORT/Families/MultiModemiSMS/firmware.aspx

Regards,

BT

[Bryan Tran]

Hi Noah,

Would you pls post the entire AT commands that you have sent to the modem that gives you the +CMS error: 500 ?

Regards,

BT

[Bryan Tran]

Hi Mohammad,

1. Can you check your SIM and see if it is inserted in ?

2. You can also telnet into the iSMS device on port 5000 and type in:

AT+CPIN? <–Check to see if the SIM is inserted correctly. If it is then you should get a +CPIN:Ready.

AT+CSQ <–Check the signal quality

AT+CREG? <–Check to see if it is registering to home or roam.

AT+CMGF=1 <–Turn on text mode.

AT+CMGS=”your_cell_number”[enter]

*After you hit Enter Key, you will get: ‘>’ prompt, then type in your sms message then to send it, you must do ctr+z.

For example,

>This is your message[ctr+z]

3. If it is still not working for you, I suggest take out the SIM and put it in your cell phone and try it out and verify it if you can send the sms message with that SIM. Or you can try to plug in a different SIM to the iSMS device and see if it helps.

Regards,

BT

[Bryan Tran]

Hi Mohammad,

Can you web into the device and go to Statistic&Logs -> live log and see what error you have got ? May be it will give you a clues.

Regards,

BT

[Bryan Tran]

Hi Mohammad,

1. It looks like the &password=admin param should be &passwd=admin instead.

2. Error 602 is a parse Error. http://www.multitech.com/en_US/DOCUMENTS/Families/MultiModemiSMS/manuals.aspx

3. Here is the link where you can take a look at our sample codes to get the message ID.

https://webfiles.multitech.com/engineering/sample-code/sms-finder/

Regards,

BT

[Bryan Tran]

Hi Noah,

Can you type: microcom /dev/ttyUSB3 to get into the microcom console. Type the following commands:

AT+CPIN? <–You should get response back with +CPIN: READY. Otherwise, check to see if SIM insert or not.

AT+CSQ[enter] <–Check signal.

AT+CREG?[enter] <–Check to see if register home or roam.

AT+CMGF=1[enter] <–Set to text mode.

AT+CMGS=”Your_SIM_number_here”[enter]

*After you hit Enter key, you will get a greater than sign, just type in your sms message and then hit ctr+z to send the sms message to your SIM. For example:

>This is your sms message [ctr+z]

Do: AT+CMGL=”ALL”[enter] <–List all of the messages received.

Regards,

BT

[Bryan Tran]

Hi Noah,

1. You can try to issue the command: microcom /dev/ttyUSB3 and then type:

AT[enter] and see if you are getting an OK back.

ATE1[enter] <–To turn echo on.

AT+CSQ[enter] <–Check signal.

AT+CREG?[enter] <–Check to see if register home or roam.

Ctrl + x [enter] <–Exit out the microcom.

2. Once you get the above commands to work, then you know that which /dev/ttyUSBx is talking to the wireless modem. You can then modify the .smsconfig and try it again.

3. If it is still not working for you, you can try:

sms –device /dev/ttyUSB3 send your_phone_number_here

or sms[enter] to list out a usage.

Regards,

BT

[Author]

Posts