-
-
Notifications
You must be signed in to change notification settings - Fork 217
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BOM changelist #14
Comments
Hi, thanks for the suggestions. If you compare the schematic with the earlier version (https://github.com/jankae/VNA) you'll notice that I pretty much changed parts in exactly the positions you mentioned before, when redoing the design for this version. Some initial thought from my side:
Although the RFSA3714 is only specified down to 50MHz, it actually works great on my prototypes all the way to 100kHz (going down even further doesn't really make sense because of the limitations of other parts). I guess RFSA3713 or PE43711 would work just as well.
If the PE42420 also works at lower frequencies, it could be an option but I don't see the need to change it at the moment. From what I've found,
The B012-617DB-1-63-B331 is actually a replacement for the TCM1-63AX+, so yes, that would definitely work as well. The MABA-011082 is what I used in the first prototype and while it is OK, I measured a slightly worse directivity than with the B012-617DB-1-63-B331. The problem with all of these is that you need to remove the tertiary winding, otherwise they won't work very well at all. For prototypes, this can easily be done with tweezers and a steady hand. |
Hi friends! |
Hi nbgsmk |
Exactly! |
Oh,thank you for your reply, |
Yes, you need to remove that winding, otherwise the directivity is really bad at higher frequencies and you won't be able to make accurate return loss measurements. |
Thanks,and I guess it is due to balun's unbalunce?It seems that the balun is not designed for high directionality. |
I believe the issue is that all these baluns are designed for single-ended to differential conversion (I guess that is also implied by the name balun :D). What really is required at that point in the schematic is a common-mode choke. Something like a CX2156NL would be more fitting. However, I couldn't find anything (at least nothing affordable) with a wide enough frequency range. |
Hi All, Where can I get all the parts in the BOM? I tried JLCPCB for SMT Assembly, but almost half of the parts are not available, especially the ICs. I've decided to order just the PCB & Stencil and do the assembly old-fashioned way (by hand!). Still, I couldn't find all the parts needed in Mouser or Digit Key. |
Hi, there are some parts that are hard to find, the biggest problem is most likely the balun. As stated above, you can use the TCM1-63ax+ instead (might have to adjust the shielding a tiny bit because this balun is slightly higher). I didn't do a thorough check but most other parts should be available at mouser as well as digikey (at least they were when I last ordered there for this project). Two exceptions I know of:
|
Hi @fickybabs ! Back to the actual build, my idea was to use LCSC and their smt assembly service for almost all that is available. I would rather pay, say...10$ (forgot how much it was) than spend two days fiddling with a bunch of resistors and capacitors. If you divide the cost of smt assembly with the working hours it would take you ...is it really worth it? It depends. ;-) I do hope my thinking helps you. Zoran |
Hi Jan, Thank you for your prompt response. It seems the TCM1 will be available next week on Mouser, and I just found LDL212PU50R on DigitKey. Things are looking good, still have about 6 parts to search for. I like to take this opportunity to thank you for sharing this project. I have all the other nanoVNAs including the recent Plus4, but OWO and edelswartz123 introduced me to your project. This one would work best for my application (6GHz). I currently use a Copper Mountain VNA that cost $5k and only goes up to 5.4GHz. |
Thanks for sharing your BOM. I tried to go through the same process as you when ordering from JLCPCB. The minimum order for the PCB is 5 and the assembly is 2. The total came up to about $240 with shipping without any of the ICs and lots of extended parts. I ordered stencil with it but I thought that will be useless since I would have to but all the parts to use the stencil on a new board. So I cancelled the order and decided to order the PCB with stencil only. |
Sorry for the late reply, somehow I missed this message. |
Thanks,I am projecting the PCB in JLCPCB. I use KICAD. I have made some changes based on yours, such as the package size. Some traces go to the inner layer to shield the entire module without leaving obvious gaps. |
I was thinking exactly in the same direction - closing some chambers and routing signal traces on inner layers. My first thought was decrease the crosstalk by closing the port1/2 cavities near the source switches IC17, IC18. |
I agree with you very much. Although vias will have an impact, I think I should pay more attention to isolation than isolation.IC16, IC17 and IC18 have relatively far physical separation. I guess there is not much impact. Therefore, I only switch the traces near T3, IC21, and IC24 to the inner layer, and then close the shielding cavity. In addition, the resistance and capacitor packaging are reduced, the 5V external power is changed to a 12V external power supply and the packaging of relatively easy-to-purchase components is replaced. |
Could you share a few details about the conversion to KiCad and how you edited the soldermask for the shielding? I am an absolute beginner in KiCad but would like to move this project away from Eagle eventually. However, I couldn't figure out how to edit/create the soldermask layer with round features. See also #1 and #7 for more details. About the isolation: I am curious to see how your changes improved that, please share some measurements once you finished the assembly. I am currently attempting to add RF gaskets (as suggested here) to improve the isolation. The grooves are already milled but measurements will have to wait until after the christmas holidays. |
I will update my measurement data after finished the assembly! |
I have soldered the PCBA, but some problems cannot be solved. |
Can you share the schematic? I don't think I can help without it, since you changed the power supply section on your PCB |
I use the USB power,here is my schematic: |
Sorry to hear that... At first I thought maybe you are able to fix it with botch wires, but the LQFP variant is missing a few pins (PC4/PC6/PC10/PC11). You could do without PC10/PC11 (just no debug output) but PC4 is used for I2C. It still might be possible if you find another free SCL-pin to replace it but this starts to get complicated and would also need a software change... Maybe get the other STM variant and solder the UFQFPN onto the LQFP footprint? I'm not sure whether that is even possible but if I remember correctly, at least the pitch is the same |
Yes, when I modified the PCB at the beginning, I was compatible with both packages, but later found that the U6 version was difficult to buy, so I only bought the T6 version. |
I don't have access to my ST-Link right now, but I think it also shows that error. Not really sure what it is about but the important thing is the ** Verified OK ** some lines below. Looks to me as if the flashing worked. Do any of the LEDs light up? |
|
Sorry, I meant LEDs on the VNA. If you just flashed the firmware, the error LED should report a "Flash empty" error (see also the user manual and https://github.com/jankae/VNA2/blob/master/Documentation/DeveloperInfo/BuildAndFlash.md (Getting a new board running at the bottom of the page). |
I'm very sorry to disturb you. Therefore, I think the hex should not be flashed successfully |
Ok, that does sound like flashing didn't work. Which really confuses me, because the verification appears to be correct. Another strange thing: two lines above the error the STM32L4xx is mentioned. Maybe just a typo in OpenOCD? Two more wild guesses:
Edit: you managed to debug the program and it already showed up as VNA on USB? During debug, the MCU is already programmed and a simple reset after debugging should restart the program. The fact that you land in the DFU mode afterwards makes me even more suspicious of the BOOT0 pin |
I'll check my connection further, anyway, It reminds me: The fact that you land in the DFU mode afterwards makes me even more suspicious of the BOOT0 pin |
Did you figure out what caused it to boot into DFU mode or do you have to exit DFU mode every time now? |
I tested the capacitance of 1nf with the self-made TRL calibration kit, the error was 11.3%, and there was some resonance. This may be caused by the cable I used (CINCH 415-0029-012). When I switched to a semi-flexible cable, the trace resonance will be a little better |
Hi, just wondering, are you planning to release your kicad source files, I'd quite like to take a look at them? |
Actual KiCad source files are available in special branch https://github.com/jankae/LibreVNA/tree/kicad it is Work In Progress
|
Hi, thanks for that, I have downloaded the files and I'm now looking at them in kicad! |
closing due to inactivity |
First of all, it's really, really great,and thanks for your design and sharing.
After looking at the design, I raised the question of component replacement in order to further reduce costs or improve performance(according to each person's own situation):
1>RFSA3714(50MHz to 6000MHz) to RFSA3713(5MHz to 6000MHz),Package is not pin to pin
or to PE43711(9kHz to 6000MHz) ,Package is pin to pin;
2>QPC6324SR(5MHz to 6000MHz) to PE42420(100MHz to 6000MHz) ,Package is pin to pin;
3>B012-617DB-1-63-B331(10MHz to 6000MHz?) to TCM1-63AX+(10MHz to 6000MHz),B012-617DB-1-63-B331 is EASTEVER BALUN,but I can't find the datasheet,can you provide the datasheet?I would be very grateful!
or
MABA-011082(5MHz to 8000MHz)
The text was updated successfully, but these errors were encountered: