I would like to describe you what I did until now and what problem I have. My project is to connect the SM5100B GSM with a Raspberry Pi which runs Raspbian (similar version to debian) and to send message in my mobile. I did the first, the connection with the Raspberry pi. I have the cutecom as hyperterminal which I opened it, I connected the device /dev/ttyAMA0 and finally I clicked in the 'open device button'.
I have the following message:
+SIND: 4
I would like to send a message in my mobile. I wrote the following Inputs and I had the following results:
at
OK
at+cmgf=1
OK
at+cmgs="my number"
OK
>Hello
>Hello
But when I type or press ctrl-z it doesnt do anything. I have a spanish keyboard. What is the problem here? Is the problem the keyboard? Is the Cutecom's problem? Do I have to write any code?
There should be an option to enter Hex input. Select this and send Ox1A1D0D.
Related
I need to be able to resume debugging a webpage I wrote which is misbehaving in some of the browsers on my phone.
I have a Samsung A5 (2017) and Samsung phones apparently have some special challenges in getting connected to laptops for debugging, as discussed in this thread: https://stackoverflow.com/questions...evices-does-not-detect-device-when-plugged-in
Fortunately, I was using the technique in the second suggested technique (by studocwho) and it was working well until I did a slight variation on his technique: when I changed the USB Connection from MTP (Media Transport Protocol) to Audio Source and the dialog about the RSA key appeared, I checked the checkbox thinking that this would cause the RSA fingerprint to be sent from my phone to my laptop automatically each time so that I wouldn't get the RSA fingerprint dialog any more, save a couple of seconds, and still connect to the laptop.
As it turns out, that is NOT what happened at all. For whatever reason, it stopped giving me the dialog and also failed to send the RSA fingerprint to the laptop AT ALL. The laptop just waits patiently for me to accept the debugging session on the phone (see screen shot) but the phone does absolutely nothing at all. Apparently, checking that checkbox prevents the RSA fingerprint from being sent so no debugging session can start at all.
How do I get that RSA dialog to appear again so that I can start my debug session? I have to believe there is SOME way to reverse the effect of checking that checkbox but I'm darned if I know what it is. I've tried rebooting the phone but that didn't do it.
This is a huge project that my group is working on right now. We are very inexperienced with IoTs and Web stuffs.
First, we created an android app and with it, we're sending a message to the socket with port 8000 (192.168.X.X:8000) with a press of a button. The messages being sent are color names (Green, Red, Blue, etc) and our raspberry pi is running a script that could decode this color names, control the GPIO, and light up a whole LED Strip depending on the color sent. We are successful in this portion.
In addition, we managed to successfully install Google Assistant into Raspberry Pi. Now, we're planning to use IFTTT (If Google Assistant Then WebHooks) to make custom commands for our Google Assistant. We also managed to run the LEDStrip script and the Google Assistant script together on Raspberry Pi with no issues at all.
Now the problem that we're facing is sending a message to the socket.
Example: "Ok Google, Green Light Please" will send a message "Green" to the socket and the LEDStrip script will just receive it normally like how it receives messages from the android app.
Is it possible to do this? I've been researching a lot about POSTing Web Requests to http://192.168.X.X:8000 using IFTTT; and even tried the Google Advanced REST Client to do it manually but I'm just not successful at all. It says the http://192.168.X.X:8000 is not a valid URL or can't be accessed.
ISSUES ENCOUNTERED SO FAR:
Directly controlling GPIOs with Google Assistant on Raspberry pi by customizing hotword.py isn't successful for us at all because we can't import the neopixel library since the Google Assistant runs in virtual environment (env).
Thanks. Hope someone would be able to help us. We accept any recommendations on how to make our project successful.
I currently have a pi zero which acts as a bluetooth keyboard which - when attached to a computer - types text read from the SD card. I followed this tutorial https://www.rmedgar.com/blog/using-rpi-zero-as-keyboard-setup-and-device-definition. I use only the USB "Data" port, to power it up and to send data.
This setup works really fine on nearly all computers I tested it on, just on some Windows 7 systems it is not working at all. The system where it is not working on identify the pi zero as "Unknown device" and then never "re-identify" it as the keyboard which it is supposed to be.
All other systems first identify the device as "Unknown device" and after some seconds "re-identify" it as the actual keyboard. IMO the problem is the one mentioned by scruss in this post: https://raspberrypi.stackexchange.com/questions/60056/cant-see-raspberry-pi-zero-via-usb-otg-on-windows-10
I'm looking for a possibility to fix this problem. Is there some possibility to configure the pi zero in a way that during boot it does not identify as any USB device. Maybe that during boot the data USB port acts only as a power USB port.
Or can I turn the USB port off and on after a boot so that form the computers point of view it looks like the usb devices is removed and reattached??
I fixed that with the help of a colleague.
The solutions seems super simple - just remove the usb gadget and add it again.
The code necessary is equally simple:
#Remove usb gadget
echo "" > UDC
#Add it again
ls /sys/class/udc > UDC
I want to read text message using Matlab as hyperterminal using AT commands and bluetooth as connection medium since I am new in it could somebody suggest that how can I do it.
I am using nokia c2-03 for sending the message but if you suggest any other phone i can that too
I connected my phone through USB, saw the Port name then connected it through matlab using
s=serial('COM1');
and then opened the port
fopen(s)
now I don't know what to do I mean now how can send at command to control the device.
PS I am sure that my device supports serial communication.
RtMIDI under qt 4.7; using port 0 for midi in and midi out ports, using MIDI channel 1 to send and receive.
This works perfectly under OSX. Sends and receives, no issues whatsoever.
It compiles fine under Windows (running in a VMware Fusion Windows XP VM on my Mac), and the app can SEND messages to my control surface, but receives nothing... I never get a callback, so no midi input. Both the open of the MIDI input and output devices seem to go ok, no errors raised.
I can switch back to OSX, run the same app (compiled for OSX of course) and everything works again with no config changes on the control surface.
so : The surface is connecting and opening (it receives MIDI under windows); but I get nothing FROM it.
Am I missing something here?
TIA
Under Windows XP, the device opened for input needs to be device 1 (of 0...1)
Under Windows 7 starter, the device opened for output needs to be device 1 (of 0...1)
Under OSX, both input and output need to be zero.
That's all it was. A config dialog later, problem solved (well, at least handed over to the end user.)
RtMidi is a nice package, little short on documentation, but other than that, super.
Under windows device 0 is always the windows media player midi synth, midi devices start from device 1.
You can make the midi port selection by name if you read the port names then select the index value offset, that allows for the changing port positions when other devices are added/removed so your program selects the same default midi device.
Unlike OSX, Windows doesn't necessarily keep the input and output ports of the same device at the same ID/portNumber. Cool huh?
A config dialog is really helpful, but if you know one port then you can search through the port names of the opposite IO direction to get its counterpart.