Regarding the "Revisions"
LP1 = Lab Prototype 1 (normal first prototype build with final design)
LP2 = Lab Prototype 2 (second interation)
PP = Production Prototype (Final production design to do tests with, dropping, climate chamber, EMC and such)
put those bad emissions on frequencies of the nearby radio station next to the testlab! So no one will know
Sounds reasonable, except these aren't prototype units.
Regarding the "Revisions"
LP1 = Lab Prototype 1 (normal first prototype build with final design)
LP2 = Lab Prototype 2 (second interation)
PP = Production Prototype (Final production design to do tests with, dropping, climate chamber, EMC and such)
put those bad emissions on frequencies of the nearby radio station next to the testlab! So no one will know
Sounds reasonable, except these aren't prototype units.
Yes, but you're inserting much lower values than your production unit started with. You originally had a product config of 24, with a revision of FPR.
Regarding the "Revisions"
LP1 = Lab Prototype 1 (normal first prototype build with final design)
LP2 = Lab Prototype 2 (second interation)
PP = Production Prototype (Final production design to do tests with, dropping, climate chamber, EMC and such)
put those bad emissions on frequencies of the nearby radio station next to the testlab! So no one will know
Sounds reasonable, except these aren't prototype units.
Yes, but you're inserting much lower values than your production unit started with. You originally had a product config of 24, with a revision of FPR.
Yes, just some leftover identifiers in the firmware images that haven't been cleaned out. Exactly the sort of thing that can get invalidated by a new firmware update.
You can calculate the voltage needed for a given ID by this equation.
x=ID#
5/1024*64*x=Voltage
Yes, but you're inserting much lower values than your production unit started with. You originally had a product config of 24, with a revision of FPR.
Right.
FPR=Final Production Revision?
But it never ceases to amaze me seeing Dave use this huge soldering iron tip on small board items (me, I prefer the small tips for that ! I guess it's an Australian thing, like the butcher knife ... ).
I reckon it might be a genetic thing from British ancestry, my go to Iron is a Weller W60D with a 3.2mm tip and it gets used for *everything* down to and including rework on stuff like this BL1551 (which is in a smaller package than the SOT363 and yes, I did catch the plastic on the connector but replaced it afterwards for cosmetic reasons).
For really small stuff I might use a smaller iron tip.
Yes, but you're inserting much lower values than your production unit started with. You originally had a product config of 24, with a revision of FPR.
Right.
FPR=Final Production Revision?
Yep it´s "Production Run"
L* is normally not produced by the production P* is produced on the production line, this is especially relevant if the production site is not the same site as the development site IMHO..
Most of the time the serial numbers gives away the country of origin, so US* is produced in US (at least assembled and tested) as far as i know.
I'm surprised no one has put a set of digital potentiometers, wacked in a relay, and automated the configuration testing
Sent from my SM-G935V using Tapatalk
Actually using a row of d-pots you can automate the testing process, and then you can select the model you want before boot through an Arduino-based interface, setting the d-pots to the appropriate values.
Does someone have an image of the AWG section from a NON-AWG version?
As Dave brillantly pointed out, that option seems to be enabled by those ID resistors.
I'm really interested to know if the parts are fully unpopulated or simply missing the BNC.
As the option brings the price of the scope up by about 200$US, a "solder yourself" part list would be a great aftermarket warranty-voiding option!
Thanks!
Great news that the hack is working on Dave's unit. But remember that he has the full list of software keys enabled.
It might be that the resistors allow the system to know the
capabilities of the scope's hardware, but the final decision of enabling and disabling an upgradable feature could very well still be up to software licence keys. That would be at least how i would design such a product feature.
So perhaps Dave's scope is not the best scope to verify all these upgrades on... But still good news that a 100MHz enabled bandwidth scope can be upgraded to a 200MHz+ model
I wonder why they even do it that way (configuration resistors).. So they have to keep boards with different part numbers in their warehouse for the different configurations... Otherwise production could just assemble the units, whack on a sticker with the correct model number they are currently producing and flash it to the right Bandwidth / Samplerate setting via Software.. So one Board version instead of X...
The BNC Connector + analog circuits could be put on a daughterboard which is only installed once someone buys the option in the models with that option.. So you can mass produce the base boards and use them in all productversion instead of doing a specific board for each version...
It could be that the resistors Dave changed are only the "pullup" resistors (or better said the fixed part of the divider), and that the config resistors are on the other board. Which makes more sense.
resistors are generally to tell the software what build variant the hardware is, so there will be other differences spart from the R's
Just spotted this in the datasheet, implying that at least some of the wavegen hardware is fitted as standard.
All models come standard with built-in training signals
One other thing,
The EDU models have very limited memory depth: 100kpts vs 1Mpts for the non EDU.
I'm wondering if this is easily verifiable to check if a hacked scope will get more of those sweet pts'es.
I think someone needs to go buy an EDUX...
I think someone needs to go buy an EDUX...
You think anyone round here's going to buy one before the end of the month?
There is more difference:
Trigger types: edge, pulse width, and video on EDUX1000-Series models.
DSOX1000-Series models add: pattern, rise/fall time, and setup and hold.
but this seems to be only software modes.
Does someone have an image of the AWG section from a NON-AWG version?
I bought the 70MHz version without AWG (DSOX1102A). Here are pics of the main board.
So that answers the question about population - not only the function gen outputs not fitted but also some PSU components near the power-in connector.
Is the PSU the same ?
15 and 18 volt supplies for the Wavegen I guess.
Is the PSU the same ?
Here's the power supply. Looks the same to me as the one in Dave's teardown. I'm happy to take other pictures of the scope if anyone would find them useful.
I wonder, if you do the mod described, if you would get an error for missing components.
Sent from my SM-G935V using Tapatalk