Products > Test Equipment

FeelTech FY6600 60MHz 2-Ch VCO Function Arbitrary Waveform Signal Generator

<< < (314/450) > >>

DaveR:
precaud - don't use the Feeltech software to upload the data files, use one of fremen67's versions of the control software, which gets rid of the unneccesary and confusing Chinglish options.

If you start with a csv file, open it in a spreadsheet and copy and paste JUST the 8192 data values into a blank text file with either a .txt or .fy extension.  Use Notepad so that you don't get any hidden formatting information saved in the file.  As bugi says, you've probably got an invisible character in the file which is causing the problem.

Try a couple of mine to make sure your software is working ok.

 

precaud:
Thanks for chiming in, cybermaus.


--- Quote from: cybermaus on August 05, 2018, 06:19:32 am ---I also manually edited one, they are not CSV, they are normal TXT files!
--- End quote ---

For those who may not know, CSV = "Comma Separated Values". It's just a list of data points, separated by a comma or other commonly-used separator. If there's only one data point per line, then CRLF substitutes for the comma.
Excel .CSV files are a little different, they have a few lines of descriptive header before the data points.
But the main feature is, they are simple text files of ASCII-encoded decimal values between +1.0 and -1.0
That is what my software generates. (Actually, its HP's software from the 90's...)
From the FY6x00 software POV, there is no difference between .CSV and .TXT or .SUX, it doesn't care what the file type designator is, as long as the data format is correct, it will read it.


--- Quote ---Did you try making one with the tool?
--- End quote ---

No. Once I saw that the file format is the usual list of data points, I saw no point (pun intended!).


--- Quote ---This *.FYC file is next used to calculate the actual points in the waveform numerically, which is in the *.FY file. The latter is just a list of 8192 floating point values between -1 and 1
I attached 1 set as example (4 Sine waveforms added together)
--- End quote ---

Thanks. My files are identical to yours, except a) yours has a blank line at the end (where point 8193 would be is just CRLF), and b) mine uses a small-case "e" for the engineering notation. I wonder if that's making a difference. The blank line isn't likely causing the problem, because the software reads the file in fine, the error comes when loading it into the waveform buffer.

I created a 4096-point version. It reads it in and loads it into the edit buffer. While doing so, it expands it to 8192 points by duplicating every data point. I sent that file to the 6800 and it plays back fine (if duplicated data points is what you want...)

I then edited off one data point from the 8192-point version. The software reads it in, counts the # of data points correctly (8191), and displays the waveform correctly in the graphics box to the right. Clicking "Load Data" loads the waveform into the edit buffer but imposes an ascending ramp modulation on the data and multiplies it way out of bounds. Wierd.


--- Quote ---Edit: I checked: all values are suffixed by x20 x20 x0d x0a
meaning <space> <space> <cr> <lf>
The last line is padded with an extra empty line x0d x0a
--- End quote ---

Thanks. All mine are CRLF terminated too. No empty line at the end, though.

I'll try making the "e" an upper case and see what happens.

But this has raised two larger questions.
First: I bought this thing mostly for its arb capability. As I wrote in a thread started a couple months ago, I wanted to see if higher-resolution (14-bit) arb could make up for the lack of a real output filter and reduce the clock noise that is created when inevitable waveform delay shifts the samples and puts the stair-step at the center of the sampled point in the FFT. Some here opined that it would. My hunch was (and still is), no, it won't, there's no substitute for proper output filtering. This was a cheap way of testing it out, so I went for it.

Second: Only now have I learned that all waveform files have to be 8192 points. Can I live with that? I already know the answer: No. I need the flexibility of point-by-point waveform playback of any number of data points. Not all digitizers use power-of-two-based time record lengths.

So I'll try changing the "e"s to "E"s. But even if/when the data format issue is solved, it appears this unit is not going to do what I want.

Philipp F.:
Hey,
I am a somewhat inexperienced electronics hobbyist and I'm in the market for a signal generator for testing various things and circuits because my cheap Chinese 3 knob signal generator kit isn't cutting it anymore.

I really want to get the FY6800 because of all its functions (the VCO and sweep stuff really interests me) and it costs about right what I can spend, but all this talk is kinda deterring me...

Is it worth getting or do I risk ending up with a 115€ brick?
I can get it shipped from a Germany warehouse, so I could at least hope for a basic 2 year warranty (and the seller also advertises 2 year warranty).

DaveR:
precaud - I've just spotted the file you posted, and it loads into fremen67's 0.7 version of the control software, so it should upload to your 6800 ok (although what it will do to the 6800 when you run it is anyone's guess  :)).

Regards,
Dave

precaud:
@Phillip F., you can ignore all this talk, we're just getting into the weeds on some details.

So I changed the "e"s to "E"s, put a blank line at the end of the 8192-point file, and just for the halibut, renamed the file with a .FY extension. The software reads it in fine. Clicking "Load Data" generates the same error as before, "Run-time error 6 : Overflow".

There are no data points in the file larger than 1.0 or smaller than -1.0 . In fact, there are no data point equal to those values, either. The data conforms to all the rules. So the raw data is not the cause of the overflow.

This is the arb waveform I use more than any other. If it won't work with this, there's no point to me going further with it.

I've attached the file (with extension .ASC) if you're interested to see it.

DaveR - I just saw your post. That file is 4096 data points. It loads into the 6800 fine for me too, except every point is duplicated. Try the attached one and see if that works. Meanwhile, I'll look for fremen67's 0.7 version and try it.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod