TG44A (Device not found) strange behavior

I’m just posting this here if some one have the that strange behavoir…

Hi from Italy,

would be a bit long mail, but I’m completely stuck with TG44 (bought with SA44 on March 2017 via Foltronics NL).
All worked fine till some months ago. Then, because of other projects, both slept aside on their boxes.
A week ago I’ve restarted Spike (was 3.1.5), discovered that a new software (3.1.12) were on line, so I’ve uninstalled the old one and installed the new one. I’ve loaded, as admin, also the new CDM drivers (2.12). Connected the SA44 & TG44 and only SA44 is seen by Spike soft.
The PC is a HP laptop running WIN10 (no major changes on since last time).
Here the all tests I’ve done.
1) TG as a solid green light, and the 10MHz ref out is working out
2) On SPIKE, FILE folder in the “Connect device” opt only SA is seen
3) Tried TGstandalone soft with no results (GUI with freq appear but “Connect” button seems does nothing) and no signal output from TG
4) On PC, in the device manager, on the “Universal Serial Bus Controllers” tab I found “Serial Converter A” & “Serial Converter B ” (2 lines) I’ve controlled the “Load VCP” box to be unchecked (relates to SG). On Details TAB this is the VID_0403&PID_6010
5) Again on the device manager, on the “Universal Serial Bus Controllers” tab I also found “USB Serial Converter” (no A&B indication). On Details TAB this is the VID_0403&PID_6001 – the VPC is unchecked
6) I’ve run CDM uninstaller and here strange, the uninstaller found and uninstall the 6001 (TG PID) but don’t find the 6010 (SG PID) – even if, in the program LOG file recoded, it claim have removed both.. strange. Strange the LOG and, more, strange the PGM find the TG PID (that doesn’t work with SPIKE) and not the SG PID, that works…
7) Installed again the CDM 2.12. Connected TG via USB and the PC correctly installed the “new” USB device. Then, after, connected the SG, same response by HP-PC
8) Run again SPIKE and same results. Only SG is seen (even the most bottom line indicate the SG connected)
9) These are the USB conditions (with usbview.exe)
a. Below the report for PORT 1 were TG is connected – the USB if seems to be OK – even the TG s/n is recovered
b. And for PORT 2 were SG is connected – the USB if seems to be OK
TG in USB port 1
[Port1] : USB Serial Converter
Is Port User Connectable: yes
Is Port Debug Capable: no
Companion Port Number: 0
Companion Hub Symbolic Link Name:
Protocols Supported:
USB 1.1: yes
USB 2.0: yes
USB 3.0: no
Device Power State: PowerDeviceD0
—===>Device Information<===—
English product name: “SignalHoundTG”
ConnectionStatus:
Current Config Value: 0x01 -> Device Bus Speed: Full (is not SuperSpeed or higher capable)
Device Address: 0x03
Open Pipes: 2
===>Device Descriptor<===
bLength: 0x12
bDescriptorType: 0x01
bcdUSB: 0x0200
bDeviceClass: 0x00 -> This is an Interface Class Defined Device
bDeviceSubClass: 0x00
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x08 = (8) Bytes
idVendor: 0x0403 = Future Technology Devices International Limited
idProduct: 0x6001
bcdDevice: 0x0600
iManufacturer: 0x01
English (United States) “FTDI”
iProduct: 0x02
English (United States) “SignalHoundTG”
iSerialNumber: 0x03
English (United States) “62280109”
bNumConfigurations: 0x01
SG in USB port 2
[Port2] : Dispositivo USB composito
Is Port User Connectable: yes
Is Port Debug Capable: no
Companion Port Number: 0
Companion Hub Symbolic Link Name:
Protocols Supported:
USB 1.1: yes
USB 2.0: yes
USB 3.0: no
Device Power State: PowerDeviceD0
—===>Device Information<===—
English product name: “Signal Hound”
ConnectionStatus:
Current Config Value: 0x01 -> Device Bus Speed: High (is not SuperSpeed or higher capable)
Device Address: 0x02
Open Pipes: 4
===>Device Descriptor<===
bLength: 0x12
bDescriptorType: 0x01
bcdUSB: 0x0200
bDeviceClass: 0x00 -> This is an Interface Class Defined Device
bDeviceSubClass: 0x00
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x40 = (64) Bytes
idVendor: 0x0403 = Future Technology Devices International Limited
idProduct: 0x6010
bcdDevice: 0x0700
iManufacturer: 0x01
English (United States) “FTDI”
iProduct: 0x02
English (United States) “Signal Hound”
iSerialNumber: 0x03
English (United States) “60400509”
bNumConfigurations: 0x01

10) I’ve tried also to uninstall everything and reinstall old Spike soft 3.1.5 I’ve on CDrom with old CDM drivers (2.10 again as Admin) – same results – only SG is seen.
11) With Spike 3.1.12 and CDM 2.12 tried to positive check the VCP boxes – worst – no SG neither TG connect to Spike. So I’ve uninstalled all, and made a fresh Spike 3.1.12 + CDM 2.12 and, again only SG is seen by Spike
12) Last I’ve tried to clean all USB instances recorded onto PC with “USB Oblivion” (is a program that reset on WIN REG all USB infos) of course before I’ve uninstalled Spike (with WIN feature) & CDM (with CDM uninstall) – so, I thought would be a “zero” condition
13) Than I’ve made again a very fresh Spike 3.1.12 and CDM 2.12 install but again only SG is seen

