Much appreciation for the great work
Tested on 7.20. You must use the launcher from the version you are using, if it is not 7.10. Also, I performed the cmd operations manually but they look correct. LAN settings appeared as zeros until 2nd boot.
I am slowly getting familiar with my first 3D printer.
I am slowly getting familiar with my first 3D printer.
Color like... first channel. Hope you will make three else in known colors
)
BTW how your USB converter?
I am slowly getting familiar with my first 3D printer.
Looks very nice.
How do you remove it from the housing, since the spring clips don't look accessible from the outside?
BTW how your USB converter?
It's a USB to UART converter connect to the console port on main PCB.
Yes, I remember.
I mean that you fed it from the PC side in last version.
This version is isolated, so I feed them from both side.
This version is isolated, so I feed them from both side.
Yes, I see. Very interesting. For what 3d isolated channel?
This version is isolated, so I feed them from both side.
Yes, I see. Very interesting. For what 3d isolated channel?
There will be a problem if it's not isolated.
When the USB port has been connected to PC and oscilloscope has been turned off, the oscilloscope will steal power from the STM32 MCU I used as converter.
This version is isolated, so I feed them from both side.
Yes, I see. Very interesting. For what 3d isolated channel?
There will be a problem if it's not isolated.
When the USB port has been connected to PC and oscilloscope has been turned off, the oscilloscope will steal power from the STM32 MCU I used as converter.
You don't need isolation, just a series resistor to limit current drawn by the TXD line.
You can find very thorough review and teardown videos on EEVBlog Youtube channel.
Yes, that's what I'm interested in, to see whether people have managed to unlock the features.
All the info you need is in the thread - reading it all will take a long time. Probably worth it all though for 3K + in "free" features. Maybe start with the last 20/30 pages, it will have the most up to date information. Be sure to understand any changes you are making before you do it to prevent a brick.
Read the thread backwards. You will find the latest hack method around page 60-65
Read the thread backwards. You will find the latest hack method around page 60-65
Page numbers are meaningless as they depend on the user's posts-per-page setting - use post numbers
Read the thread backwards. You will find the latest hack method around page 60-65
Page numbers are meaningless as they depend on the user's posts-per-page setting - use post numbers
@mikeselectricstuff, you are right. Post number 1529 shows the steps and includes the link to download the CAB file. Read from there forward and backward to get some background information about the hack.
Google the apps bundle for the 2000 x to learn about the features. If you read the thread, you'll get extra joy out of it
Are there issues with garbage on LAN with the USB method?
LAN garbage issue will be in any FW when you try start scope app (infiniivisionLauncher.exe) with keys. Any hack method do this actually.
For eliminate this issue you should patch infiniiVisionCore.dll.
Not sure about 2.35, but 2.41 and 2.42 patch methods still in this topic. Think is better to use for search "infiniiVisionCore.dll".
infiniiVisionCore.dll in 2.41 packed in FW as File and in 2.42 packed as Module, so methods and patch addresses is differ.
I patched 2.42 in nk.bin directly, and flashed it to scope via LAN telnet command, but hope that is possible just replace nk.bin in CAB file and flash scope as usually. And ksx file in 2.42 is cab actually, so just rename it.
But anyway LAN strongly recommend for use these patches.
and remember, at scopes with firmware versions below 2.4x the flash will be corrupted after RND(TIME). The scope will not boot anymore and is bricked and needs to be serviced by Keysight. After firmware 2.4x the scope will detect this and repairs itself .... somehow.
Thus with 2.35 or 2.38 there is the constant danger, that your scope (DSOX2000a and DSOX3000a series) won't boot anymore at some day.
Since firmware version 2.4x I haven’t seen a single 2000 or 3000 series scope as a customer return, they seem to be incredibly robust and reliable now. Keysight certainly sorted any problems out and have exceptional customer support.
I’ve seen quite a few new R&S RTB 2000 series ones being returned with issues though, they seem to be having some teething problems. Good warranty support from R&S as well though.