Products > Test Equipment
open source GPIB adapter
dazz1:
--- Quote from: coromonadalix on October 27, 2024, 10:50:43 am ---if your design suit your needs :-+ and for sure i would love more leds / indicators
i have 2x of the Xyphro adapters, no complaints ... works fine ... but sometimes i would have loved more leds to get the connection status ...
--- End quote ---
I find more LEDs is an essential feature.
If I show SWMBO something with no LEDs, her eyes instantly glaze over as she ponders what will happen in the next episode of Coronation Street. ::)
If I show her something with LEDs, I can hold her attention for at least a few seconds. 8)
--- Quote from: coromonadalix on October 27, 2024, 10:50:43 am ---i hope you'll do some tests with wingpib or other gpib softwares, the id string can play tricks ...
--- End quote ---
None of my test equipment is young enough to have an ID string, so I can't help there. Of course if anyone would like to donate any test equipment for testing, it would find a good home here. :-DD
dazz1:
--- Quote from: Kean on October 27, 2024, 10:58:44 am ---
--- Quote from: dazz1 on October 26, 2024, 08:09:53 pm ---OK but not obvious to me. I haven't yet figured out the Github etiquette This was an all or nothing change. I wanted to submit a complete and completed package, not a series of half baked code changes. If Xyphro is not processing pull requests, the point is moot.
--- End quote ---
No better way to learn than have a go, and you've proven yourself to be someone that does that.
I'm no expect on Github either, and I've only done a few pull requests. You can make some changes to the pull request once created, either via command line or the web interface - but it will be via changes to your fork. Sometimes the best way is to create a branch for the pull request, which you can delete later.
--- End quote ---
If Xyphro isn't processing pull requests, the only incentive to creating pull requests is to alert others that there is some ongoing development.
I have already stripped out all version 1 stuff from my fork so that it is dedicated to the enhanced version 2e. My current understanding is that will effectively block acceptance of any future pull requests by Xyphro because it would wipe out all the version 1 stuff that should be kept on Xyphro's site. I think it would require Xyphro to create a new branch that he would pull in and clone my version 2e branch. That might be desirable, not-essential if people can just get the version 2e files they need from my site.
eliocor:
here it is a (v2e) BOM for buying components from LCSC or for PCB assemby by JLCPCB.
BOM contains indicative prices (€) and MOQ
For PCBA by JLCPCB the file should be slightly edited:
- delete line(s) LED1 or LED2.3 according to your choices
- it seems U1 can be chosen in two different cases: leaded and leadless. Is it correct*?
- priority was given to components in the BASIC list
*) was the PCB designed to accept leaded and leadless cases for U1?
dazz1:
--- Quote from: eliocor on October 28, 2024, 12:02:04 am --- was the PCB designed to accept leaded and leadless cases for U1?
--- End quote ---
Thanks for the BOM.
The Ver 2e PCB is designed only for the leaded version of U1. The first versions I made were for the leadless MCUs but I had issues with soldering them. The leaded version is much easier to hand solder.
I will add your BOM to my Github site.
dazz1:
Hi
I have just updated my ver 2e BOM because some parts I purchased from Aliexpress and those might not be an option for an assembly service. I have now identified parts from element14 that are equivalent to the Aliexpress parts.
The exception is the usb-c connector. element14 don't stock the HRO part. I am reasonably sure there are equivalents by other manufacturers that fit the same foot print. I just don't know the part IDs.
I have pushed the update BOM to Github. Would you like to check that against your BOM against my updated version before I push yours to Github?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version