Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Adrianf1980
    @Adrianf1980
    Hello
    I wonder if the spectrum analyzer is good for a 100% rf noob
    Jose Luu
    @joseluu
    Hi Adrian, it is not as good as a real SA as it has a fixed bandwidth (about 300KHz), and depending on how you scan, you may miss narrow band signals, for instance if you go from 1GHz to 3GHz in 2000 steps, the command software will make it jump every MHz and signals in between the 300KHz BW will be missed. In a word: you have to know how it works and its limitations (can be a good way to learn). Still it has impressive performance if you look for instance at the FM band survey on David's page: http://alloza.eu/david/WordPress3/?p=542 (scroll down 3/4). A few of us are spending some time to make it better (hardware and software wise), and if you factor in the low price, it is certainly worth considering.
    F1CHF
    @f1_chf_twitter
    je suis venu voir ..j'avais jamais vu
    faut pas faire enter , ça part tout seul
    hi ...
    controle et enter pour passer a la ligne
    le CHF
    Jose Luu
    @joseluu
    On peut ajouter des documents par drag/drop, ici la doc de l'ADF4351ADF4351.pdf
    Jose Luu
    @joseluu
    On peut creer des "rooms" par sous-sujet (du D6), a nous de nous organiser
    F1CHF
    @f1_chf_twitter
    pour info j'ai trouvé un boitier en alu pour peanut, il arrive
    F1CHF
    @f1_chf_twitter
    ATTENTION avec ce boitier
    si F1BHY a raison et si ce sont les cotes EXTERIEURES le D6 ne rentre pas dedans !
    j'attends de voir
    le CHF
    Adrianf1980
    @Adrianf1980
    This is so France :( I cant read it
    DavidAlloza
    @DavidAlloza
    Adrian, we are talking about a box case for the D6. This not seem an easy task :)
    Adrianf1980
    @Adrianf1980
    Well as soon as I get my board I will sit on fusion and make a case for it. I can publish the STl file when I’m done
    STL
    Adrianf1980
    @Adrianf1980
    In English or at least a breakdown
    F1CHF
    @f1_chf_twitter
    @Adrianf1980 I have the STL files
    send me an email I will forward
    the files (because I don't if it is possible here) F1CHF at FREE.FR
    DavidAlloza
    @DavidAlloza
    I just release a new version of SNASharp
    All details here : http://alloza.eu/david/WordPress3/?p=791
    HuubH
    @HuubH

    May have done something stupid. I own a V2.032B version of the board. Programmed it with the modified firmware. Tried all of them, but no luck. VFO does work, but input does not show signal. It seems to scan the spectrum but output is a flat line Across the spectrum with an extreme out of range value. Tried with Simple Spectrum Analyzer and SNASharp, no joy. Made a backup of the firmware (i thought) but the file seems corrupt.

    Is there some calibration to be done or could somebody provide me with a backup of the original firmware for the V2.032B board. Any input is welcome.
    Thank you in advance, Huub

    Jose Luu
    @joseluu
    Hello HuubH,
    I made a V6 firmware enabling a pull up resistor on pin4 of the stm32, this should be enough to enable the AD8307, could you try it ?
    Huub Hameleers
    @huubh_gitlab
    Hi Jose, Sure! I will try this tomorrow or the day after. Will report back when done. Huub
    Huub Hameleers
    @huubh_gitlab
    Oke, Jose, could not wait so I just tried the version and it works. Had to repair the trace, disconnected the enable pin from the 5V line and reprogrammed the STM with you latest version. Done that, and used SNASHarp for testing. Thank you for making the effort. Huub
    By the way, can not think of a reason the enable line was added, do you have a clue about that?
    Jose Luu
    @joseluu
    Thanks for trying. No idea why the enable is used, I have checked: it does not help the ADC calibration phase.
    HuubH
    @HuubH
    One other thing (maybe two) Seems i have two gitlab account, sorry about that. The other thing, with the version 6 firmware i seem not to be able to do a callibration in SNASharp. Using a previous DeviceDef with previously run callibration does give me callibrated output.
    Jose Luu
    @joseluu
    Thanks for the info for bug with the calibration in V6. I have to confess I did not test the V6 :-(
    DavidAlloza
    @DavidAlloza
    @HuubH
    What device definition do you use in your test ?
    F1FGV_FIRMWARE_12BITS_D6_JTGP-1033 35M-4.4G or
    HAOBA_D6_JTGP-1033_35M_4.4G ?
    Could you test with "raw cature" checked, the input linked to the output, TG On, and put a screenshot here ?
    Jose Luu
    @joseluu
    I have released a .def file with the V6, nothing special in it, but could be buggy, see: https://github.com/joseluu/D6_firmware/releases/tag/V6
    Huub Hameleers
    @huubh_gitlab
    F1FGV_FIRMWARE_12BITS_D6_JTGP-1033_After_Calllibration_TG_ON.PNG
    F1FGV_FIRMWARE_V06_D6_JTGP-1033_Not_Callbrated_TG_ON.PNG
    F1FGV_FIRMWARE_V06_D6_JTGP-1033_After_Callibration_TG_ON.PNG
    SNASHARP_v06-30_F1FGV_FIRMWARE_V04_D6_JTGP-1033_After_Callibration_TG_OFF.PNG
    F1FGV_FIRMWARE_12BITS_D6_JTGP-1033_After_Calllibration_TG_OFF.PNG
    F1FGV_FIRMWARE_V06_D6_JTGP-1033_After_Callibration_TG_OFF.PNG
    F1FGV_FIRMWARE_12BITS_D6_JTGP-1033_Not_Calllibrated_TG_ON.PNG
    Hi, i've run some test. First a calibration with the latest version SNASharp. With your latest def. file and same test with the included defenition. Trace before and after callibration (cleaned folder) And with TG ON and OFF. Finally an image of the previous version of SNASharp with a nicely callibrated result (Flat). Exchanged callibration file form old and latest SNA version. The calibration file from the 04 definition gives a nice callibrated trace when i disabld the RAW option.
    The names of the imagefiles contain some information
    DavidAlloza
    @DavidAlloza
    Thank you. The raw capture don't take account of calibration, "normaly" you will get the same result with the last version and raw capture disabled as the previous version. If this is not the case there is a bug.
    DavidAlloza
    @DavidAlloza
    I found the issue.
    The "0dB reference" for 12 bits firmware is wrong ( value is for 10 bits capture)
    To fix it:
    Run SNASharp
    open device editor panel.
    change RawMode0dBReference from 510 to 2040.
    And click on "save to disk"
    after the fix, the curve will drop to -8dB in raw mode
    Huub Hameleers
    @huubh_gitlab
    F1FGV_FIRMWARE_12BITS_D6_JTGP-1033_After_Calllibration_TG_OFF.PNG
    Thank you. This morning I changed the value from 510 to 2040 in the default definition F1FGV_FIRMWARE_12BITS_D6_JTGP-1033 35M-4.4G. That worked. See screenshot. Couldn't get the other definitions to work correctly using the calibration option in the latest SNASharp. What puzzles me is that the file contents of the definition files are the same as far as i can see. Getting complex, surely I'm missing something but no worries, I’m happy now.