<d1b2>
<esden> Thanks @tnt got them. Let's see if they will work for us. 🤞
<d1b2>
<tnt> "Stock level: 0pcs". Ah wow, you really took all of them 😅
<d1b2>
<esden> look... desperate times require desperate measures
<d1b2>
<esden> It is a gamble... let's hope it pays off :/
<d1b2>
<esden> (I would be really angry if I got only a few units, tested them, they worked, and I could not get more)
<d1b2>
<esden> (it is still not the 8k pcs we need, but it is getting us closer)
bvernoux has joined #glasgow
<whitequark>
let's see how it works out!
<SnoopJ>
🙏
<ar>
how many were there?
<d1b2>
<esden> bit over 2.5k
<electronic_eel>
@esden i'm looking forward to testing of them. do you want to do live testing in a stream?
<d1b2>
<esden> I don't have a test plan yet. I just jumped on them as they were available, seems close enough replacement, and the price was better than what I have seen otherwise.
<d1b2>
<davidc__> There are another 564 at newark
<d1b2>
<esden> We need to put together a test protocol. (and yes I am happy to send you some parts when I get them @electronic_eel )
<whitequark>
is it a drop-in replacement, or does it need a PCB revision?
<d1b2>
<esden> that is an ongoing problem with these parts, "burst of excitement for a small batch of the part" -> then either "dang someone was faster than me" or "shit too pricy"
<d1b2>
<esden> @whitequark I have not checked yet
<d1b2>
<esden> (I assumed if it needs a pinout change it is still "acceptable")
<davidc__>
Looks to be pin-compatible from a skim of the datasheet
<davidc__>
Vref is different - 0.8v for the ST part, 1.2V for the TI part
<electronic_eel>
yeah, the different vref then needs different resistors on the dac or a different firmware (or maybe both)
<d1b2>
<esden> ok, that is still in the realm "we can deal with this"
<electronic_eel>
i would say so
<d1b2>
<esden> replacing the resistors would make it easier on the firmware compatibility, so I think I would rather do that
<d1b2>
<esden> if we can ...
<electronic_eel>
even if it is just changed resistors, we should somehow mark the units that use this setup. so that it is easy for a user to find out which kind of unit they got, for example when some problem shows up or if they want to tinker with their glasgow
<davidc__>
I'm fairly sure we can just change R27 to account for the difference in VFB
<davidc__>
but let me double check my math
<d1b2>
<esden> @davidc__ thank you 🙂 👍
<davidc__>
esden: according to my unchecked math, keeping R28/R29 and changing R27 to 16.91 k will have the same VDAC = VIO curve
<davidc__>
Now, 16.91 isn't a 1% tolerance value; I've gotta work out the tolerancing - but presumably this is something that needs cal anyways (or we have an acceptable error)
<d1b2>
<esden> Ok cool, making a note of that. We probably should start an issue on github for this.
<davidc__>
er, keep the VDAC _to_ VIO curve the same
<davidc__>
That will also increase the current out of the DAC; that needs to be checked too
<davidc__>
esden: assuming that works, is that the last missing piece for the first batch?
<d1b2>
<esden> Lattice despite promising to expedite shipment are dragging their feet. So I need to follow up on that. And we need to look in alternate footprint for the rail VREGs so I can use the different packaged fixed regulators. I think that is pretty much it.
<d1b2>
<esden> to be honest, the expedited shipping from lattice needs big fat quotemarks on it ...
cr1901_ has joined #glasgow
cr1901_ has quit [Remote host closed the connection]
cr1901_ has joined #glasgow
cr1901 has quit [Ping timeout: 240 seconds]
cr1901_ has quit [Remote host closed the connection]
cr1901_ has joined #glasgow
cr1901_ has quit [Remote host closed the connection]