| Products > Test Equipment |
| Picoscope Hack |
| << < (15/18) > >> |
| _Wim_:
--- Quote from: egonotto on December 13, 2022, 04:32:16 pm ---Hello, here are 3 pictures with sine with 50 Ohm termination 100 MHz 301 MHz and 320 MHz Best regards egonotto --- End quote --- Excellent! Thanks for confirming, this saves me from trying to fix something that would not have been fixable. :phew: |
| _Wim_:
A bit off topic, but not completely... Because the BG7TBL noise source was very spiky between 0 and 2MHz, I had always been using a low cost DC block to act as a high pass filter. Today I made a quick and dirty filter board to get completely rid of these spikes (5th order filter), and also flatten the response up to 200Mhz. After some experimentation, I achieved a flatness of < 2dBm between 10Mhz and 200MHz. For reference, I attached also the spectrum measured up to 2000MHz measured with my CMU200, but the high frequency spectrum is not changed. |
| jasonRF:
I can verify that there is at least one Picoscope that doesn't follow this hacking recipe. :-DD I have a 2204a I purchased in 2016. The hardware version is 17. Anyway, increasing byte 0B by 1 and decreasing byte 1B by 1 did not do the trick. I have tried a bunch of other options as well, but so far all of the trials have resulted in a device that the picoscope software does not recognize. Edit:forgot to say that i am trying to turn it into a 2205a, which has identical hardware. The eeprom on my 2204a is definitely different than the one discussed on the sigroc page. For example, B7-D9 and F8-FD are all non-zero. I have of course mucked with some of these bytes as well - especially F8-FD that look less like cal data than some of the other areas. I am very inexperienced when it comes to this kind of stuff, so any suggestions you-all might have would be helpful. For the trial and error approach I have been using so far, it might be time to write a python script to automate it more. In any case, it has been fun to play with this. cheers, jason |
| _Wim_:
--- Quote from: jasonRF on May 27, 2023, 09:39:36 am ---I can verify that there is at least one Picoscope that doesn't follow this hacking recipe. :-DD I have a 2204a I purchased in 2016. The hardware version is 17. Anyway, increasing byte 0B by 1 and decreasing byte 1B by 1 did not do the trick. I have tried a bunch of other options as well, but so far all of the trials have resulted in a device that the picoscope software does not recognize. Edit:forgot to say that i am trying to turn it into a 2205a, which has identical hardware. The eeprom on my 2204a is definitely different than the one discussed on the sigroc page. For example, B7-D9 and F8-FD are all non-zero. I have of course mucked with some of these bytes as well - especially F8-FD that look less like cal data than some of the other areas. I am very inexperienced when it comes to this kind of stuff, so any suggestions you-all might have would be helpful. For the trial and error approach I have been using so far, it might be time to write a python script to automate it more. In any case, it has been fun to play with this. cheers, jason --- End quote --- Can you post the original bin file here? Do you have somewhere a byte with the value "77" in the original binary? |
| jasonRF:
--- Quote from: _Wim_ on May 27, 2023, 06:39:22 pm --- --- Quote from: jasonRF on May 27, 2023, 09:39:36 am ---I can verify that there is at least one Picoscope that doesn't follow this hacking recipe. :-DD I have a 2204a I purchased in 2016. The hardware version is 17. Anyway, increasing byte 0B by 1 and decreasing byte 1B by 1 did not do the trick. I have tried a bunch of other options as well, but so far all of the trials have resulted in a device that the picoscope software does not recognize. Edit:forgot to say that i am trying to turn it into a 2205a, which has identical hardware. The eeprom on my 2204a is definitely different than the one discussed on the sigroc page. For example, B7-D9 and F8-FD are all non-zero. I have of course mucked with some of these bytes as well - especially F8-FD that look less like cal data than some of the other areas. I am very inexperienced when it comes to this kind of stuff, so any suggestions you-all might have would be helpful. For the trial and error approach I have been using so far, it might be time to write a python script to automate it more. In any case, it has been fun to play with this. cheers, jason --- End quote --- Can you post the original bin file here? Do you have somewhere a byte with the value "77" in the original binary? --- End quote --- Hi _Wim_, Good question! I did notice that byte F8 is 77 so is the nominal device type 119, and have played with increasing it by one and then decreasing the neighboring bytes (one at a time, of course) by one, but all to no avail. I have attached a file with the eeprom dump I made using an arduino. I wrote the file to include both hex and dec values because I don't think so well in hex. Edit: and if you want the file in a different format let me know. I used a python script to talk to the arduino and dump this file, so is easy to do it again in a different format. Thanks, jason |
| Navigation |
| Message Index |
| Next page |
| Previous page |