Thales' cellular IoT products business is now part of Telit Cinterion, find out more.

You are here

Community > Forum > Cellular Hardware > Command AT^SGIO not working,

Command AT^SGIO not working, | Telit Cinterion IoT Developer Community

Like
0
3
kikeenerlin's picture
kikeenerlin

September 6, 2016 - 7:01pm, 2329 views

I'm trying to get the state of a GPIO but I'm getting an error. Am I using the command properly?

at^sgio=?

^SGIO: (0-7,10-23)

OK

AT^SGIO=0

ERROR

AT^SGIO=1

ERROR

AT^SGIO=2

ERROR

AT^SGIO=3

ERROR

AT^SGIO=4

ERROR

AT^SGIO=5

ERROR

AT^SGIO=6

ERROR

AT^SGIO=7

ERROR

AT^SGIO=10

ERROR

AT^SGIO=11

ERROR

AT^SGIO=12 

 .

 .

 .

Thanks in advance!

3
Comment
Log in or register to post comments
Jure's picture
Jure
Sep 7 2016 - 8:04am

Hi,

have you configured your GPIOs before issuing AT^SGIO? I had similar problems, so this thread will probably help you: https://iot-developer.thalesgroup.com/threads/bgs5t-input-gpio-allways-0...

Here is post from Jedrzej, which helped me the most:

It looks like you're trying to use USB interface for configuration, this will not work, usage of serial interface is mandatory for watchdog configuration. Has your terminal serial interface? If not, you have to use I2C:
1. start the module
2. Invoke the command AT^SSPI=
3. Wait for CONNECT
4. Set GPIO7 to input sending <aD41100>
5. Wait for acknowledge {a+}
6. Set GPIO8 to input sending <aD41200>
7. Wait for acknowledge {a+}
8. Exit data **** with # character
9. Restart the module with AT+CFUN=1,1
10. Invoke following commands:
AT^SPIO=1 <- enable GPIO driver
AT^SCPIN=1,6,0 <- open GPIO7 as input
AT^SCPIN=1,7,0 <- open GPIO8 as input
AT^SGIO=6 <- read GPIO7 value
AT^SGIO=7 <- read GPIO8 value

Regards
Jedrzej

You can read more about GPIO configuration in document: Cinterion® Java Terminals Hardware Interface Description,  chapter Configuring GPIO Directions.

Regards,

Jure

Bartłomiej Gemalto Moderator's picture
Bartłomiej Gema...
Sep 7 2016 - 3:05pm

Hello,

Please note that the configuration with i2c is only necessary for terminals. If you are using the concept board you need to follow the description in the hardware description for concept board. If you just have the module on DSB75 or other hardware you may only need to enable and configure the GPIO driver with AT commands.

Regards,

Bartłomiej

kikeenerlin's picture
kikeenerlin
Sep 7 2016 - 4:10pm

Thanks Jure and Bartłomiej for your answers.

I was trying it in a custom board and Jure's answer pointed me to the solution.

As Bartłomiej said, I only needed to enable the GPIO driver with AT^SPIO=1.