| Products > Test Equipment |
| Sniffing the Rigol's internal I2C bus |
| << < (569/899) > >> |
| awh4992:
--- Quote from: tiagobaracho on February 04, 2014, 02:54:39 am --- --- Quote from: np on February 03, 2014, 05:47:28 pm --- Thanks zombie28 for the IDA plugin ;) I comfirm, 0x1C0C7 is the good option for permanent 300Mhz + all options (screenshot) Timebase : 1ns Congratulations for all the team members as done that possible --- End quote --- HI... In which model you were able to install the 300mhz? How did you do to get the NS8H ? when i try rigup license keys.txt 0x1C0C7, windows asks to close.. --- End quote --- rigup spits out a keyfile (saves it to a text file) if you have a memory dump of your scope using the following command: --- Code: ---rigup scan keyfile.txt ds2k_00_sdram.bin --- End code --- Once you have the keyfile, do: --- Code: ---rigup license keyfile.txt 0x1C0C7 --- End code --- and that spits out the license key. I'm pretty sure the stuff spit out by zombie28's firmware via ultra sigma has that keyfile information there too, but ordered differently and whatnot. I didn't bother to figure it out since I have a dump of my scope. - Andy |
| idpromnut:
Confirmed that the NS8H "works" on my scope. I see the options and timebase, but I am not a believer until I can test it ;) |
| tiagobaracho:
do you know if the hardware is able to do 300mhz ? is it only software limited ? |
| tiagobaracho:
I just installed the 300mhz... But it now shows two lines... BANDWIDTH 200M BadnWidth Official Version 300M BadnWidth Official Version Is that all right ? Or do I need to uninstall first to put the NS8H serial ? |
| Mark_O:
--- Quote from: mrflibble on February 04, 2014, 12:26:57 am --- --- Quote from: johna on February 03, 2014, 10:40:09 pm ---...but even RS232/SPI doesn't work as expected. Sometimes it doesn't read correct values even though signal on screen is visible and there are multiple points per bit. --- End quote --- If it really fails to decode that would be bad. So far all the complaint I've read about decoding boiled down to user error. Not that I'm implying (okay yes I am but not the point ;) ) that this is user error, but if Rigol really stuffed up rs232 decoding that would be a bit sad. --- End quote --- As far as RS232 is concerned, initially there was one specific baud rate that failed. That's been fixed. Also, a few bytes when decoded to ASCII didn't map to the proper characters. That was also fixed. So as far as RS232 is concerned, that's been reported to be working properly for quite some time now. Of course, that was on unhacked units. Also, "doesn't work as expected" doesn't necessarily mean the Rigol isn't working properly, though that's often the inference drawn. |
| Navigation |
| Message Index |
| Next page |
| Previous page |