Products > Test Equipment
Siglent SDS1104X-E and SDS1204X-E: Bode plot with a non-Siglent AWG
sp9bsl:
Andy, one more thing: I had to change the frequency exponent from 0 to 1 in pt6900 array. In my case frequencies synthetized by FY6900 were 10 times lower.
awakephd:
sp9, thank you so much for this feedback! I am especially delighted that it works with the SDS1204X, since I do not have a way to test with anything other than my SDS804X.
Can you tell me what firmware your FY6900 is running? I have been aware that there are different versions of the FY6900, and have been debating how to account for all of them. One though I have had is to work up a "setup" routine that could be accessed via telnet, which would lead the user through setting and verifying results, then write the correct pt6900 array out to eeprom.
On the include file - I was trying to set up a system where I could have my private credentials in a file that I could set to be ignored by git - but still show how the credentials file should be set up. My idea was that people would copy the credentials_format.h file over to credentials.h with the proper login credentials. I would welcome a better way to do this - I have scratched my head over it, and done a fair bit of searching on the internet, but this is the best I have come up with so far.
If any others use this code, I will greatly welcome additional feedback, especially for how to configure it for various FY models!
sp9bsl:
Hello Andy,
my FY6900 has firmware v1.3 installed, I bought it over 5 years ago. It is sad that Feeltech doesn't allow firmware upgrade but I knew it at the moment of buy.
This would be great if settings could be changed without removing ESP from FY, reprogram and then put it back. Although, in my case I did it twice and everything works fine now.
Regarding the credentials file, your idea is ok I didn't think this way. I think you should move branch version-2.0 to master and write info about credentials file to readme.md just to save other initial problem with build.
Anyway, thank you for your work, now I can set sweep frequency above the limit of 25MHz which original stuff has. In my case I can work up to 40Mhz, for some reason ESP hangs above this frequency loosing connection with oscilloscope.
awakephd:
Hmm, interesting on the problem above 40MHz. I haven't tried anything going that high - mostly I need up to 10MHz or so. I'm guessing there is some problem with EMD at the higher frequencies. I have thought about going ahead and sending the simple interface board that I built using toner-transfer over to JLCPCB and have some "real" boards printed ... maybe some better shielding on the board would help? (High speed noise is definitely getting into the territory where I don't actually know what I'm doing ...)
Based on what others have said in this and other threads, I think they must have changed the interface slightly between 1.3 and 1.4. If you looked at my comments, you will see that the interface on 1.5 is very inconsistent, and I'm guessing it may be equally but differently inconsistent on 1.3 and earlier as well. :(
Have you tried the "passthrough" mode? If you telnet into the ESP-01 when it is connected to your FY6900, you can type passthrough and it will toggle the passthrough mode. When passthrough is on, you can type into the telnet interface and it will relay it to the serial port, and vice versa - in other words, you can telnet directly into the serial interface. In this mode, if you type WMW123456.12345678 and hit Enter, what does your FY6900 show as the set frequency? And if you then type in RMF, what does it send back?
Based on what you have said, it appears that firmware 1.3 is shifting by a factor of 10 ... but is it catching all of the decimal places? On mine, I can set, e.g., 12345678.12345678 and it will show up as 12,345,678.123456 Hz - six digits after the decimal, up to eight digits before. From what I have read, it sounds like some units need to have the value sent as an integer scaled by 1000, so that sending WMW123456789 becomes 123,456.789 Hz. The "translation table" should be able to take care of anything like that - or at least that was my goal. I would love to get several others with various models testing this, so that I have a better understanding of whether my code will work "universally" (with the right settings in the translation table) or whether there are still some bugs in there.
awakephd:
New developments on the new espBode2.0:
Merged the version-2.0 branch into master
Renamed the repository as espBode2.0 (https://github.com/awakephd/espBode2.0.git)
Extensive documentation including doxygen tags
Added doxygen documentation in docs/html
On edit: off-line conversation with bateau020 helped me see that it is better to leave the repository as espBode and instead use a version tag. As soon as this reaches a point where I am ready to consider it "done for now," I'll generate a release and tag it as v2.0. Thus, the repository remains https://github.com/awakephd/espBode.git
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version