paparazzi-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Paparazzi-devel] STM32 and GPS receive


From: Eduardo lavratti
Subject: Re: [Paparazzi-devel] STM32 and GPS receive
Date: Sun, 18 Nov 2012 02:05:40 +0000

BTW ... in my test´s with lisa/m i never get an stable position hold.
May be this is the problem.
My lea-5 are side-by-side with lisa.

i will test again.

> Date: Sun, 18 Nov 2012 00:36:47 +0100
> From: address@hidden
> To: address@hidden
> Subject: Re: [Paparazzi-devel] STM32 and GPS receive
>
> Hi,
> i always use ferrite rings for GPS connections wires.
> Also for the receivers and modems.
> http://paparazzi.enac.fr/wiki/File:RazzorIMU.jpg
> If you have problems please try them first.
> The LPC2148 use low clocks on pads (range 4 MHz). In the ST
> processors the io clock is 36 or 72 MHz ?
> The autopilots with 4 layers (Tiny HBmini) generate lower dissertation
> than such with 2 layer.
> But also with the Twog and Umarin i had never problems with the GPS 5cm
> away from the autopilots..
> By applying aluminium foil below the GPS module i got a 3dBbetter
> signal in my fun jet.
> In the fun jet the GPS module fetch noise from the motor controller
> The most problems i had with 35MHz and 40 MHz receivers and the old AVR
> autopilots.
> Regards
>
> Heinirch
>
> Sergey Krukowski schrieb:
>
> > I tried any possible power supply configurations to be sure that the
> > internal switching regulator does not affect this. And it is
> > absolutely unambiguouslyfor me - the problem is in STM32F1.
> > I've also tried LisaM with only a led test programm on it - same
> > result. Ublox5 GPS receiver has noticeable worse receive nearby the
> > board.
> >
> > I found yet one forum topic about it
> >
> > https://my.st.com/public/STe2ecommunities/mcu/Lists/cortex_mx_stm32/Flat.aspx?RootFolder=%2Fpublic%2FSTe2ecommunities%2Fmcu%2FLists%2Fcortex_mx_stm32%2FHSI%20and%20GPS%20interfence&FolderCTID=0x01200200770978C69A1141439FE559EB459D7580009C4E14902C3CDE46A77F0FFD06506F5B&currentviews=3
> >
> >
> > The solution could probably be to switch off the HSI after HSE and
> > PLL init. As I see, the HSI is switched on in
> > rcc_clock_setup_in_hse_12mhz_out_72mhz function and stays on from
> > that point.
> > By adding rcc_osc_off(HSI) at the end of this function could probably
> > help.
> > Regards,
> > Sergey
> >
> > _______________________________________________
> > Paparazzi-devel mailing list
> > address@hidden
> > https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
> >
>
>
> _______________________________________________
> Paparazzi-devel mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/paparazzi-devel

reply via email to

[Prev in Thread] Current Thread [Next in Thread]