I cannot get these to work and my IDA skills are too bad to figure out what is happening.
As I said in the other thread, there should also be a debug console avalible that is accessible through TCPIP but I cannot figure out how to connect to it....
I cannot get these to work and my IDA skills are too bad to figure out what is happening.
As I said in the other thread, there should also be a debug console avalible that is accessible through TCPIP but I cannot figure out how to connect to it....
I cannot get these to work and my IDA skills are too bad to figure out what is happening.
As I said in the other thread, there should also be a debug console avalible that is accessible through TCPIP but I cannot figure out how to connect to it....
Just a guess, but maybe Telnet? I have an MSO3034 - I'll give it a try later today and see what happens.
Jay
I cannot get these to work and my IDA skills are too bad to figure out what is happening.
As I said in the other thread, there should also be a debug console avalible that is accessible through TCPIP but I cannot figure out how to connect to it....
Just a guess, but maybe Telnet? I have an MSO3034 - I'll give it a try later today and see what happens.
Jay
OK, so using telnet didn't work, but using my browser (Firefox) brings up a Tektronix menu.
I selected the tab "DATA" and I'm able to talk to the scope using GPIB commands.
I then sent the following per abyrvalg's post:
:SETMODELID 5
:HWAccountant:ACQBandwidth 500
Then power-cycled the unit. It did not make any changes.
So I used the back door password first:
:PASSWord "INTEKRITY"
:SETMODELID 5
:HWAccountant:ACQBandwidth 500
Then power-cycled the unit again. Still no change. I'm probably doing something wrong; I'm an idiot when it comes to stuff like this...
Jay
Great! Try ARMDEMO also - my guess it should enable all options for a specified number of days.
I tried both:
:ARMDEMO DontMakeTheWookieMad, 30
:ARMDEMO DontMakeTheWookieMad 30
:PASSWord INTEKRITY
In other news, with a 500MHz 600mV signal applied from my signal generator to each channel in 50 Ohm mode, all four channels measure a minimum of 520mV, so the scope exceeds the specification of a MSO5054.
QuoteI tried both:
:ARMDEMO DontMakeTheWookieMad, 30
:ARMDEMO DontMakeTheWookieMad 30
Did you do:Code: [Select]:PASSWord INTEKRITY
First?QuoteIn other news, with a 500MHz 600mV signal applied from my signal generator to each channel in 50 Ohm mode, all four channels measure a minimum of 520mV, so the scope exceeds the specification of a MSO5054.
Does it say MSO5054 or MSO3054?
There are "tricks" for the TDS7000B (and others), I can't imagine why the code would be that much different for the TDS5000B...
But it looks like every model series has its own encryption key(s) and options bitmasks, so disassembling the code and finding those would always be step 1...
The logic is always the same... a key is an encryptet version of a bitmask (every bit set being a specific option), coded using the device ID and an (AES) encryption key.
So you (just ;-) need the bitmasks for the different options, the logic to generate the unique device ID, and the AES key...