Andrew

Seems like there is more too this. I also struggled to get the GPS comms going.

My GPS created a COM35 port. This was the first available COM port. No connection in Spike.

I changed it to COM2 manually in Device Manager and all was good!

So there is a limitation somewhere …

Cheers

Dan

You could use a simple powered usb hub. Use a portable power pack to plug into the usb hub? BB60C plugged into USB hub too.

Just a thought while I’m searching the Forum 🙂

Jason

Did a quick and dirty test on linux 64 bit intel processor running low latency kernel with the new FTDI drivers.

Getting same results as with previous drivers. If you’re not after absolute accuracy then its fine, if you’re looking for the 1.5dB stated amplitude accuracy then the linux/ARM API is not going to meet this for channel power type measurements anyway. Or anything that is close to the noise floor.

Would like to work with Signal Hound to get it working on the other platforms as well as it does on windows.

Let me know how I can help … it would benefit a large range of industries to use non-windows PCs!

Regards
Jason

Hey Ron

Not yet … had to resort back to Windows.

Cannot replicate the accuracy of the windows version vs ARM/linux. There’s something amiss in the way the FTDI driver caches data.

At the moment, this is on hold …

However, FTDI have just released some new drivers … will test when I get a chance.

Andre, have you guys tested the new FTDI drivers for linux/ARM devices yet?

Regards
Jason

Thanks Andrew

That helps.

Same limitations for the BB60C? … actually, I don’t think you have any ARM implementation for it yet.

Regards
Jason

Thanks Justin.

Is this still the case for higher end ARM processors? Thinking of the Nvidia TX1 SOC which is a high performance SOC.

Ah, thanks Andrew (appreciate the quick response)

I should be able to use ‘send keys’ command /or something similar in the batch file to load the preset then. Forgot about the shortcut.

I’ll give that a go. Thanks Andrew.

[Author]

Posts