Activity for Thorsten Wagner
-
Thorsten Wagner posted a comment on discussion SPM electronics
Hi Tugce. If you want the tip extend while feedback is on and the coarse approach is moving continously, it might be simple. Just setting the set point of the feedback high enough will extend the z-piezo to its limit. You can check its position in a python script (see Percy's posting) with gxsm.rtquery ("z"). In the moment, contact is achived, the feedback will retract the tip. So you just have to make a while loop for setting for example the "motor" output (out7) to 5V (or whatever you need) as...
-
Hi Tugce. If you want the tip extend while feedback is on and the coarse approach is moving continously, it might be simple. Just setting the set point of the feedback high enough will extend the z-piezo to its limit. You can check its position in a python script (see Percy's posting) with gxsm.rtquery ("z"). In the moment, contact is achived, the feedback will retract the tip. So you just have to make a while loop for setting for example the "motor" output (out7) to 5V (or whatever you need) as...
-
I am stil confused. Let's resume your plans. You want to have an auto approach as follows: The piezo is fully extended and feedback is on, a course motion controlled by pulses should move forward until the feedback starts to retract the piezo and its z voltags is below a given threshold. Is this so far correct? As Percy suggested, the python interface would be most suitable for this. You do not need a extra input for the z-position as this is directly accessible. You just have to think about how...
-
What do you mean with IN3 does not output? It is an input you can use for the z-feedback regulator. All 8 BNC on the right side of the controller (FB-i, FB-2, FB-3, FB-4, 5, 6, 7, 8) are inputs! In the GXSM gui they should be named In0: I-Tunnel, In1, .... In7. To do so, please make sure that the gain (see section source - see Fig. 23.23 in the gxsm3 manual: https://github.com/pyzahl/Gxsm3/blob/master/debian/Gxsm3-main.pdf) for this respective input is set at least to 0.5. The feedback output is...
-
Hi. What exactly happens when the scan is interupted. I can not see in you screenshots. It gxsm3 crashing or does the controller stopp unindently the scanning (you can check by conneting a scope to the outputs of the controller)? A few notes: I see that you are using an elder ventiotec distribution using an elder ubuntu 22.04 and "only" gxsm3-3.53. You might want to update to a newer ubuntu 24.04 which will enable you to use gxssm3-3.54 available on launchpad. There had been a few - less critical...
-
Hi Tugce. The VB output is usually used for the bias voltage so that it is a DC voltage. I do not see how you want to use this for triggering a coarse step. This is certainly the reason why you see only for this channel a DC voltage in the scope. Just to be on the same level: a) You are using an MK2 or MK3 controller. b) You need a standard trigger signal (0V -> 5V) after a z-ramp is finished and while the piezo is still retracted. c) Did you look for the SRanger-DSP-Mover window? Or are you using...
-
How do you connect the coarse driver to GXSM? Are you using the M-output and the arbitrary function generator or do you connect to the GPIOs? The GPIO switch in coarse motion mode just between modes, but the do not provide single pulses. Therefore, you might have to use the arbitrary function generator! Locks that your piezo controller works on the rising edge .... Did you try with a function generator to test your matlab script? What timing parameters do you need for your course driver? What is...
-
I was able to reproduce the problem on Ubuntu 24.04 LTS and with the cgt_c5500_4.4.1 tools. If you just use sudo ./ti_cgt_c5500_4.3.7_setup_linux_x86.bin the terminal hangs and nothing happens. Please try sudo ./ti_cgt_c5500_4.3.7_setup_linux_x86.bin --mode console This should install the cgt into /opt/ti/... Please check the exact path, because you will have to set in in the Makefile. Use an editor like gedit to adapt the file <your gxsm="" source="" foler="">/plug-ins/hard/MK2-A810_spmcontrol/Makefile</your>...
-
Are you using the internal PLL? Remember GXSM can use up to four ínput channel connected with a fuzzy logic as input for the z-feedback. The patch rack (script) allows you to root certain signal. The rest might be just a proper scaling factor to convert counts (internal number) or volt (external input) <-> absolute frequency. Thorsten :-)
-
It is quite a while ago that I needed the CGT to be installed. Usually I would suggest a procesure like this: cd < folder where you downloaded the binary > chmod 755 ti_cgt_c5500_4.3.7_setup_linux_x86.bin sudo ./ti_cgt_c5500_4.3.7_setup_linux_x86.bin For sure a double click in the file browser will not work, but you may be able to make the file executable with a right-click and some property menu. The CGT is quite old - the release of the specific binary was 2010. There is a chance that there is...
-
So you want to modifiy the code on the controller? For MK2 it is in https://github.com/pyzahl/Gxsm3/tree/master/plug-ins/hard/MK2-A810_spmcontrol For MK3 it is in https://github.com/pyzahl/Gxsm3/tree/master/plug-ins/hard/MK3-A810_spmcontrol Look for the file FB_spm_autoapproach.c in there. In addition, you will need the respective compiler from Texas instruments. This is what I found in a README of the MK2: ** install the TI "cgtools-c5500" in /opt/TI/cgtools-c55 -- tested with: TMS320C55x Code Generation...
-
I am not sure what you mean. The mover window is coded in C. You are able to control quite a lot of widget from python, but you can not change the behaviou of them totally. gxsm.action emulates the interaction of the user with the GUI. Not all widget have a python connection yet. Just hold the mouse over the widget which you want to control remotely. If a tooltip appears it will tell you the name of the widget used in gxsm.action. I guess your questions aim that you want to know if a certain button...
-
What do you mean be logic? As for the mover control, the python code will use the feedback loop as signal. If the piezo is extended above a certain threshold value, the tip is retracted by setting the gain parameter with the opposite sign. While the piezo is retracted, you can trigger your coarse step. Here you have all the freedom you need. The the orginal feedback parameter are set and the tip starts approaching. For ultra-high vacuum applications, this stepwise appraoch is the standard procedure....
-
Hi. The waveforms are generated in GXSM and then transfered as table to the DSP. Please have a look at <gxsm3-source>/plug-ins/hard/sranger_mk2_hwi_mover.C</gxsm3-source> You may also be able to code your own coarse approach in python using usb communication to control the coarse motion. Thorsten :-)
-
The mover can produce also wave forms used by stepper motors but you need the additional H-brigde (electronics) for that. If you have a motor controller with TTL input, you might use the pulse generated on a analog out or on the GPIOs. If just pulses are used you have to define the moving direction "manually". So what do you have in mind? Thorsten :-)
-
Gxsm2? Is there any special reason to run such old version? Definetelly, you will have to downgrade the DSP program for that. We might have used at that time still the CVS instead of subversion and later github ... Thorsten :-)
-
The firmware files are stored on github (and older on sourceforge), so that you can go back any time you need. Usually, the version increases very slowly - only after changing the "software" interface between GXSM and hardware. In GXSM you can change also the visibility of certain tabs. It may happen that you had enabled it in your old installation. Just click on the swiss army knife. Then a line with a radio button on each tab should appear where you can enable or disable the tab. Another possibilty...
-
The firmware files are stored on github (and older on sourceforge), so that you can go back any time you need. Usually, the version increases very slowly - only after changing the "software" interface between GXSM and hardware. In GXSM you can change also the visibility of certain tabs. It may happen that you had enabled it in your old installation. Just click on the swiss army knife. Then a line with a radio button on each tab should appear where you can enable or disable the tab. Another possibilty...
-
backport of recent changes in MK23 related to dkms.conf: removed automatic generatioin of initrd
-
updated README to include hints about secure boot
-
Hi. I can reproduce your problem on my Ubuntu 24.04 with same kernel. The problem is related to secureboot which is enabled in your bios - maybe because you are using a parallel installation of windows. Please have a look at this discussion: https://sourceforge.net/p/gxsm/discussion/297458/thread/3f0faafe/?page=2&limit=25#8095 Please install mokutil and shim-signed sudo apt install mokutil shim-signed Typing sudo mokutil --sb-state should indicate in your case that secureboot is enabled. In this...
-
Do you have the "universe" repository enabled? I guess that you do use Ubuntu, don't you? Just try: sudo add-apt-repository universe sudo apt update sudo apt install ibnetcdf-cxx-legacy-dev Thorsten :-)
-
Hi. Did you also install all dependencies on the second system? Please check for: libnetcdf-dev, libnetcdf-c++4-dev, libnetcdf-cxx-legacy-dev You can get a list of all installed packages via dpkg-query -l If you type dpkg-query -l | grep libnetcdf the output list should be restricked to all packages containing libnetcdf in the name! Thorsten :-)
-
Hi Amit. Thanks for the description how to install gxsm on a WSL. About 10a - the code on svn in not maintained any more. Please use option 10b to download from github. I did not have time to test, but it should work also with the standard ubuntu coming with WSL. Thorsten :-) Install wsl (Follow: https://learn.microsoft.com/en-us/windows/wsl/setup/environment?source=recommendations): wsl --install -> Start > Turn windows features on or off > Turn on "Windows Subsystem for Linux" and "Virtual Machine...
-
Hi Amit. You got GXSM running in a Windows Subsystem for Linux (WSL). Cool. If you do not mind, please post a step by step manual how to do this. I tried myself with Ubuntu on WSL but did not succeed with the hardware support which needs to be compiled into the kernel. About your problem with the pyrremote console? Which GXSM did you install? 3 or 4? Did you compile it or did you take precompiled binaries? Maybe even the flatpak? It is important that python is installed properly during the compilation...
-
Maybe this older documentations helps you: https://gxsm.sourceforge.net/?content=gxsmdocusection§ion=Documentation:%20Manual Thorsten :-)
-
Right now, there is not such file, but you may use doxygen to create it. Thorsten :-)
-
I guess one image is scanned top to bottom and the other vice versa, aren't they? Your scan piezo seems to suffer from a huge creep. Is it a commercial system (with sensors for the position)? If it is self-made, you may have to think about a new supplier for your piezos. What kind of piezo amplifier do you use? If you are using an "convential" voltage amplifiert (+/-10V -> +/- 200 V) you may want to change to a setup which ensures a certain charge on the piezo electrodes. Please check the keyword...
-
The source code for the GUI is in Gxsm3/plug-ins/hard /sranger_mk2_hwi_mover.cpp (for GXSM3). You will find in the same folder more specific files acting as "backend". On this low hardware level there are (partly) different files for mk2 and mk3 boards. The mk2 does not have the PLL/PAC option ... Thorsten :-)
-
It looks like that you missed to install some dependencies - here libpng. Aussumung that you want to install GXSM3 (not GXSM4), have a look into the folder https://github.com/pyzahl/Gxsm3/tree/master/debian There you will find for most Ubuntu LTS (long term support) a control-file. Please make sure that you have installed all packages mentioned in Bulid-Depends and Depends. Your missing libpng is not listed hre, but another package depends on it. Using apt or apt-get or synaptic for the installation...
-
Hi. GXSM is programmed in C/C++, python, ... You can use any IDE to edit the code. The toolchain used is based on the autotools (autogen.sh, make, ...) GXSSM4 uses maeson/ninja instead. You can find a compiled manual here: https://gxsm.sourceforge.net/Gxsm3-main.pdf Thorsten :-)
-
Konichi-wa. The main window is somewhat called "SPM DSP mover controll". You may access it from the gxsm3 application icon by clicking on it. Then you should get a list of all open windows. If you never have opened it, you may access it from the gxsm3-menue (main window)->views->... Be aware that you need a MK2/3 controller to be installed and configured in gxsm3. If the MK2/3 controller is not set in the preferences the hardware related plug-ins are not loaded. Thorsten :-)
-
backport for Ubuntu 22.04
-
Dear Takayuki-san. Do you get any warning about a firmware mismatch when starting gxsm? You certainly have installed the latest gxsm3 but what about the controller? Is it up to date? You can do a self check of the controller with the windows tools supplied from softdb. Did you ever have voltages larger than 10 V at one of the inputs? In this case, you have a chance that the DSP or FPGA are damaged ... Thorsten :-)
-
Hi Takayuki-san. Did it start once until you set up the hardware? Usually after a kernel update, you should run once sudo dpkg-reconfigure sranger-modules-mk23-dkms to prepare the kernel module for the freshly installed kernel. If you start gxsm3 with the prefix sudo it runs from another configuration, most possible without hardware support. You can also try gxsm3 --hardware=no which should start gxsm3 but the hwi (hardware interface) is not loaded. You can check whether the kernel module is loaded...
-
Hi Yoichi. Please check if you have installed all dependencies (includind build-debendencies) listed in the file https://github.com/pyzahl/Gxsm3/blob/master/debian/control_ubuntu22.04 If you have to install additional libraries, do not forget to "reconfigure" your makefile. In GXSM3 ./autogen.sh should do the job. Thorsten :-)
-
I hope you are not talking about the README in the root folder. Please have a look at the more helpful README.md in the subfolder of the MK2/3: https://svn.code.sf.net/p/sranger/svn/trunk/SRanger/SR_MK2_MK3Pro/kernel-module/src/README.md Thorsten :-)
-
Hi Shiang-Bin Chiu. Which instructions did you follow? If you have installed from launchpad - see posting above - also the sranger packages should be installed. Please check by running sudo lsmod | grep usb If not you have do decide whether you use dkms or you do everything manually. On what linux derivate do you try to install GXSM? The launchpad works mostly for Ubuntu - up to the most recent one. Thorsten :-)
-
HI Mujeeb. I guess the problem is that you did not enable the respective repositories after installing your Ubuntu. Please run in a terminal the following commands: sudo add-apt-repository universe sudo add-apt-repository multiverse sudo add-apt-repository restricted sudo add-apt-repository ppa:totto/gxsm sudo apt update sudo apt install gxsm3 Thorsten :-)
-
Update for ubuntu24.04
-
No, it is none of my boards! Thorsten :-)
-
Hi Wei Lu. Do you know about any special adaption of your GXSM/controller version? Anyway, you have to make sure that your GXSM3 version matches the firmware on the controller. Having your system installed originally 2016 could cause some problem now runing the most recent GXSM3, so that you have to update the firmware. Anyway, I have in mind that the DSP code is very stable for years. Assuming, the hardware wiring is stil okay, you just have to deal with proper settings for your SPM only in the...
-
If you set up your system, please update the Ubuntu OS, too. Ubuntu 2016 is not receiving updates since 2021 unless you pay Cononical for it. If you keep it with Ubuntu 2016, please check that you have all dependencies (for build and binary) installed properly - see https://github.com/pyzahl/Gxsm3/blob/master/debian/control_ubuntu16.04 For later Ubuntu versions, I added also "intltool" as build dependency. Thorsten :-)
-
Hi Wei Lu. Did you check out the latest GXSM3 code via git or svn. You should use the github repository: git clone https://github.com/pyzahl/Gxsm3 gxsm3-git Was there any warning running the autogen.sh skript? You may want to post the output from the script. If the computer was freshly installed, library might be missing. Thorsten :-)
-
Hi Roman, hi Ronja. In far as I remember, the retract during approach is done by setting a negative feedback gain ci, cp is set to zero. Have have a look for details in <gxsm-source>/plug-ins/hard/MK3-A810_spmcontrol/FB_spm_autoapproach.c line 198ff. The parameter is accessible via the fb_spm_dataexchange (so you can set it also in a python script) and should be a parameter of the mover control - see 318 of the GXSM manual. I can not check it without having a controller (right not at home). </gxsm-source>...
-
Hi Ronja. Ist this Prof. Möller's design? To use his microscopes, the cycloidic wave forms had been implement. These only use half the piezo range to that you do not crash. If I remember correctly, the setup would need an analog adding of z-scan (fine approach) and z-offset (cycloide with base voltage 0). Thorsten :-)
-
I have in mind that there is not command for that but you can set the feedback parameters ci and cp to 0. Thorsten :-)
-
Hi Daniel. Welcome. The DSP code is written in a C dialect. You will need a compiler supplied by Texas instruments. To access the DSP (setting parameter, reading values) you can do via GXSM, python, ... If you install the windows driver supplied by softdb, you have also the PDF of the circuits on your drive. Thorsten :-)
-
Hi Huey. You definetelly have to provide more details about your setup and your settings so that one may be able to reproduce your problem. So far just: If possible check by eye how far your are away with your tip from the sample. You course motion might work assymmetrically. The approach steps are smaller than the one to retract the tip. Also keep in mind that slip-stick-motion devices (Besocke, Beetle, ...) might just stuck at certain positions (dust particles, roughness of the surfaces, ...)....
-
So please try cd /usr/src/linux-headers-5.15.0-84-generic make oldconfig && make prepare You may have to run this commands as root (run sudo -i). You may also check your installed and running kernel via uname -a If it is different from version 5.15.0-84-generic, then you do not have the right kernel sources installed. Thorsten :-) P.S.: Sometimes I had similar problems. It may have been related to faulty kernel headers ... This is a original Ubuntu. You did not install the gxsm distro, did you? The...
-
Hi Bugrahan. Sorry there was a typo. It is: sudo apt install sranger-modules-mk23-dkms You can run this comment in every folder. So install is here an option to apt. There is another command "install" which will required some source code in the same folder. That's why you got an error message. Thorsten :-)
-
Hi Bugrahan. You going the hard way: Compiling everything on your own! I guess that you have installed the right kernel-headers not the kernel-sources. I have in mind that it might require to run one in the kernel-header-folder make mrproper to generate the configuration file of the kernel in use. The easy way: sudo add-apt-repository ppa:totto/gxsm sudo apt update sudo install sranger-modules-mk23-dkms Thorsten :-)
-
Hi Bugrahan. If you have installed packages, did you do via dpkg (after manually downloading) or apt/apt-get/synaptic/...? I have in mind that dpkg does not fulfil the dependencies. Therefore, I definetelly advice to use a high level package manager. To solve your problem, sudo apt install build-essential might be enough. Thorsten :-)
-
HI Bugrahan. Which packages did you install? If you have installed GXSM3 as binary, you may have unmet dependencies to install the kernel modules or GXSM3. Please make sure that you have installed all packages mentioned in this file: https://github.com/pyzahl/Gxsm3/blob/master/debian/control_ubuntu22.04 Installing the kernel modules will require linux-headers-generic and dkms. Thorsten :-)
-
Hi Nick. The output should be correct. The PanView will show with the small rectangle that the scan region is moved; this is given be xo and yo. The large rectangle indicates the scan areaa. So the tip position just represents xs and ys. In genreal, the behaviour of PanView will depend whether digital or analog offset adding is set. Thorsten :-)
-
Hi Barnet. If you have the digital offset adding enabled, you can set in the main window an respective offset. Say, you scan should be 100 nm x 100 nm, then set 50 nm for x and y offset. Please check with an oszilloscope for the proper sign of the offset. If this finally works for you, you can think of setting up a python script which automatically sets the offset whenever the scan size is changed. Please keep in mind that you can also alter the offset by placing objects into the image/scan window....
-
Hi Wenxuan. Did you have (eight!) BNC cables connected between adc0-dac0, adc1-dac1, ... adc7-dac7? (input to respective output) If not, the test produces some arbitrary values. By the way, the programm checks just the A810 addon board responsible for the input and output signals. It will also ask youi to connect the "bridge" between the GPIO, but please ignore that part of the test! If doing wrong, you can break the board. To test your MK3Pro (and therefore the DSP, memory, ...) you have to run...
-
Hi Wenxuan. The output site is completelly disconnected? This is not visible in the picture which you send. I have in mind that all BNC connectors use the same ground. You can also run srx_analog810_selftest (on windows). It should indicate you, if you have an offset. Thorsten :-)
-
Hi Nick, hi Jose. I have in mind that the rbt file is also flashed using srx_analog810_selftest. Please also run it once with your system. The communication via windows is okay? If you continue to have memory problems, you should contact softdb. There might be a hardware issue. Thorsten :-) P.S.: You are running linux natively on a PC not within a virtual box, aren't you?
-
Hi Wenxuan. You low frequency signal might be 60 Hz related to your power line. This hints that you have a problem with some ground loops. Anyway, do not have the (used) inputs "open"=not connected, because in this way they may pick up excactly some stray fields. The card may have a small, constant offset. For the older STD/SP2 boards we compensated for that digitally subtracting the respective value. For the newer MK2/3-A810 this was in general not necessary. The offset might disappear, if you "close"...
-
Hi Wenxuan. Yes reflashing! Do not forget to power off and on the board afterwards so that the firmware is loaded into the memory. Thorsten :-)
-
Hi Wnxuan. Please make sure that you have the most recent firmware. Percy submitted some updated recently. The new code should be also available as binary from launchpad.net. Thorsten :-)
-
If it is a constant offset during ramping of z, this is capacitive crosstalk. You may have to shielt your tunneling wire better. Thorsten :-)
-
Hi Chen. After flashing a new firmware, you will have to run another tool shipped with the PLL package by softdb: https://www.softdb.com/_files/_dsp_division/SoftdB_SPM_PLL_1_84b.exe It is calles SPMReset. If the message appears: "You card is not in the list", please also contact softdb. Please do not forget to power off and on the controller. The red indicator after the DDR2 test might be an issue to talk about with softdb. Thorsten :-)
-
Hi Jose, hi Nick. Test 2.4 shows an expected behaviour: The input signal is always zero. You may set the parameter to a higher value to have more "resolution"! That might explain the up/down behaviour of the the other two tests. As you have not real feedback, the smallest difference might um up (with ci not being 0) so a large variation of z. Same is true for cp. You also might try smaller values of cp and ci, say 0.001. I guesst you are using ADC1 intently. Be aware about the numbering. ADC0 is...
-
Hi Chang. To avoid grounding loops and, therefore, the pick up of noise, it is usually recommended to wire all grounds star-like. The anchor point can be either your controller or your SPM. Usually, I would suggest to have the chamber connected with a thick wire to the building ground. Definetelly, try to avoid ground connection between instruments. They can be connected obviously via the signal cables (if not having differential inputs) but also via the power cables. As you already noted: The controller...
-
Update to link to git-folder
-
Hi Avijit. Indeed, the ...A16.out is for another add-on board which is not used for the SPM controllers. Using the FB_spmcontrol_MK2_A810.out was correct. Thorsten :-)
-
Hi Avijit. You GXSM is more recent than the firmware on your controller. So please update the controller firmware. To do so, you will need the software tools from softdb for windows: https://www.softdb.com/_files/_dsp_division/SR3_Applications_Installer_V212.zip You can use for example the SRx_A810_selftest. The firmware for your GXSM is found in /usr/share/gxsm3/dsp-firmware/SR-MK2 - You have try to run an MK2 controller, don't you? Not availabe as binary package is even a later version of gxsm...
-
Dear Chang. Possibly, there was a kernel update in meantime. Please run sudo dpkg-reconfigure sranger-modules-mk23-dkms in a terminal and then check via: sudo lsmod | grep usb wether the kernel modul is loaded. Thorsten :-)
-
Dear Chang. Avoid +/-12 V at the inputs under all circumstances. You might just use a simple voltage devider (pair of resistors) to adapt the voltage. The windows tools come also with some circuit schematics as documentation but unfortunatelly not for the A810. So better assume that there is no protective circuit. Thorsten :-)
-
Hi Ald. You are right: If digital offset adding is selected, only the scan outputs X(S), Y(S) and Z(S) are used. If you activate analog offset adding in the preferences (AND DSP control window), you have separate signals for scanning and offset (scan position). In this case, you will need an external amplifier with two input channels and different gains for each channel X, Y, and Z. So digital offset adding will work for all systems, analog offset adding just for dedicated systems. Thorsten :-)
-
Dear Ald. Please have a look at https://github.com/pyzahl/Gxsm-Scripting/blob/main/script_auto_app.py If you can control you hardware via python it should not be a problem. Anyway, you may thing to trigger directly the MSCU or via Arduino. GXSM can also produce TTL pulses. Thorsten :-)
-
I hope the "woops" means that you found out that you can drag and drop the tabs from one window to the other. This is quite handy if you want to do e.g. spectroscopy while taking topographic images, because you can see both tabs. Thorsten :-)
-
Hi Ald. Not sure how you try to emulate the STM tunneling current. Simply speaking: The input is not current sensing but a +/-10V input. So you will have to add a current to voltage converter to operate an STM. For simple testing, you can conntect the bias voltage output to the input 0. You also have to set the conversion gain in the preferences. Usual values are 1 V / 1 nA. Then set the bias voltage to 1 V. The PanView or the HUD display should give you now a reading of 1 nA. You can then adjust...
-
Hi Ald. Did you turn on the feedback on the "Advance" tab of the DSP-dialog (where you set the bias)? After powering the DSP the feedback is off by default. You may have to short the input to read (almost) zero. If the input is open/not connected to anything, some charges accumulate and produce this potential. Thorsten :-)
-
Hi Percy. Your hint about Wayland was right. Just citing from the Ubuntu webpage: We also see significant improvements when using AMD and NVIDIA graphics cards as well as runtime power management for NVIDIA GPUs. Wayland is now the default display server for most systems, whilst X11 remains the default for those with NVIDIA GPUs. So after editing /etc/gdm3/custom.conf by setting WaylandEnable=false it works out of the box. Just a note: meson did not check for libglm but some code required it. Thorsten...
-
Hi Percy. I did try on an old PC with NVIDIA chip and it worked. So I guess that you make somewhere a call to the NVIDIA library in the main program? It would be a pitty to limit GXSM just on NVIDIA GPUs! Thorsten :-)
-
Hi Percy. No, it is on a native system - not sandbox, no flatpak. It is also not crashing. Only the main window appears, no others are created. The widget in the window response to mouseover and clicking but no callback is emitted so that in principle the window is not functional. Even the bar on the top with the window controls does not have any function: You can not close the window using the "x". You can even not move the window by clicking, holding and moving. To kill the window, you need to...
-
Hi Thorsten, I updated my Debian Testing. Now Gnome 43.0 I had to add libz ("lz" called in meson files) to plugins to complete the ninja -- some how libz symbols were missing in two plugins. Will check all and then push to git next. Then all looks fine and it start up ok and works fine as far I can tell. Also the pull down scroll menu/lists now work! Just a quick check so far... best regards -Percy
-
Hi Percy. I am still not able to run GXSM4. I removed all plugins but that just removes the this warning Gtk-CRITICAL **: 21:45:27.620: gtk_grid_attach: assertion '_gtk_widget_get_parent (child) == NULL' failed Calling gxsm4 --disable-plugins results in a segmentation fault. I guess as plugins_reload is not called some pointers are missing to be set. While enabling debug messages, the last displayed is that the splash screen will be closed, but not splash screen is visible at all. Thorsten :-)
-
Hi Timo. In principle the cycloidic wave forms have been generated to do the job, but that would require some external offset of the signals. If the exact limit is not important, I would suggest to use a python script. As this is not totally realtime on DSP it may need a slow fine approach. Have a look at this script https://github.com/pyzahl/Gxsm-Scripting/blob/main/script_auto_app.py Changes on DSP level would imply that you maintain your own firmware. @Percy: Is is maybe usefull to have a user...
-
Hi Percy. The problem occurs in both cases - compiling via meson compile meson install or while making a flatpak package, although the compiler output looks a little bit different. I first had some problems with the flatpak and how to include numpy but finally I solved it. The problem was indeed related to the meson.build file. But the python includes should not affect the GUI behaviour. Anyway, I also used the coded labeled with v4.0.0-alpha.0 from May, 12th. I had in mind that around the workshop...
-
Hi Thorsten, Does that also happen when you install and run it locally, native? (No flatpak) BTW: -- unrelated -- I forward ported recent Gxsm3 patches and new features to Gxsm4 to maintain sync -- I hope I caught it all... best regards -Percy
-
Hi Thorsten, Hmm, I have not used or worked on Gxsm4 in a while. No idea. Did not touched it either. Will check... / try update my Gtk4 local system. (So far unchanged and working OK here on Debian Testing as of several month "old") What Gtk4 version are we having there? best regards -Percy
-
Hi Percy. Ubuntu 22.04 comes with GTK 4.6.6+ds-0ubuntu1 and GNOME 42.4-0ubuntu1. Both are of course adapted by Ubuntu ... Thorsten :-)
-
Hi Percy, hi everyone. I just want to share some problem with GXSM4 (on Ubuntu 22.04) and ask if you can confirm them on other systems: After obtaining the recent code from github and compiling&installing via meson or via flatpak I can open gxsm4 from the command line but it opens just the main window - now slash screen, no extra dialogs like channel selector, ... The main window is only responsive in the such way that the widgets show a mouse over ("being activated") and then a tooltip. There is...
-
Hi Timo. Yes it is about right. Please have a look at the package control file here: https://github.com/pyzahl/Gxsm3/blob/master/debian/control_ubuntu22.04 The files which you mention are used for the build process (upon some more). If you just install the binary, these "build-depends" are not installed automatically. Thorsten :-)
-
Then try $ lsmod | grep usb and check if the kernel module is loaded. lsmod will list all loaded kernel modules. | redirects the output to grep, which then will just print all lines containing usb. Thorsten :-)
-
Then try $ lsmod | grep usb and check if the kernel module is loaded. lsmod will list all loaded kernel modules. | redirects the output to grep, which then will just print all lines containing usb. Thorsten :-)
-
Hi Timo. It will also work $ sudo modprobe usb-sranger-mk23 after installing the kernel module from the PPA. Modprobe has a certain search path for the modules, but it will not look into your private home directory. Therefore, if you do it from the svn repository, you have to point to point to the local file via ./ Thorsten :-)
-
Hi Divya. If you did a fresh installation, please check the settings for the gain (in A/V) in the preferences. I guess that you already changed the fuzzy gain from 0 to 0.5? If not the feedback would not work at all. CP, CP can be 50 from my experience. Thorsten :-)
-
Hi Timo. dkms will also need to sign the kernel module. I guess that you have to install/create first some proper certificates, if you do not deactivate secure boot on bios level. If you want secure boot enabled you might need to install/create proper certificates. sign-file: ./certs/signing_key.pem: No such file or directory I have in mind that the package was called mokutils. You can also do manually: https://www.kernel.org/doc/html/latest/admin-guide/module-signing.html What message do you get...
-
Hi Timo. The problem might be simply related to secure boot which is enables in the UEFI bios. The simple way to solve the problem is to deactivate it there. The more complex way is to use MOK and enroll the key to sign the module. Have a look here: https://wiki.ubuntu.com/UEFI/SecureBoot/DKMS In any case, you can savely use the kernel module package from launchpad repository so that you do not have to compile it on your system. The package will use dkms to maintain the kernel module. Just run $...
-
Hi Timo. You can try dconf reset -f /org/gnome/gxsm3 to reset the GUI. Thorsten :-)
-
note to ii.) If you need just one puls, please try auf GPIO dir 0001 h (for GPIO0), Poff 0001 h, Preset 0000 h. You can then adjust the puls length via "space".
-
Hi all. As this is frequently a topic in several postings, I want to summarize some issue about the coarse motion: i.) The DSP-Mover control allows you to create dedicated wave forms - even by using several channel. While using a MK3 you can map these waveforms just onto DAC0-DAC5 (Offset: x,y,z and Scan x,y,z). DAC6 is used by the bias voltage and DAC7 is used for the PLL signal. Using channel 6 or 7 usually causes some noisy output. The tooltip suggest a signal adding if numbers larger 10 are given...
-
Hi Xiaozhu Li. Scala on a Solaris system sounds that it is more than 20 years old. Did the scala have already the firewire (IEEE) connector? This is a critical part, because I have in mind that this runs only with a dedicaded board ... As Percy said: There is not software interface between the scala and GXSM (or any other software which I am aware). As far as I remember, the scala hardware allows you to access the HV inputs. The tunneling current is feed in any way via BNC. There is also a change...
-
Hi Avijit. RedPitaya is a great platform but mainly kind of USB scope. Therefore the boards have just two outputs. Using a second MK2 is certainly possible but also expensive. You may indeed check for some microcontroller with DACs included. Other options: arbitrary wave function generators (e.g. AWG5208) which you can trigger. A decent IO-card (maybe national instruments) used as arbitrary wave function generator... some kind of analog electronics like the one shown in the patent ... But definetelly...
1 >