I am stuck in my GPS ( ublox Neo-M8N) and when I go outside it didn’t turn blinking green, its big blue led is blinking always and the switch is blingking red.
Then I didn’t get the right outcomes from nsh (mavlink console) terminal, if you have a knowledge about it ,could you illuminate me please?Because I finished all the issues about GPS in discuss forum but I didn’t find the solution, this is the output that I got in terminal:
nsh> gps status
INFO [gps] Main GPS
INFO [gps] protocol: UBX
INFO [gps] status: OK, port: /dev/ttyS0, baudrate: 115200
INFO [gps] sat info: disabled
INFO [gps] rate reading: 697 B/s
INFO [gps] rate position: 5.00 Hz
INFO [gps] rate velocity: 5.00 Hz
INFO [gps] rate publication: 5.00 Hz
INFO [gps] rate RTCM injection: 0.00 Hz
timestamp: 72835397 (0.108428 seconds ago)
device_id: 11010053 (Type: 0xA8, SERIAL:0 (0x00))
Can you post a picture so we can see how it is mounted?
Also do you have a camera on the drone?
I don’t have a camera currently. I used TELEM1 to connect nsh and ACM0 for micrortps_agent side.
Also parameters are like:
For the other sensor data , I can see them in the nsh terminal but not in the agent side:
nsh> listener sensor_combined
timestamp: 97735200 (0.001099 seconds ago)
gyro_rad: [0.0006, 0.0063, -0.0013]
accelerometer_m_s2: [0.0430, -9.8173, -0.0997]
ros2 run px4_ros_com sensor_combined_listener
Starting sensor_combined listener node...
RECEIVED SENSOR COMBINED DATA
when I try to see them in nsh terminal sensor by sensor, I see them their protocols I2C and SPI, like:
nsh> listener sensor_mag
TOPIC: sensor_mag 2 instances
timestamp: 588927009 (0.028543 seconds ago)
timestamp_sample: 588926069 (940 us before timestamp)
device_id: 396825 (Type: 0x06, I2C:3 (0x0E))
timestamp: 589140681 (0.004018 seconds ago)
timestamp_sample: 589139735 (946 us before timestamp)
device_id: 396809 (Type: 0x06, I2C:1 (0x0E))
nsh> listener sensor_baro
timestamp: 618058600 (0.018138 seconds ago)
timestamp_sample: 618058591 (9 us before timestamp)
device_id: 3997730 (Type: 0x3D, SPI:4 (0x00))
so if the protocol issue comes because of the UART to TTL converter , how can I solve it?
Thanks for posting the pictures. However we need to see it mounted on the drone.
I suggest that you connect all the standard factory cables for the GPS, switch, buzzer, etc., (that came in the original shipping box) to the Pixhawk, without any of the additional wires going through the breadboard, mount it on the quadcopter without propellors, take it outdoors, and try to start the aircraft. That will tell you if the system is working or not. Usually the problems with a Pixhawk have to do with the compass and calibration. If the system works, then starting adding in the extra wires you have attached to the breadboard one by one, checking to see if the aircraft still starts after each change. You will eventually identify the source of the problem. With a Pixhawk, it will either work beautifully or it won’t work at all. They work best when you only use the parts that came in the original box. Changing parts like the GPS or cables just leads to frustration because they often do not match between manufacturers. If it gets frustrating, sleep on it and the answer may come to you.
I will mount it but simply I made my pc as a companion computer before the calibration, RC settings etc. but Does it make any change in my error mounting frame? I didn’t get the logic behind it.
I will try it and make you know , thanks a lot for explanation basically.
I connect GPS module without any other connections (breadboard) and go outside but I got the same error. Is there anything you know about that error. Because first connection that I made GPS module works fine, now it is not. I didn’t change any parameter I just changed airframe, may error depend on it?
Your initial post of the output of
gps status shows that the Pixhawk is talking to the GPS. The last line of that output is important -
That means that the GNSS device is working but can’t see any GNSS satellites in the sky. This can be caused by a few things, including:
- Being indoors (especially with thick walls/ceilings)
- Being in an urban canyon.
- GPS initialization time
- Bad antenna
Those hockey puck modules usually have the antenna built in, so the last one is unlikely. When the devices are first booted in a new region they take a while to “learn” the constellations and figure out where they are. Often you just need to give it time.
The best bet is to get on a roof or open field (with a clear view of the southern sky if in the northern hemisphere) and let the GNSS device get a fix. If you put it near a window (southern facing towards the equator if you can) and run the nsh
gps status command you should start seeing the satellite count go up, although not as high as when you are outdoors.
Just for dibs, take a magnifier and inspect the pins where the GPS plugs into the FC and make sure that none of them are bent. Ask me how I know… Also inspect the GPS connector.
You can always use UAV Forecast to get an idea how many satellites are available in your area.
Thank you so much! It was just waiting for two or three min. in outside solve the problem but I got another issue right now…
thanks I will check it but I am facing another problem.