Tektronix THS7xxx Scope Hack/Teardown/Discussion - FW 1.16 found

[walter.aranda]

Dear jal1234, I am using version 3.0.0.0 (sending image), but I have reported freezing issues when recording data while connected to Windows 10 via a USB-RJ45 cable. However, this lag problem has been 'resolved' by using Windows 7 in a Virtualbox. Regarding the license issue you reported, I have read that Tektronix has released the license for domestic use (keycode: WSTRO618650124). I used that keycode, and it hasn't given me any problems related to licenses. Finally, regarding the baud rate, I also haven't encountered any issues, as long as the baud rate settings on both the PC and the oscilloscope match.

[jal1234]

Did you find a way to use anything other than 9600 baud in 3.0?  Some earlier versions had a faster option, but no option that I could find in 3.0.
Thanks,
Jon

[walter.aranda]

Although the recommended setting is 9600 I have not reported any problems when changing the baudrate, (I am using a modified FTDI USB-RJ45 cable, I can pass you my pin if you want), I did a test with the THS7XX HardCopy program which should run at 34800 in its configuration and I have had no problems.
Poniout color description:
| FTDI Cable | Description | New Color Pattern |
|------------|-------------|-------------------|
| 1 Brown    | CTS         | Black             |
| 2 Purple   | DSR         | Brown             |
| 3 Yellow   | RXD         | Red               |
| 4 Red      | GND         | Orange            |
| 5 Black    | GND         | Yellow            |
| 6 Orange   | TXD         | Green             |
| 7 Blue     | DTR         | Blue              |
| 8 Green    | RTS         | Purple            |

New order (tested):
   1        2       3           4           5         6        7          8
Purple | Blue | Brown | Orange | Green | Red | Purple | Black
  RTS    DTR     DSR      GND      TXD       RXD    RTS      CTS

[jal1234]

The Hard Copy program itself
 works at 34,800 baud, but the add-on analytic program doesn't work, so I'm left with the basic Hard Copy functions. So I went to the Tektronix program, which works at 9600. But while 2.x versions had speed options greater than 9600, the only option I see in 3.0 is 9600. The scope is capable, but the program appears not to be.

[mrprecision]

Hello,

I have tried the THS7XX HardCopy program and it worked with my scope. Also the post process with SignalAnalyzer worked fine for me. What are your issues?

Regards
MP

[jal1234]

It tries to connect, fails, and errors out. This is after I've verified the basic Hard Copy program works ok. Are you using 9600 or 34800 baud?
Jon

[mrprecision]

Which tool can not connect? Can you connect with THS7XX HardCopy and the the the scope display via remote? Can you set the scope to factory defaults and only change in the scope to 34800. The tool works only with 34800 and default settings.

[TERRA Operative]

Have you set the port on the PC to the same baud rate?

I'll have to experiment, but I seem to remember having to set that in Windows, maybe...

[jal1234]

It tries to connect, fails, and errors out. This is after I've verified the basic Hard Copy program works ok. Are you using 9600 or 34800 baud?
Jon

Hard Copy connects fine at 34800, and displays the screen. It can also do the quasi real time updates on screen. When I try to use the add on, then it won't connect.

Jon

[jal1234]

Update. Not sure what I did different, but after erroring out once, now Signal Analyzer connects. When it eventually opens, now I get this screen, sorry it's at 90°. When I click OK, I get just a blank screen.

Jon

[walter.aranda]

my friend, I just noticed that I have the same problem (virtualbox Win7 & FTDI cable)  as you when trying to communicate with baud rates higher than 9600. I tested with 19200 and 38400, and indeed, as soon as I change this setting on the scope, the hardware communication stops, and I even need to disconnect the cable to restore communication. I saw in the programming manual, Table 1-2, that it is recommended to leave the default configuration (I'll send an image); however, I don't understand why the options to increase the baud rate exist if this is not possible. Could it be due to some limitation from not using a pure serial cable? Could someone show if this problem occurs with an RS232-RJ45 cable for a PC's serial port? In any case, I can communicate at 9600, so I'm not too concerned about the transfer speed at the moment. Finally, I've noticed that I'm unable to do data logging from the scope to the PC—can you? Could you show me how to do it? If you wish, you can contact me privately. Best regards!

[mrprecision]

It seems that connection do SignalAnalyzer works. The free version is limited to 512 samples, so you need a licence key to use it.

[jal1234]

my friend, I just noticed that I have the same problem (virtualbox Win7 & FTDI cable)  as you when trying to communicate with baud rates higher than 9600. I tested with 19200 and 38400, and indeed, as soon as I change this setting on the scope, the hardware communication stops, and I even need to disconnect the cable to restore communication. I saw in the programming manual, Table 1-2, that it is recommended to leave the default configuration (I'll send an image); however, I don't understand why the options to increase the baud rate exist if this is not possible. Could it be due to some limitation from not using a pure serial cable? Could someone show if this problem occurs with an RS232-RJ45 cable for a PC's serial port? In any case, I can communicate at 9600, so I'm not too concerned about the transfer speed at the moment. Finally, I've noticed that I'm unable to do data logging from the scope to the PC—can you? Could you show me how to do it? If you wish, you can contact me privately. Best regards!

What version of Wavestar are you using? There was no option to change the baud rate in 3.0 that there was in earlier versions. Maybe the fact that Wavestar can't seem to communicate at that speed caused then to delete that option.
I haven't done much with Wavestar yet. I'll look and see what I can do when I get a chance.
Oh, and I'm using a serial cable with my Panasonic CF-19. No USB in the mix.

[jal1234]

It seems that connection do SignalAnalyzer works. The free version is limited to 512 samples, so you need a licence key to use it.

Oh, I see. The documentation to use SignalAnalyzer with the THS7xx is basically non-existant. I wish there was a trial period to try it before the limits kicked in. As it is, I'm hesitant to buy a license without making sure it actually works.
I've managed to get a couple of screens by fluke, I guess, a couple of times. Non-repeatable, and nothing useful was on screen.