2011-08-01 00:25 ah is true http://gnss-sdr.ru/media/1/20101004-screenshot.gif, Artyom dint get track.. 2011-08-01 00:25 yeah, same situation as my self :-S 2011-08-01 00:25 i guess osgps never got track as i was feeding it with complex data 2011-08-01 00:25 even after sample 40Mb of data 2011-08-01 00:27 also this gps-sdr from CTA es kinda slow and cpu consuming, was very wise from him to swtich to scilab :-) 2011-08-01 00:31 so what's the plan then ? wait for Artyom to fix things on his side ? 2011-08-01 00:32 no of course not 2011-08-01 00:33 also his side have its complexity that he only understand 2011-08-01 00:33 i still on my namuru debugging, afaik cant make carrier nco to work.. 2011-08-01 00:34 once i get it work, the accumulator should start to work 2011-08-01 00:35 ah, so your troubles are still in earlier processing stages than his. i see. 2011-08-01 00:35 with namuru yes 2011-08-01 00:35 but in full software processing kinda same 2011-08-01 00:37 but i had same issues as heen before with the acquisition module, i got prn code detection but couldt lock it.. 2011-08-01 00:37 that was with osgps 2011-08-01 00:38 i soft mode to put it a name 2011-08-01 00:38 he was very kind to sent my hist vhdl namuru code 2011-08-01 00:39 i discover i missed a state for the time base counter on my verilog code 2011-08-01 00:39 fixed now, i'll try as soon sitesis finish 2011-08-01 00:40 cool. that's probably a good bug to fix ;-) 2011-08-01 00:42 well, i depend may be xst asumed what he wrote in the code and i specify 2011-08-01 00:42 and sadly it wast related to my carrier nco stuckness... 2011-08-01 00:42 and i'm using carrier_nco code as it is.. 2011-08-01 00:43 so the error should be in higher layers.. 2011-08-01 00:48 the harder the bug to fix, the greater the glory ;-) 2011-08-01 00:55 [commit] Werner Almesberger: ptrude/: functions for path stretching and calculation of proportional length (master) http://qi-hw.com/p/cae-tools/7ef6269 2011-08-01 00:55 [commit] Werner Almesberger: ptrude/: changed extrusion from xy path to xz path; variable number of faces (master) http://qi-hw.com/p/cae-tools/ee63445 2011-08-01 00:55 [commit] Werner Almesberger: ptrude/: many major math fixes, especially in stretch_path (master) http://qi-hw.com/p/cae-tools/26a0f4c 2011-08-01 07:28 kristianpaul: don't you think the Nyan cat is more like 400 microns high? 2011-08-01 07:29 http://en.qi-hardware.com/wiki/Copyleft_Hardware_News_2011-08-01#Homebrew_CMOS_and_MEMS_foundry_design 2011-08-01 11:49 wolfspraul: dunno may be azonenberg can tell us more 2011-08-01 11:56 hi kristianpaul 2011-08-01 11:56 hello 2011-08-01 11:57 I've seen discussion about real/complex data samples from your front-end 2011-08-01 11:57 ah yes, 2011-08-01 11:57 it make complex out of the box.. 2011-08-01 11:58 but at time i tested i havent software avaliable for complex procesing.. :( 2011-08-01 11:58 and what is sampling frequency and intermediate frequency? 2011-08-01 11:58 and bandwidth? 2011-08-01 11:58 2.556 intermdiate 2.048Mhz sampling 2011-08-01 11:58 every sample 4 bits 2011-08-01 11:58 oh... 2011-08-01 11:59 But can you use higher sampling frequency? 2011-08-01 11:59 yeah, in real mode 2011-08-01 11:59 16.694Mhz of sampling 2011-08-01 12:00 same IF, 2 bits per sample 2011-08-01 12:00 i switched to that mode now 2011-08-01 12:00 but all went i can try complex agains namuru 2011-08-01 12:01 btw i checked you code, i added a codition to the counters that i missed, but of course time_base was working before 2011-08-01 12:01 and i still get the carrier nco stuck :( 2011-08-01 12:02 In my front-end I also have complex-data output. I have IF=2.42MHz Sampling=16MHz and bandwidth=4.2MHz. When I work with osgps, I just throw away all Q-samples and use only I-samples. 2011-08-01 12:02 Artyom: every sample 4 bits at 2.048 MSPS at 8.192 Mhz sampling clock in other words 2011-08-01 12:02 still using maxin right? 2011-08-01 12:02 yes 2011-08-01 12:03 you trought away all Q-samples?? but what happened if carrier mas in that? 2011-08-01 12:03 i may be wrong but i think is no always exactly this guess 2011-08-01 12:03 s/carrier/C/A 2011-08-01 12:04 s/guess/asumption 2011-08-01 12:05 what do you mean "what happened if carrier mas in that?". Can you explain in more detail... 2011-08-01 12:05 ah, moment you work with GLONASS not GPS right? 2011-08-01 12:08 in GPS L1 signals there is a P-code and C/A code 2011-08-01 12:08 I work with both. But now as I use osgps+namuru I work with GPS only. Later It will be easy to switch to GLONASS 2011-08-01 12:08 on is in phase other quadrature, (dont remenber wich on is who..) 2011-08-01 12:08 Yes, In GLONASS the same thing 2011-08-01 12:08 oh nice 2011-08-01 12:09 i may may be wrong but i undertood that processing just Q for example you cant get the P-code 2011-08-01 12:10 but as i said, is a _guess_ for me i never dig in to 2011-08-01 12:10 No, this is wrong 2011-08-01 12:10 :-) 2011-08-01 12:10 :( 2011-08-01 12:11 In receiver there is another meaning in quadrature channels 2011-08-01 12:12 We use quadratures in receiver when we work with signals with unknown phase (like it is in GPS/GLONASS/COMPASS/GALILEO) 2011-08-01 12:12 ah 2011-08-01 12:15 well. i'll check more theory about this later 2011-08-01 12:16 btw before i leave cause i travel to work like 2hr and i have a meeting in the morning.. 2011-08-01 12:17 the carrier phase register in namuru just need to be written once isnt? well at least for initilization, later i may be ajusted acording to doppler etc.. 2011-08-01 12:18 i think i'll write a testbench for it, and debug it individually.. 2011-08-01 12:18 which exactly register are you asking about? 2011-08-01 12:18 CODE_NCO 2011-08-01 12:18 and  CARRIER_NCO 2011-08-01 12:19 during acquisition you set CODE_NCO to a fixed value 2011-08-01 12:20 yes 2011-08-01 12:20 and CARRIER_NCO is changing according to current doppler-bin (where we search the signal) 2011-08-01 12:21 And during tracking we always change their values 2011-08-01 12:21 both CODE_NCO and CARRIER_NCO 2011-08-01 12:23 but then CARRIER_MEASUREMENT will not change its value over the time if i dont change the CARRIER_NCO ? 2011-08-01 12:24 cause i'm initializing both CODE_NCO and CARRIER_NCO with fixed values 2011-08-01 12:24 if i read CODE_MEASUREMENT it looks like is changing vauet but not the case for CARRIER_MEASUREMENT.. 2011-08-01 12:25 that let me thing something wrong was happening with the carrier nco module.. 2011-08-01 12:26 may be, I can't tell you exactly as I didn't dig so far. I only tried to control tracking loops. And CODE_MEASUREMENT and CARRIER_MEASUREMENT are used later for calculating pseudoranges... (if I'm not wrong) 2011-08-01 12:31 hum. but how you track if the carrier nco is not fixed first? 2011-08-01 12:31 or i'm misiing something.. 2011-08-01 12:32 agrh, i must leave now, but my irc client gets here catching 2011-08-01 12:32 bye Artyom 2011-08-01 12:32 bye 2011-08-01 12:34 but you read the accumulators right? i mean after initializr CODE_NCO and CARRIER_NCO ? 2011-08-01 12:35 also if read it must be before got overwrite 2011-08-01 12:35 I read only i_prompt,q_prompt,i_late,q_late 2011-08-01 12:35 i read all, but zero is the cotent tought.. 2011-08-01 12:36 okay now leaving, i'm late ;) 2011-08-01 12:36 bye 2011-08-01 12:38 I must make a note: I tried to use my own code for tracking. In general we have only to read i_promt,q_prompt,i_late,q_late_i_early,_qearly in order to calculate errors of our carrier-generator and code_generator. And based on these 6 values we can calculate new values for CODE_NCO and CARRIER_NCO. 2011-08-01 12:39 In osgps there are some additions to the general rule: 2011-08-01 12:42 During pull-in process additionally navigation bits border is also identified. And additional checks are made in order to be sure that the process is working correctly. 2011-08-01 12:43 And also osgps uses only 4 values i_prompt, q_prompt, i_late, q_late. 2011-08-01 12:49 Based on these 4 values every ms during pull-in process new CARRIER_DCO and CODE_DCO values are calculated. During tracking process CARRIER_DCO is updated every ms and CODE_DCO is updated every 20 ms. 2011-08-01 12:50 And CODE_MEASUREMENTS/CARRIER_MEASUREMENTS are used only every 100 ms to calculate pseudoranges. 2011-08-01 14:24 The build has FAILED, see log here: http://fidelio.qi-hardware.com/~xiangfu/compile-log/openwrt-xburst.full_system-07312011-1105/ 2011-08-01 14:25 wolfspraul I was w-r-o-n-g re ARM costs. The use case I was thinking of is this part: 2011-08-01 14:25 NXP LPC1768, ARM Cortex M3 100MHz, ~$5 in >1K volume. 2011-08-01 14:26 meh.. this shipping logistics makes my brain hurt 2011-08-01 14:27 these madmen who wrote those texts and regulations 2011-08-01 14:27 semi-unrelated factoid: the per-piece royalty to ARM when a licesee produces an ARM-based CPU is as low as $00.07 per chip 2011-08-01 14:27 hello roh 2011-08-01 14:28 rjeffries: yeah. thats not really a cost factor for us at the volumes we do. 2011-08-01 14:28 roh I was not suggesting it was. I had calimed a 1GHz Arm was $5 I was wrong about that 2011-08-01 14:29 rjeffries: fair enough. 2011-08-01 14:29 even lower than 7 cents 2011-08-01 14:29 2-40 cents, afaik 2011-08-01 14:30 it is a tough business for sure 2011-08-01 14:30 imx233 is 7.05Euro at digikey 2011-08-01 14:30 nah, all fine. they don't shoulder the expensive and risky part. 2011-08-01 14:30 454mhz 2011-08-01 14:36 gnnnh. 2011-08-01 14:36 wolfspraul: any idea what zolltarifnummer to use? 2011-08-01 14:36 no idea 2011-08-01 14:38 fsck.. i havent got a clue either.. there are thousands 2011-08-01 14:47 it seems i have to atleast fill a CN23 2011-08-01 14:53 fsck. need this number.. gah. 1h till the shop closes 2011-08-01 15:09 roh: is that the same as HS code? I found "390690  Other Acrylic Polymers" 2011-08-01 15:09 :-) 2011-08-01 15:09 but there's also metal and other stuff inside... 2011-08-01 15:11 exactly.. i only found codes withing 39xxxxxx which are for uncut material 2011-08-01 15:19 this zoll-lists are a serious case of TL;DR 2011-08-01 15:45 roh: try to google for something similar in china. they sometimes list the HS code. 2011-08-01 15:45 roh: i.e., acrylic case screws "hs code" 2011-08-01 15:45 first hit: Face plastic case with screws (HS Code : 85439000, made in china) 2011-08-01 15:47 854390  "Parts of Particle Accelerators, Audio Mixers, High Frequency Amplifiers" hehe ;-) 2011-08-01 15:48 maybe i should just note the first 4 chars and a ? 2011-08-01 15:48 3906? 2011-08-01 15:48 need to run. closing in 10 minutes 2011-08-01 15:49 you can abbreviate the numbers. but i don't remember to what point. 2011-08-01 15:49 ask them if they actually want the code :) 2011-08-01 15:49 fedex usually do (but they're probably okay without it, too) 2011-08-01 15:50 when i asked at the postal office, they said "no" (there's room on the form for it, in case you insist) 2011-08-01 16:20 wolfspraul: how's the news coming along ? the 2 months schedule seems to be a little tough for the sheer quantity of things - even if july was actually fairly quiet on the ben side (and quite the contrary on the m1 side) 2011-08-01 16:56 shipment shipped 2011-08-01 17:08 did you put a code ? 2011-08-01 17:10 nope 2011-08-01 17:10 filled a CN23 2011-08-01 17:10 ;) 2011-08-01 18:38 hello everyone ! 2011-08-01 18:38 Long time no see ! 2011-08-01 18:40 What's up since the last month ?