Products > Test Equipment
Siglent SDS1104X-E and SDS1204X-E: Bode plot with a non-Siglent AWG
awakephd:
Ah, that makes sense. If / as this revision develops, it would be interesting to see how far we could go to offer generic SCPI control.
awakephd:
Quick update: I have moved forward with the github repo (https://github.com/awakephd/espBode). I went back and forked it from the Hamhackin version, rather than the newer hankst69 - I concluded that it would be easier to proceed down the path I have planned starting from there. I have now updated that code base with a new commit, incorporating the changes that Knutselaar made (and the FY3200 code that his version included) as well as my own updates. Most of what I have done is to add a passthrough command to the telnet interface, and in the process reorganize the logic of the loop() function. Some other minor tweaks and updates as well. At this point, I will try to do a quick-and-dirty implementatiion of the UDP connection needed for the SDS804X and verify that it works. Once that is done, I will create a new development branch and start work on a complete rewrite.
bateau020:
In order to make espbode (or the python script) into a siglent emulating SCPI frontend for any AWG, that respects at least some of the standards, 3 loops/threads/processes are needed:
* 1 that does portmap on UDP (this part is used for broadcasts/discovery and by the HD scopes)
* 1 that does portmap on TCP (this part is used by direct VISA communication, as with the non-HD scopes
* 1 that does the VXI-11 communication (on TCP)The latter should switch to a new port after every LINK_DESTROY, and communicate the new port to the port mappers.
Made this work in the python version, in today's commit. Previously it only ran 1 of those loops at a time, which messed up communication with other SCPI tools.
Haven't really looked yet at how espbode does it.
Knutselaar:
Hi awakephd,
Before my first post I have searched all corners of the internet and found a espbode-master with date 8 december 2020, I think from Github.
I am sorry, I did search today, and I can not repoduce the origin of espbode-master I have used.
I think I have used Youtube:
Text under this video:
************************************
Vastgezet door Tim's Electronics Lab
@TimsElectronicsLab
3 jaar geleden (translation: 3 years ago)
I have created a pull-request on GitHub (https://github.com/sq6sfo/espBode/pull/4) that enables the full FY6900 instruction set. It hasn't been merged yet, so feel free to clone my repo (https://github.com/timkoers/espBode) until it is merged.
************************************
I think that I used one of these links, but they dont exist any more.
I took the espbode-master that worked with the old FY6900.
In my first post reply #112 I explained the path I followed.
Because I also own a FY3224S I took the working driver of the FY6900 and adapt it for my FY3224S.
In the espbode-master attached at reply #113 I made a different solution of the frequency send to the FY6900 than described in post #112.
Maybe it is best, to be complete, to include also the driver for the old version of the FY6900 for those who have the old FY6900.
attatchment: old FY6900 driver:
awakephd:
Thank you, Knutselaar. I think I have generated a repository that does a reasonable job of incorporating the elements that were in the base you used, along with your updates plus mine. I agree that we should have the old FY6900 as an option; thanks for sending it! timkoer's repository is one of those that I looked at, but as best I recall it does not include the FY3200 as an option. At this point I can't determine where that code came from. :(
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version