SKYLAB SKM53 compatability ?
- NikTheGreek
- Posts: 348
- Joined: Thu Dec 08, 2011 4:17 pm
- Location: Greece
- Contact:
SKYLAB SKM53 compatability ?
Hi.
I've read a lot of post concerning the SKYLAB SKM53 GPS that i'm holding in my hand but i haven't taken a clear answer .
This module it is or not compatible with MW ?
If yes could you please provide me with a link on how to do it ?
If no ... could you please help me to buy a new one that is compatible ?
Thank you in advance
I've read a lot of post concerning the SKYLAB SKM53 GPS that i'm holding in my hand but i haven't taken a clear answer .
This module it is or not compatible with MW ?
If yes could you please provide me with a link on how to do it ?
If no ... could you please help me to buy a new one that is compatible ?
Thank you in advance
- NikTheGreek
- Posts: 348
- Joined: Thu Dec 08, 2011 4:17 pm
- Location: Greece
- Contact:
Re: SKYLAB SKM53 compatability ?
Successfully flashed my Skylab SKM53 according the directions found here http://code.google.com/p/i2c-gps-nav/do ... p&can=2&q=
- NikTheGreek
- Posts: 348
- Joined: Thu Dec 08, 2011 4:17 pm
- Location: Greece
- Contact:
Re: SKYLAB SKM53 compatability ?
As i wrote above successfully flashed my SKYLAB SKM53 and is used in I2C mode (additional arduino 328p).
What i've done so far is...
1.Uploaded I2C_GPS_NAV V2.1 to my secondary arduino. I didnt made no changes to the file
2. In the Multiwii_2_1 in config.h
a. uncomment #define I2C_GPS
b. defined the correct magnetic declination---> #define MAG_DECLINATION 3.71f
When is used with MiniGPS seems that works fine.
Below are some pics of MiniGPS readings
STATUS
SETUP
TEST
I get no errors in GUI exept when i press reset in my secondary arduino which seems logical to me.
The problem is that i dont take any readings from my GPS in GUI.
No satelites no coordinations...nothing.
The led in my secondary arduino blinking ... i assume that waiting data from my GPS
and here are my questions.
1. do i have to make something more in the two files uploaded to my boards ?
2. In MiniGPS my settings are correct ?
3. In TEST tab do i have to write settings into flash ?
Any help will be much appreciated
What i've done so far is...
1.Uploaded I2C_GPS_NAV V2.1 to my secondary arduino. I didnt made no changes to the file
2. In the Multiwii_2_1 in config.h
a. uncomment #define I2C_GPS
b. defined the correct magnetic declination---> #define MAG_DECLINATION 3.71f
When is used with MiniGPS seems that works fine.
Below are some pics of MiniGPS readings
STATUS
SETUP
TEST
I get no errors in GUI exept when i press reset in my secondary arduino which seems logical to me.
The problem is that i dont take any readings from my GPS in GUI.
No satelites no coordinations...nothing.
The led in my secondary arduino blinking ... i assume that waiting data from my GPS
and here are my questions.
1. do i have to make something more in the two files uploaded to my boards ?
2. In MiniGPS my settings are correct ?
3. In TEST tab do i have to write settings into flash ?
Any help will be much appreciated
- NikTheGreek
- Posts: 348
- Joined: Thu Dec 08, 2011 4:17 pm
- Location: Greece
- Contact:
Re: SKYLAB SKM53 compatability ?
Acording to the EosBandi "manual" ..
The GPS implementation in MultiWii (both I2c and serial) expects that your GPS receiver is
1. set to 10Hz (or 5Hz) update rate
2. communicates at 115200 baud speed
3. and output GGA, GSA and RMC frames
This values must be set to 10 in each dropdown menu ?
and all other that is not needed to 0 ?
which means
GLL to 0 .......... RMC to 10 ? .......... VTG to 0
GSA to 10 ? .......... GSV to 0 ........... GGA to 10 ?
ZDA to 0.......... MCHN to 0
and then in TEST tab to "Write setting into flash" ?
The GPS implementation in MultiWii (both I2c and serial) expects that your GPS receiver is
1. set to 10Hz (or 5Hz) update rate
2. communicates at 115200 baud speed
3. and output GGA, GSA and RMC frames
This values must be set to 10 in each dropdown menu ?
and all other that is not needed to 0 ?
which means
GLL to 0 .......... RMC to 10 ? .......... VTG to 0
GSA to 10 ? .......... GSV to 0 ........... GGA to 10 ?
ZDA to 0.......... MCHN to 0
and then in TEST tab to "Write setting into flash" ?
- NikTheGreek
- Posts: 348
- Joined: Thu Dec 08, 2011 4:17 pm
- Location: Greece
- Contact:
Re: SKYLAB SKM53 compatability ?
No one ?
Re: SKYLAB SKM53 compatability ?
Hi Nik,
i am using this GPS in nmea mode and it works in gui and i get outside also a fix indicated by the flashing status led.
to your question:
my setting for the above 3 parameter is 1 (not 10), the other not used parameters are 0. finally i tap on the "Confirm" button.
under the tab Test i do nothing.
hopefully i am right with your environment and it was a help for you
mfg vistauser
i am using this GPS in nmea mode and it works in gui and i get outside also a fix indicated by the flashing status led.
to your question:
my setting for the above 3 parameter is 1 (not 10), the other not used parameters are 0. finally i tap on the "Confirm" button.
under the tab Test i do nothing.
hopefully i am right with your environment and it was a help for you
mfg vistauser
- NikTheGreek
- Posts: 348
- Joined: Thu Dec 08, 2011 4:17 pm
- Location: Greece
- Contact:
Re: SKYLAB SKM53 compatability ?
Thank you vistauser for your answer.
But my problem persists even with your suggested settings.
As i mention here viewtopic.php?f=8&t=649&start=1440#p25562 .
I dont know if it is a GUI problem or anything else .
But my problem persists even with your suggested settings.
As i mention here viewtopic.php?f=8&t=649&start=1440#p25562 .
I dont know if it is a GUI problem or anything else .
Re: SKYLAB SKM53 compatability ?
Try swapping tx and rx pins around between GPS and I2c board. Unless absolutely sure they are right.
- NikTheGreek
- Posts: 348
- Joined: Thu Dec 08, 2011 4:17 pm
- Location: Greece
- Contact:
Re: SKYLAB SKM53 compatability ?
shikra wrote:Try swapping tx and rx pins around between GPS and I2c board. Unless absolutely sure they are right.
Thank you for your answer.
swapped tx/rx cables but now i don't take any signal.
My problem is that the GPS FIX isn't stable.
Re: SKYLAB SKM53 compatability ?
Norry Nik
I misunderstood - thought it was working OK in miniGPS , but nothing in multiwii.
not relevant now but and I saw error on my post too - I meant between multiwii and I2C... doh...
I misunderstood - thought it was working OK in miniGPS , but nothing in multiwii.
not relevant now but and I saw error on my post too - I meant between multiwii and I2C... doh...
- NikTheGreek
- Posts: 348
- Joined: Thu Dec 08, 2011 4:17 pm
- Location: Greece
- Contact:
Re: SKYLAB SKM53 compatability ?
I'll continue here hoping that someone else will find the infos useful.
I flashed the same board with AXN1.51_2776_3329_384.1151100.5_v19.bin found here https://code.google.com/p/ardupilot-mega/downloads/detail?name=AXN1.51_2776_3329_384.1151100.5_v19.bin&can=2&q=
but now i'm facing some problems
Here are some pics to make it more clear for you.
Image 01: MiniGPS starting screen
Image 02 : When connected COM3 / 38400 at the top of MiniGPS screen the loaded FW displayed.
Image 03 : The default settings displayed when connected
Image 04 : FW version
Image 05 : When Hot Start/Warm Start/Cold Start clicked the FW at the top of the MiniGPS screen disapear !!!
and i get no readings at all (sats-lon-lat..etc)
Image 06 : When i'm trying to cennect in higher baudrates i get no info from the module
My questions
1) I assume that the default baudrate sould be 38400 . Right ?
2)Are all the above "symptoms" normal ?
3)In my config (2.2 Ver) im using
and i dont get any readings in GUI.
Can you please help me ?
Than you in advance
Nikos
I flashed the same board with AXN1.51_2776_3329_384.1151100.5_v19.bin found here https://code.google.com/p/ardupilot-mega/downloads/detail?name=AXN1.51_2776_3329_384.1151100.5_v19.bin&can=2&q=
but now i'm facing some problems
Here are some pics to make it more clear for you.
Image 01: MiniGPS starting screen
Image 02 : When connected COM3 / 38400 at the top of MiniGPS screen the loaded FW displayed.
Image 03 : The default settings displayed when connected
Image 04 : FW version
Image 05 : When Hot Start/Warm Start/Cold Start clicked the FW at the top of the MiniGPS screen disapear !!!
and i get no readings at all (sats-lon-lat..etc)
Image 06 : When i'm trying to cennect in higher baudrates i get no info from the module
My questions
1) I assume that the default baudrate sould be 38400 . Right ?
2)Are all the above "symptoms" normal ?
3)In my config (2.2 Ver) im using
Code: Select all
/**************************************************************************************/
/*********************** GPS **************************/
/**************************************************************************************/
/* GPS using a SERIAL port
if enabled, define here the Arduino Serial port number and the UART speed
note: only the RX PIN is used in case of NMEA mode, the GPS is not configured by multiwii
in NMEA mode the GPS must be configured to output GGA and RMC NMEA sentences (which is generally the default conf for most GPS devices)
at least 5Hz update rate. uncomment the first line to select the GPS serial port of the arduino */
#define GPS_SERIAL 2 // should be 2 for flyduino v2. It's the serial port number on arduino MEGA
#define GPS_BAUD 38400
// #define GPS_BAUD 115200
/* GPS protocol
NMEA - Standard NMEA protocol GGA, GSA and RMC sentences are needed
UBLOX - U-Blox binary protocol, use the ublox config file (u-blox-config.ublox.txt) from the source tree
MTK_BINARY16 and MTK_BINARY19 - MTK3329 chipset based GPS with DIYDrones binary firmware (v1.6 or v1.9)
With UBLOX and MTK_BINARY you don't have to use GPS_FILTERING in multiwii code !!! */
//#define NMEA
//#define UBLOX
//#define MTK_BINARY16
#define MTK_BINARY19
#define INIT_MTK_GPS // initialize MTK GPS for using selected speed, 5Hz update rate and GGA & RMC sentence or binary settings
//#define GPS_PROMINI_SERIAL 57600 // Will Autosense if GPS is connected when ardu boots
/* I2C GPS device made with an independant arduino + GPS device
including some navigation functions
contribution from EOSBandi http://code.google.com/p/i2c-gps-nav/
You have to use at least I2CGpsNav code r33 */
//#define I2C_GPS
/* I2C GPS device made with an indeedent ATTiny[24]313 + GPS device and
optional sonar device. https://github.com/wertarbyte/tiny-gps/ */
/* get GPS data from Tiny-GPS */
//#define TINY_GPS
/* get sonar data from Tiny-GPS */
//#define TINY_GPS_SONAR
/* GPS data readed from Misio-OSD - GPS module connected to OSD, and MultiWii read GPS data from OSD - tested and working OK ! */
//#define GPS_FROM_OSD
/* indicate a valid GPS fix with at least 5 satellites by flashing the LED - Modified by MIS - Using stable LED (YELLOW on CRIUS AIO) led work as sat number indicator
- No GPS FIX -> LED blink at speed of incoming GPS frames
- Fix and sat no. bellow 5 -> LED off
- Fix and sat no. >= 5 -> LED blinks, one blink for 5 sat, two blinks for 6 sat, three for 7 ... */
#define GPS_LED_INDICATOR
//#define USE_MSP_WP //Enables the MSP_WP command, which is used by WinGUI to display and log Home and Poshold positions
//#define DONT_RESET_HOME_AT_ARM // HOME position is reset at every arm, uncomment it to prohibit it (you can set home position with GyroCalibration)
/* GPS navigation can control the heading */
#define NAV_CONTROLS_HEADING true // copter faces toward the navigation point, maghold must be enabled for it
#define NAV_TAIL_FIRST false // true - copter comes in with tail first
#define NAV_SET_TAKEOFF_HEADING true // true - when copter arrives to home position it rotates it's head to takeoff direction
/* Get your magnetic decliniation from here : http://magnetic-declination.com/
Convert the degree+minutes into decimal degree by ==> degree+minutes*(1/60)
Note the sign on declination it could be negative or positive (WEST or EAST) */
//#define MAG_DECLINIATION 3.96f //For Budapest Hungary.
#define MAG_DECLINIATION 0.0f
#define GPS_LEAD_FILTER // Adds a forward predictive filterig to compensate gps lag. Code based on Jason Short's lead filter implementation
//#define GPS_FILTERING // add a 5 element moving average filter to GPS coordinates, helps eliminate gps noise but adds latency comment out to disable
#define GPS_WP_RADIUS 200 // if we are within this distance to a waypoint then we consider it reached (distance is in cm)
#define NAV_SLEW_RATE 30 // Adds a rate control to nav output, will smoothen out nav angle spikes
/**************************************************************************************/
and i dont get any readings in GUI.
Can you please help me ?
Than you in advance
Nikos
- NikTheGreek
- Posts: 348
- Joined: Thu Dec 08, 2011 4:17 pm
- Location: Greece
- Contact:
Re: SKYLAB SKM53 compatability ?
Tested with AXN1.30_2389_3329_384.1151100.1_v16.bin and working fine.
so i guess that this module won't work with V1.9
unless someone knows what more i have to do
so i guess that this module won't work with V1.9
unless someone knows what more i have to do
Re: SKYLAB SKM53 compatability ?
Hi
If you read the specifications from Skylab, then you will see that the default baud rate for the SKM53 is 9600.
So change the define from 115200 to 9600, and it runs like a charm
If you read the specifications from Skylab, then you will see that the default baud rate for the SKM53 is 9600.
So change the define from 115200 to 9600, and it runs like a charm
- NikTheGreek
- Posts: 348
- Joined: Thu Dec 08, 2011 4:17 pm
- Location: Greece
- Contact:
Re: SKYLAB SKM53 compatability ?
Thank you