As you could imagine I’ve dried my “fantasy” (SOB)

Is it possible that the TG processor/memory isn’t responding to Spike?
As USB/Iface works (were is memorized the TG S/N I’m able to read?)

Any suggestion?

Many tks – Luigi

Hello Luigi,

Sorry for the difficulty you have experienced.

I can clarify some things. The Spike software does not install/uninstall any drivers for the SA or TG, only the CDM installer/uninstaller. If the Spike software detects and run the SA44, then the driver is installed properly, since the SA shares the same driver with the TG. You cannot connect the TG through the Connect menu in Spike. Spike will only interact with the TG through the Utilities->TG control panel menu or by activating scalar network analysis.

I would try using the Utilities->TG menu to try to control the TG. Additionally, ensure the “Load VCP” checkbox is unchecked for any devices that appear for both the TG and SA in the device manager.

I look forward to your results.

Regards,
Andrew

Dear Andrew,

thanks for answer
VCP etc were OK, and CDM are the USB drivers WIN needs.
So all were as described in the previous mail.

But, you were right.

My memory betrayed me.
I thought TG had to appear on the same line at screen bottom with SA condition.
Or have to appear on “Connect” menu.

I’ve followed yr suggestion to activate “Scalar vector analysis” (just to be dummy proofed I’ve followed YouTube demo) – all works fine (many many tks)
SA and TG works fine.

Just an advice to someone that maybe could experience the same with TG.
Don’t be deceived by “TGstandalone” software.
Here what happen to me and the steps done (but after Andrew suggestions I’was sure that TG were working).

I’ve connected TG first. Than launched the TGstandalone
Some second with the message “connecting device” but don’t expect other msgs.
In a while appear the software GUI.
I’ve decided the freq & amplitude and clicked “connect” GUI button……
And NOTHING HAPPEN
(I was looking the output to a scope)

If happen you too, don’t panic.

By chance, this time, my WIN10, ask for some update – SO I CHANGED THE WINDOW (from TGstandalone to WINupdate)
and “magically” the sine wave appears on the scope screen.

I’ve tested all again.
TG disconnected and TG soft OFF.
TG connected via USB (WIN sounds), I’ve launched the TGstandalone soft. Set the desidered freq/amplit.
And
Instead click the GUI button, I’ve right clicked with mouse another portion of my PC windows screen
(I mean, off the TGstandalone GUI).
Again the sine wave appears.
I don’t know why, but this method works to me more times (instead the expected GUI “connect” button)

Again many many thanks Andrew for the help

ciao Luigi

Hi Luigi,

Thanks for contacting us.

I’m not sure I’m following everything…it actually sounds like both devices are working. Is the TG not producing a signal?

The TG will not show up in the File > Connect menu, that is only used for spec ans. If the TG is connected, its LED should be green. In Spike, the TG is accessed in two ways: through Utilities > Tracking Generator Controls (which will add a subsection to the left-hand control panel). If the TG is not connected, an error dialog will appear that says “Tracking generator not found…” The other way is by entering scalar network analysis mode via Analysis Mode > Scalar Network Analysis. If the tracking generator is not connected, this option will be greyed out.

When the TG standalone app is opened, it will attempt to connect with the device, and a dialog will say “Connecting device…”. If it is not successful, a dialog will be displayed that says “Error connecting device.”

Please note that you cannot have Spike and the TG standalone software running simultaneously, so make sure that you shut one down before using the other.

Are any of these error dialogs appearing? Is the Scalar Network Analysis Mode available or greyed out? Most importantly, is the TG producing a signal? My apologies if I missed that in your email, I didn’t see any information about whether or not it was generating a signal.

I look forward to your response.

Regards,

Roger Rush | Software Engineer
Signal Hound, Inc.

Hi Roger,

again thanks for all support.
Great customer attention!

I’m sorry if I wasn’t clear in Andrew’s answer.

Yes now both SG and TG are working fine and TG is producing the expected signal.
The Spike soft (and SG+TG) are working correctly in Scalar network and in Tracking gen modes.
So all as expected till here.

Now about TG standalone.
As per yesterday mail I do confirm the strange behavior (on one HP/PC running WIN10).
And I do confirm I’m running an app at the time. So Spike is killed when I’m running TG standalone.
And I do confirm also what wrote yesterday.
In order to have a signal out from TG44 with TG standalone software, after launched the soft and waited it connect to TG44, and the GUI selection freq & ampli appears, isn’t enough to hit “Connect” button (right mouse click) to have a signal out from TG I have to move the mouse outside the TG standalone GUI region, example over a clean WIN desktop region and right click. Or, after changed the freq or ampli simply hit enter button.
Maybe I was confused by the “Connect” button – as a button that send values to TG44 after I’ve set it on GUI.
Enter on KBD or right click on other screen zone than GUI works perfect and TG44 generates waves as expected.
Hope this clarify my previous mail.

Again thanks for yr mail, and a big underline to the absolutely quick and responsive customer relationship from Signal Hound.

If you do permit I post on the forum also this our dialogs.
Maybe it could be a help to some other SH customer.

Ciao

Luigi
IK2VJF

[Author]

Posts