I bought few pieces of GPS modules (jupiter-610f, http://www.rfsolutions.co.uk/acatalog/info_GPS_610F.html) from online shop.
I tried to connect the GPS module to PC thought a USB to TTL 3.3V converter (
http://item.taobao.com/item.htm?spm=2013.1.0.0.wymWWk&scm=1007.10009.518.0&id=18313941913&pvid=51e783b9-f467-4297-bbe2-2f4df1fc78df
)
Connect is as follow,
pin1 (GPS) Serial Data <-> (USB) RX
pin2 (GPS) Serial Data In 1 <-> (USB) TX
pin3 (GPS) VCC <-> (USB) 3.3VDC
pin4 (GPS) GND <-> (USB) GND
pin5 (GPS) PIO Output <-> (USB) NC
pin6 (GPS) 1PPS <-> (USB) NC
pin7 (GPS) RESET IN <-> (USB) NC
pin8 (GPS) Serial Data In 2 <-> (USB) NC
pin9 (GPS) VBAT <-> (USB) NC
pin10 (GPS) Antenna Power <-> (USB) 5VDC
I use LSViewer.exe to study the result.
However, it does not work. No response from the device.
Regards,
Angus
Check the devices datasheet. Check the placement of the Antenna. Make sure your power source can provide enough power. Then check for connections again. First use something like putty! or some serial monitor. Such things are easy not to go wrong.
if you are using windows, go to system properties and find out which COM port the GPS is connected to.Afterwards, open the COM port via putty setting the BAUD RATE set on the GPS module. if BAUDs match, you will see data on the putty serial termial.
Related
When connecting a Black Magic Probe to my mac i'm not able to receive any data when connecting UART RX to UART TX. I tried updating the firmware to the latest version without success.
I tried multiple Black Magic probes, both on Mac and Windows without success. The UART TX led on the board blinks when transmitting. I verified the connection was to the correct device endpoint (second interface of the device). When using an oscilloscoop I did not see and data transmitted on the TX output port.
By default the Black Magic Probe does not power the target. The Black Magic Probe uses levels shifters that require a reference voltage provided by the target to be present. Without this reference level the levels shifter buffer will not output any signals or receive any signals.
It is possible to use the 3.3V LDO on the Black Magic Probe as a reference by using this command in GDB: "monitor tpwr enable". Use the command: "monitor tpwr" to validate the target is powered by the Black Magic Probe. Please be careful the target supports 3.3V power and the total power consumption is limited. By supplying the power to the target the level shifters have a reference level and a UART loopback should work by connecting the RX and TX pin.
I'm using MPLAB X IDE to implement the transfer of UART data to I2C bus on dsPIC33EV128GM006 using interrupts. How should I start the data transfer if I'm not using the EEPROM or bridge converter IC?
For UART: Port PINS G6 and G7 are being used for communication.
FOR I2C: Port PINS SCL1 and SDA1 are being used for communication.
Baud rate: 9600
Crystal frequency = 32 MHz
The basic goal is to echo the signal from UART to I2C bus to know what data was sent or received on the UART bus.
Working part: UART is working fine with sending characters/strings. I2C is also working fine.
Please let me know the basic logic/approximate flow to implement the goal.
I'm learning embedded development, and I'm trying to communicate with the accelerometer (LIS3DSH) on the discovery board using the SPI protocol. I'm only using CMSIS headers so that I'm forced to interact directly with the registers.
According to the schematics, these are the pins being used by the board for communication with the accelerometer:
PA5: SPI1_SCK
PA7: SPI1_MOSI
PA6: SPI1_MISO
PE3: CS_I2C/SPI
From my theoretical understanding of the SPI protocol, whenever I want to receive or transmit data between the master and the slave, I first need to pull the CS pin (PE3) down and then start the communication. This seems to be confirmed by the LIS3DSH user manual as well.
But now I'm confused about what the meaning of SSM is. According to the board's user manual, this is what the software slave management bit does:
When the SSM bit is set, the NSS pin input is replaced with the value from the SSI bit.
The NSS pin is nothing but the slave select pin, right? Which means it is PE3 in this case.
The SSI bit is bit 8 on the SPI_CR1 register. Does this mean I should instead toggle this SSI bit instead of PE3? That doesn't make sense because how would board know that the PE3 is the relevant CS pin?
So how are the CS pin/line and the SSM bit related, if at all?
If they're not related, do I need to configure the PE3 pin with alternate function mode and and as a pull-up, and then pull it low every time I need to communicate using SPI with the accelerometer?
The NSS pin is an input used as a CS by some other device when the SPI peripheral is in slave mode, or can be used as an output to support multi-master configurations.
If you are operating the SPI in single-master mode, the pin is not used at all.
Moreover SPI1_NSS is an alternate function of PA4 or PA15 so not related to the CS GPIO on PE3 in your case. In master mode, any number of available GPIO pins may be used as CS lines for each peripheral on the same SPI bus, and is driven in software - it is not an "alternate function", and not part of, or controlled by, the SPI peripheral.
I am working on IoT Technology, in my current project I want to connect two sensors like BMP280 and TSL 2561 by using Raspberry PI 2.
But these two sensors are using the Same I2C Bus Pins (I2C1 SDA and I2C1 SDL on the Raspberry PI2.
Please tell me how can I use the above two pins for two sensors.
-Kishore
Have you read the I2C protocol? I2C is kinda of a serial communication bus, and you can attack multiple slave devices to an I2C bus master.
In your case, just share the SDA and SDL pins on the raspberry pi, those two sensor are distinguished by the unique device IDs when you discuss with them.
Not to mention that you have different sensors(BMP280 and TSI 2561), the manufacture ID could be just enough for differentiation.
We could even attach multiple I2c slave devices to the same I2c bus, the way we differentiate them is to use different address(normally 3 address pins). However, the total number of slaves would be limited, up to 8 though.
I am working with ADE7953 metering IC and I use the uart serial communication in raspberry pi to communicate with the IC and i have wiring pi installed in it.Can anyone help me regarding how to configure the IC.
You need to check the datasheets and look for the MODE register configuration. Also take care for the active energy line cycle accumulation mode registers to set before you take IRMS or VRMS any of the ENERGY register
The ADE7953 contains a detection system that automatically
detects which of the three communication interfaces is being
used.
The CS pin (Pin 28) is used to determine whether the
communication method is SPI. The pin must be low
during the SPI communication for this interface method.
The CS pin is active low and will automatically lock onto
SPI communication as a result.
The SCLK pin (Pin 25) is used to determine whether the
communication method is I2
C or UART. If this pin is held
high, the communication interface is set to I
2
C; if it is held
low, the communication interface is set to UART.
Now, for UART should be configured in hardware as pin28 should be high, pin25 should be low, pin 27 Rx and pin 26 Tx