azonenberg changed the topic of #scopehal to: libscopehal, libscopeprotocols, and glscopeclient development and testing | https://github.com/azonenberg/scopehal-apps | Logs: https://libera.irclog.whitequark.org/scopehal
agg has quit [Ping timeout: 250 seconds]
agg has joined #scopehal
Degi_ has joined #scopehal
Degi has quit [Quit: ZNC 1.7.5+deb4 - https://znc.in]
Degi_ is now known as Degi
someone-else has quit [Ping timeout: 240 seconds]
Degi_ has joined #scopehal
Degi has quit [Ping timeout: 256 seconds]
Degi_ is now known as Degi
massi has joined #scopehal
someone-else has joined #scopehal
someone-else has quit [Quit: Connection closed]
someone-else has joined #scopehal
<azonenberg> what do you guys think? this is probably going to be the winner for AKL-PT5 cables
<azonenberg> price tag is half what SV Microwave wanted for a similar cable assembly
<azonenberg> a lot of vendors did not offer .047" SMA to SMPM at all, only .086" cable which tends to be stiffer
<azonenberg> and the insertion loss out to the band of the probe is... not ideal but also not bad
<azonenberg> and they offer serialized s-parameter data
<someone-else> price seems ok for a cable with quality connectors and serialized s-parameter data
<azonenberg> SV Microwave wanted $263 each
<someone-else> some Chinese vendors might be able to beat it for a custom cable, but quality assurance might require cultivating some sort of relationship with them
<azonenberg> and i dont think that even included serialized data
<someone-else> SV Microwave being SV Microwave I suppose
<azonenberg> lol
<someone-else> wrt Chinese vendors: I bought some 2.4mm-2.92mm adapters for $20-30 ($150ish from SV Microwave) and manufacturing quality turned out to be excellent; although the s-parameters they provided seemed to be from the same adapter model, but not the same adapters I got
<someone-else> so perhaps if volume is sufficient, savings could be substantial enough to go through the trouble of talking to them and doing some extra qa
<azonenberg> I will be doing 100% pin gage measurement on the SMA side (I don't have SMPM gages at the moment otherwise i'd do that too)
<azonenberg> and including that info in my QA report with the probes when shipped
massi has quit [Remote host closed the connection]
<someone-else> that's fantastic customer service
<azonenberg> i've been given way too many out of tolerance SMAs in th epast
<azonenberg> When someone gets hardware with a SMA from me, they get measurements of pin and dielectric position to the nearest .001"
<azonenberg> and traceability information with the make/model/serial/last cal date of the gage i used
<someone-else> yep, an SMA gage is on my shopping list too
bvernoux has quit [Quit: Leaving]
<azonenberg> miek: hey, so for the USB decoder we have
<azonenberg> does it work on a single leg? a differential pair? etc
<azonenberg> i.e. is there a way to make it work using a single scope channel?
<azonenberg> (high speed)
<miek> right now it uses a channel on each leg, but i'm pretty sure it would be possible to use a single differential channel for high speed
<d1b2> <zyp> high speed doesn't have single ended tokens, right? just squelch IIRC
<azonenberg> miek: ok
<azonenberg> long term when possible i would like to support 2x SE or 1x diff on as many protocols as possible
<azonenberg> even if you lose some information
<azonenberg> e.g. for MIPI D-PHY i think you can't do out of band signaling because you can't distinguish the LP-00 and LP-11 states, both are differential zero
<azonenberg> but you can decode the high speed signaling fine with a single diff probe
<azonenberg> this cannot be done yet but is on the wishlist (right now you need two SE inputs)
<azonenberg> i think
<d1b2> <zyp> IIRC SE1 is not a valid token in LS/FS, so you could also assume a differential zero is SE0
<d1b2> <zyp> oh, wait, SE1 is disconnected port, since upstream has weak pullup on both lines
<d1b2> <zyp> but that's not important for protocol decode
<azonenberg> well if you are trying to debug link startup it is
<azonenberg> i eventually want to be able to do full compliance testing and such on all of these protocols
<azonenberg> including negotition
<azonenberg> but at the same time, i want to support options where all you care about is upper layer data, using as few probes as possible
<azonenberg> Give the user options and they can decide what makes sense
<d1b2> <zyp> yeah, that's what I mean, there's some information there, but in many cases you don't need it
<azonenberg> yeah
<azonenberg> long term i want to add a lot more validity checking etc features
<azonenberg> to aid in compliance testing and debug of protocol implementations
<azonenberg> but at the same time have a "permissive mode" that will decode anything you throw at it as best as it can
<azonenberg> even if somewhat malformed
<azonenberg> so you can help debug a broken protocol implementation
<azonenberg> e.g. if the CRC is bad it will still try to decode the upper layer data