Activity for bugrahan guner
-
bugrahan guner posted a comment on discussion Help
Hi Percy, We did the permission part. Now when we want to start we get the following error. tech@dell:~$ gxsm3 (gxsm3:658598): Gtk-CRITICAL **: 10:10:11.310: gtk_combo_box_text_insert: assertion 'text != NULL' failed (gxsm3:658598): Gtk-CRITICAL **: 10:10:11.310: gtk_combo_box_text_insert: assertion 'text != NULL' failed (gxsm3:658598): Gtk-CRITICAL **: 10:10:11.310: gtk_combo_box_text_insert: assertion 'text != NULL' failed (gxsm3:658598): Gtk-CRITICAL **: 10:10:11.311: gtk_combo_box_text_insert:...
-
Hi Percy, The issue was when we wanted to use the 'lift off' mode, we wanted to get a topo image over a line, finish the forward and backward imaging of the line and follow the same line path by lifting our cantilever with a certain amount so we can make measurements over the same line when we are far away. We are mainly using XS 2nd ZOff value in the Advanced tab SR DSP Control to tune this distance. However the value we put in there is not applied during the second scan of the same line (the software...
-
Hi @zahl, We had a recent problem that you patched and solved for the lift mode. I guess we kind of updated the software first time that we got the patches from you. Is there a way that we can only configure this patch but don't receive other updates or updated patches as we don't want to mess with the system's current condition but just want to fix the same issue regarding the lift off height change? Previously we installed the software based on the suggestions in the feed (https://sourceforge....
-
Hi @zahl, We were recently trying to do some indentation measurements by using the Z control menu. I am describing the problem below and will be attaching the necessary screenshots. Thank you in advance for your help. We need to be able to record the loading and unloading curves for this. So far it records the unloading part without a problem but trying to record the loading part (initial move towards the surface) as well, we tried using the 'dual mode' and the 'full ramp' options. I believe the...
-
Hi @zahl, We were recently trying to do some indentation measurements by using the Z control menu. I am describing the problem below and will be attaching the necessary screenshots. Thank you in advance for your help. We need to be able to record the loading and unloading curves for this. So far it records the unloading part without a problem but trying to record the loading part (initial move towards the surface) as well, we tried using the 'dual mode' and the 'full ramp' options. I believe the...
-
Hi Percy, Recently. we started to encounter an 'autosave' issue. While we are using the compiler to complete consecutive GVP executions, at some point the software stops saving files. After a certain period of time, it again starts saving the files. Meanwhile, it correctly executes the GVP though. Do you have any idea how can we address this issue. Since we are using the software for long experiments, too much data is lost during the process. Best. Bugrahan
-
Hi Percy, I am sending the picture of the errors in detail. Currently, when we utilize GXSM software Ubuntu displays the same error each time we use Execute command under the GVP window. In addition, all the cables are connected to USB 3.0 portals we are not running anything with USB 2.0 compliant. We just wanted to check whether this error might be arising due to the current Ubuntu version (20.04) and could upgrading the system to 22.04 might be the solution to prevent the freeze issue without damaging...
-
Hi @stm and @zahl, We installed a fresh 20.04 and installed the GXSM through ppa to that system. It is working generally fine but when we initially click execute we encounter the attached error and seems like the ubuntu freezes for a moment. It may be better to update the ubuntu to a newer version. I wanted to ask what should we do for GXSM if we update the ubuntu so it will work as it is right now. Are there any update codes or something like we run after a kernel update that we should run so GXSM...
-
Hi Thorsten and Percy, We installed a fresh 20.04 and installed the GXSM through ppa to that system. It is working generally fine but when we initially click execute we encounter the attached error and seems like the ubuntu freezes for a moment. It may be better to update the ubuntu to a newer version. I wanted to ask what should we do for GXSM if we update the ubuntu so it will work as it is right now. Are there any update codes or something like we run after a kernel update that we should run so...
-
After the errors, we also see the lines below but I suppose they were regular information lines but can be about an issue. We just wanted to make sure not to encounter any problems while using the system. ** Message: 14:11:07.836: HWI-DEV-MK2/3: Initialization and DSP verification. ** Message: 14:11:07.836: HWI-DEV-MK3-I** HwI SR-MK3: verifying MK3 FB_SPM software details. ** Message: 14:11:22.981: HWI-DEV-MK2/3: auto probing succeeded: MK3 DSP identified and ready. ** Message: 14:11:23.007: GVP-VP...
-
Hi Percy, Eventually we were left with the following line of error. Only the time part is increasing and it is appearing multiple times as we start the GXSM. Is it something to be concerned about? (gxsm3:695135): Gtk-CRITICAL **: 14:11:07.772: gtk_combo_box_text_insert: assertion 'text != NULL' failed
-
Hi Percy, Eventually we were left with the following line of error. Only the time part is increasing and it is appearing multiple times as we start the GXSM. Is it something to be concerned about? (gxsm3:695135): Gtk-CRITICAL **: 14:11:07.772: gtk_combo_box_text_insert: assertion 'text != NULL' failed
-
Hi Percy, I posted the question accidentally into another forum but there wasn't a delete option! Sorry about that, I am posting it here as well. We manage to install the GXSM for a new computer and once we started it we saw an error we haven't seen before. I just wanted to make sure it is not a critical issue on our side. Message: 10:15:13.314: HWI-DEV-MK2/3: Initialization and DSP verification. Sorry ! Can't write File !: Ev_Sep2023.log Sorry ! Can't write File !: Ev_Sep2023.log Sorry ! Can't write...
-
-
Hi Percy, We manage to install the GXSM for a new computer and once we started it we saw an error we haven't seen before. I just wanted to make sure it is not a critical issue on our side. Message: 10:15:13.314: HWI-DEV-MK2/3: Initialization and DSP verification. Sorry ! Can't write File !: Ev_Sep2023.log Sorry ! Can't write File !: Ev_Sep2023.log Sorry ! Can't write File !: Ev_Sep2023.log Sorry ! Can't write File !: Ev_Sep2023.log ** Message: 10:15:13.315: HWI-DEV-MK3-I** HwI SR-MK3: verifying MK3...
-
Hi Thorsten and Percy, Eventually, probably we messed couple of things up while trying to solve problems received at certain steps. I think the main issue is our Linux background definitely comes short when we try to implement installation steps on the first page. So we plan to start fresh with a reinstalled Ubuntu version. If one of you have the time to simplify the installation steps (I am sure it is clear for someone who knows what they are doing within Linux OS -Ubuntu :D), that would be fan...
-
Hi Thorsten and Percy, Eventually, probably we messed couple of things up while trying to solve problems received at certain steps. I think the main issue is our Linux background definitely comes short when we try to implement installation steps on the first page. So we plan to start fresh with a reinstalled Ubuntu version. If one of you have the time to simplify the installation steps (I am sure it is clear for someone who knows what they are doing within Linux OS -Ubuntu :D), that would be fan...
-
Hi Thorsten, we get the following error for make proper: root@afm1:/usr/src/linux-headers-5.15.0-84-generic# make mrproper fs/aufs/Makefile:3: fs/aufs/magic.mk: No such file or directory make[2]: *** No rule to make target 'fs/aufs/magic.mk'. Stop. make[1]: *** [scripts/Makefile.clean:68: fs/aufs] Error 2 make: *** [Makefile:1916: _clean_fs] Error 2 root@afm1:/usr/src/linux-headers-5.15.0-84-generic#
-
Hi Thorsten, We upated to 22.04 LTS from 20.04. when we run the code: we got the following error: *~~~ :~/sranger-svn/SRMK2MK3Pro/kernel-module/src# cd /usr/src/linux-headers-5.15.0-84-generic make oldconfig && make prepare # # No change to .config # make[1]: No rule to make target 'arch/x86/entry/syscalls/syscall32.tbl', needed by 'arch/x86/include/generated/uapi/asm/unistd32.h'. Stop. make: [arch/x86/Makefile:217: archheaders] Error 2* ~~~
-
Hi Thorsten, we were able to run the code but we still get the following error: Leaving directory '/usr/src/linux-headers-5.15.0-84-generic' root@afm1:~/sranger-svn/SR_MK2_MK3Pro/kernel-module/src# make make KBUILD_VERBOSE=1 CONFIG_MODULE_SIG=1 -C /usr/src/linux-headers-5.15.0-84-generic M=/root/sranger-svn/SR_MK2_MK3Pro/kernel-module/src modules make[1]: Entering directory '/usr/src/linux-headers-5.15.0-84-generic' test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \ echo >&2;...
-
Quick question :) What should be the destination folder for running sudo install sranger-modules-mk23-dkms line
-
Hi Thorsten, Thank you so much, we solved the previous issue but moved onto another one, which we couldn't figure out yet. They can be related as it is a 'Kernel configuration is invalid' error. Do you have any suggestion over how to solve it?
-
Hi Thorsten, Thank you so much, we solved the previous issue but moved onto another one we couldn't figure out yet. They can be related as it is a 'Kernel configuration is invalid' error. Do you have any suggestion over how to solve it?
-
Hi @stm and @zahl, We were recently trying to install GXSM into a new computer with better features and updated the PC to Ubuntu 22.04.3 LTS software version. However at step 4, when we try to use make install, we encounter with a problem indicating "gcc: error: unrecognized command line option ‘-mharden-sls=all’" error. We tried to solve it by updating gcc to gcc-11. However it lead to us another error indicating the following. "The following packages have unmet dependencies: gcc-11 : Depends: cpp-11...
-
Hi Percy, First of all, good news! We managed to pick up the CO. Thank you so much for the suggestions. I wanted to follow up the discussion and ask for your opinion related to another small issue. When you want to do a constant height surface measurement with the terminated tip, do you directly go for a lift at the corner of your scan frame and image the surface after lifting the tip to a certain height or go for a constantly controlled lift from the surface. Mainly, I am trying to get the idea...
-
Thank you so much Percy. Sounds challenging but fun :) One last thing, to have a greater chance for success at proper deposition, about the pressure values at the instant that you do, is there a ball park to look for?
-
Hi Percy, I wanted to ask you a question about the general CO pick-up procedure and how to do it with GXSM. I have couple of questions about the issue. What is the deposition pressure, applied bias voltage and the duration allocated for it? Voltage application procedure, time and pressure are critical aspects of the process I believe. For the pulse is it better to use a regular pulse or do it through gvp? Mainly how to apply it for this situation. I think the duration of the pulse and the magnitude...
-
Hi Percy, We figured out the issue after once again restarting the system. Actually I have another question about the lift mode if you have time to have a look at it. We want to be able to engage in the backwards direction of lifted scan if that is possible. If it is easier to do it, adding a time delay between the engaged and lifted position measurements will solve the issue too when we have a certain delay before the lifted scan starts. If it is possible to apply one of these options, preferably...
-
CP and CI are positive. Also we are sure that incoming signals etc are same as before so there definitely is a sign convention issue. Is there something else we can cross check? Do you have any ideas for the source of the problem?
-
CP and CI are positive. Also we are sure that incoming signals etc are same as before so there definitely is a convention issue. Is there something else we can cross check? Do you have any ideas for the source of the problem?
-
Hi Percy, The new files are working fine. However, after we updated our software for the lift mode, it seems like the signs that we have for the gains in the feedback & scan window as well as the piezo representation we have for the z in the application window are reversed. Do you have any idea why this has happened? It may be a preference issue as well (we checked the previously taken screenshots of the configuration that we have) but we wanted to ask for your opinion in the meantime since it may...
-
Hi Percy, The new files are working fine. However, after we updated our software for the lift mode, it seems like the signs that we have for the gains in the feedback & scan window as well as the piezo representation we have for the z in the application window are reversed. Do you have any idea why this has happened? It may be a preference issue as well but we wanted to ask for your opinion in the meantime since it may be due to something different and overlooking may cause other problems. Thank...
-
Hi Percy, Perfect! Thank you so much for your time. Do we need to reinstall the GXSM for the patch to work or is there a way to directly just patch the software?
-
Hi Percy, I just wanted to ask if there is anything that we may try in the meantime to make the mode work, while we are waiting for your response.
-
Thank you so much Percy. We are looking forward to your response.
-
Ours is MK3.
-
Hi Percy, We are trying to implement the Lift mode with our controller. However, it seems like the value that we put for XS 2nd ZOff in the Advanced tab is not applied when we start the scan. Mainly the feedback is turned off but the z value doesn't change according to the offset we set during the scan. It only changes according to the topography. We may be doing something wrong about the 'Channel Selector' selections or there may be another setting (DSP, etc.) that we need to arrange. We wanted...
-
Hi Percy, We are trying to implement the Lift mode with our controller. However, it seems like the value that we put for XS 2nd ZOff in the Advanced tab is not applied when we start the scan. Mainly the feedback is turned off but the z value doesn't change. We may be doing something wrong about the 'Channel Selector' selections or there may be another setting (DSP, etc.) that we need to arrange. We wanted to ask for your opinion about the issue and ask the settings needed for this operation for the...
-
Hi Percy, We are trying to implement the Lift mode with our controller. However, it seems like the value that we put for XS 2nd ZOff in the Advanced tab is not applied when we start the scan. Mainly the feedback is turned off but the z value doesn't change. We may be doing something wrong about the 'Channel Selector' selections or there may be another setting that we need to arrange. We wanted to ask for your opinion about the issue and ask the settings needed for this operation for the current software...
-
Hi Percy, We are trying to implement the Lift mode with our controller. However, it seems like the value that we put for XS 2nd ZOff in the Advanced tab is not applied when we start the scan. We may be doing something wrong about the 'Channel Selector' selections or there may be another setting that we need to arrange. We wanted to ask for your opinion about the issue and ask the settings needed for this operation for the current software version. All the best, Bugrahan
-
Hi Percy, We are trying to implement the Lift mode with our controller. However, it seems like the value that we put for XS 2nd ZOff in the Advanced tab is not applied when we start the scan. We may be doing something wrong about the 'Channel Selector' selections or there may be another setting that we need to arrange. We wanted to ask for your opinion about the issue and ask the settings needed for this operation for the current software version. All the best, Bugrahan
-
Hi, If the situation isn't solved through software-based solutions, the method we followed may help in implementing new hardware if you have access to your signals. In our system, we managed to use our Veeco EnviroScope SPM as an FM AFM, which originally didn't have an FM AFM capacity, by dividing our signals using a Signal access module. We get our excitation signal from the main AFM control box, divide it through a Signal access module, demodulate it with a Lock-in amplifier(which should have PLL...
-
Hi, If the situation isn't solved through software-based solutions, the method we followed may help in implementing new hardware if you have access to your signals. In our system, we managed to use our Veeco EnviroScope SPM as an FM AFM, which originally didn't have an FM AFM capacity, by dividing our signals using a Signal access module. We get our excitation signal from the main AFM control box, demodulate it with a Lock-in amplifier(which should have PLL capacity), and feed them to the GXSM controller....
-
Hi, If the situation isn't solved through software-based solutions, the method we followed may help in implementing new hardware if you have access to your signals. In our system, we managed to use our Veeco EnviroScope SPM, which didn't have an FM AFM capacity, to work as one by dividing our signals using a Signal access module. We get our excitation signal from the main AFM control box, demodulate it with a Lock-in amplifier(which should have PLL capacity), and feed them to the GXSM controller....
-
Hi, If the situation isn't solved through software-based solutions, the method we followed may help in implementing new hardware if you have access to your signals. In our system, we managed to use our Veeco EnviroScope SPM, which didn't have an FM AFM capacity to work as one by dividing our signals using a Signal access module. We get our excitation signal from the main AFM control box, demodulate it with a Lock-in amplifier(which should have PLL capacity), and feed them to the GXSM controller....
-
Hi Percy, I just wanted to update the post since right now we have the ability to do the experiments with a pretty good consistency. Thank you so much for your time and help. All the best, Bugrahan
-
Hi Percy, I think the MIXER1 is already defined as In1 in our case. If you can enable the use of them as a rtquery, we can directly give them a try. I am also attaching the screenshot that we have for the configurations too. Thank you so much. All the best, Bugrahan
-
Hi Percy, It works perfectly in terms of getting the value. Thank you so much. I wanted to ask you if there is also a way to do the same thing for ADC1 value as well (or IN1)? I checked the manual for it to see what we can do with rtquery function but couldn't find an answer to that since all the options that I tried are not matching with the desired ADC1 value (or IN1). If there is a way, that would be great to do it for the frequency shift that we have somehow as well. Thank you so much for your...
-
Hi Percy, Actually yes, we are storing the Z Mon during our experiments. The thing that we want to do is actually storing the Z value that we can track in the application window, which is instantaneously changing in real time. This way, we have the chance to store its value inside our code, we think that there is a room for overcoming the issue that we got to a certain extent, even though it will be still there. Is it possible to get the Z value shown in the screenshot into a variable in python?...
-
Hi Percy, We repeated the procedure by adding the dummy lines before the first Z changing line as well, however it didn't change anything in terms of the issue. We can say approximately 10% of the data is suffering from this problem. The thing that we are completely sure about is that the Z value is changing with twice the value that we give to the first VP line changing the Z value. So if we are going to move away from the surface with 150A, time to time it does it two times in a row with a total...
-
Hi Percy, The XY is okay right now, we are sure that nothing was problematic about that today. The double retraction we encounter is that the GVP's first line, where we go away from the surface, is executed twice time to time. As a result, during the duration of a single GVP execute, larger sized data files are saved. We are sure that the repeat is not accidentally on. I will update the post with a plot tomorrow as soon as possible. Thank you so much. All the best, Bugrahan
-
Hi Percy, The XY is okay right now, nothing seemed problematic about that today. The double retraction we encounter is that the GVP's first line, where we go away from the surface, is executed twice time to time. As a result, during the duration of a single GVP execute, larger sized data files are saved. We are sure that the repeat is not accidentally on. I will update the post with a plot tomorrow as soon as possible. Thank you so much. All the best, Bugrahan
-
Hi Percy, We did the flashing and the update once again and refreshed everything today. The Feedback and offset stability were pretty good and they didn't create a problem this time during the experiment. Overall the system is working fine in terms of the durability. We also changed the channel selections according to the attached screenshot. Right now after reimplementing, since the problem with stopping the autosave is also solved, the only remaining issue is the double retraction and saving more...
-
Hi Percy, We did the flashing and the update once again and refreshed everything today. The Feedback and offset stabilities were pretty good and they didn't create a problem this time during the experiment. Overall the system is working fine in terms of the durability. We also changed the channel selections according to the attached screenshot. Right now after reimplementing, since the problem with stopping the autosave is also solved, the only remaining issue is the double retraction and saving...
-
Hi Percy, We did the flashing and the update once again refreshed everything today. The Feedback and offset stabilities were pretty good and they didn't create a problem this time during the experiment. Overall the system is working fine in terms of the durability. We also changed the channel selections according to the attached screenshot. Right now after reimplementing, since the problem with stopping the autosave is also solved, the only remaining issue is the double retraction and saving more...
-
Hi Percy, Thank you for taking time to provide sample codes. I tried the exact same code that you provided here with counts similar to the ones that we have previously had, just to check what we will observe. Also, I updated the GXSM and made the arrangements that you mentioned like the boxes need to be unchecked and the features need to be disabled. However, even though I followed everything you mentioned, the feedback stability was kind of worse than it was before. At some point it was constantly...
-
Hi Percy, Thank you for taking time to provide sample codes. I tried the exact same code that you provided here with counts similar to the ones that we have previously had, just to check what we will observe. Also, I updated the GXSM and made the arrangements that you mentioned like the boxes need to be unchecked and the features need to be disabled. However, even though I followed everything you mentioned, the feedback stability was kind of worse than it was before. At some point it was constantly...
-
Hi Percy, Thank you so much for your response. Sorry for the inconvenience with the images. I didn't have the chance to do it that way at that instant since the experiment was going on and I don't want to accidentally do something(change the code, etc.) while doing these steps. I am attaching the code as text if it is still okay. Edit: The indents are not shown in the post I believe, even if I put them to the original post. Sorry about that. import gxsm import time import statistics import numpy...
-
Hi Percy, Thank you so much for your response. Sorry for the inconvenience with the images. I didn't have the chance to do it that way at that instant since the experiment was going on and I don't want to accidentally do something(change the code, etc.) while doing these steps. I am attaching the code as text if it is still okay. import gxsm import time import statistics import numpy as np x_dist = 1000 #distance in angstrom y_dist = 1000 #distance in angstrom x_pts = 10 y_pts = 10 N = 30 x_offset...
-
Hi Percy, Thank you so much for your response. Sorry for the inconvenience with the images. I didn't have the chance to do it that way at that instant since the experiment was going on and I don't want to accidentally do something(change the code, etc.) while doing these steps. I am attaching the code as text if it is still okay. import gxsm import time import statistics import numpy as np x_dist = 1000 #distance in angstrom y_dist = 1000 #distance in angstrom x_pts = 10 y_pts = 10 N = 30 x_offset...
-
Hi Percy, I just wanted to post a quick update. Before we start, we completed the update again. Also changed the latest code for the use of 'gxsm.moveto_scan_xy(x,y)'. However, still at some instants (still randomly), the previously discussed double retraction occurs in the GVP. This issue was more frequent than before compared to the previous cases. The Feedback stability was much better compared to previous trials, but it again went of at some instant and without loading the DSP settings, we couldn't...
-
Hi Percy, We will try it again tomorrow with the latest update. I will update the post with the current situation after we give it another go. Thank you so much for your help and time. All the best, Bugrahan
-
Hi Percy, We wait 1 second before the GVP execution in all cases. Also, we are waiting approximately '5 seconds+execution time of GVP' after it is executed. Right now we have an updated version for the code. I am attaching that as well. The inner loop issue is not utilized in this version of the code. However, the problem is still there. Additionally, we add the feedback 'on' button click to our GVP too. Z value in the application window starts to saturate at 150A in the case when we want to continue...
-
Hi Percy, We wait 1 second before the GVP execution in all cases. Also, we are waiting approximately '5 seconds+execution time of GVP' after it is executed. Right now we have an updated version for the code. I am attaching that as well. The inner loop issue is not utilized in this version of the code. However, the problem is still there. Thanks for your help. Looking forward to hearing from you. All the best, Bugrahan
-
Hi Percy, We updated the GXSM and continued to try. Right now, with location changes we are okay. Thank you for the update. I think there are only a couple of issues that are still in an ongoing situation. We still continue to observe consecutive retractions due to an overlap in GVP. Also, the feedback at some point still goes off and we need to turn it back on. With the current configuration that we have, I think we will be able to conduct our experiments but if there was an automated way to turn...
-
Hi Percy, For finding a solution to the issue that we have, while the current problem is still present, we considered that we may use GVP for changing the location as well. Since our idea depends on changing location and taking recursive GVP measurements at that point before moving to the next one, we may be able to use 'VP-dX' and 'VP-dY' to move. However, again there is an inconsistency about that as well. When we run the GVP with non-zero 'VP-dX' or 'VP-dY' values, sometimes it changes the XYs...
-
Hi Percy, For finding a solution to the issue that we have, while the current problem is still present, we considered that we may use GVP for changing the location as well. Since the idea depends on changing location and taking recursive GVP measurements at that point before moving to the next one, we may be able to use 'VP-dX' and 'VP-dY' to move. However, again there is an inconsistency about that as well. When we run the GVP with non-zero 'VP-dX' or 'VP-dY' values, sometimes it changes the XYs...
-
Hi Percy, Thank you so much for taking time to check the issue. Sorry for the late response. I am also attaching the configuration that we have for the script and the GVP. In the code please just ignore the excess amount of comments since we were going back and forth during the trials. As you said, I think the issue is related with movements through using ScanX and ScanY slots. I am looking forward to hear from you about your debugging. Meanwhile, I will give a try to your code in our system as well...
-
Hi Percy, We tried the method you suggested, however the instability still continues unfortunately. Also, in addition to the Z-SERVO/FEEDBACK enabling, to solve the issue we tried working with freshly started gxsm sessions too but each time at some point (randomly) the feedback just turned off (also the z-adjuster turned off) and/or the offset/scanxy points shown in the application window are shifted to an extreme location on its own. To solve these, we tried the combinations of booster on/off and...
-
Hi Percy, The sum of Z is already zero in our configuration. I am not exactly sure if something is off in our attached GVP configuration. If you have the chance, I would love to get your opinion regarding to that. We will try the tip you mentioned to see if it makes a change for us. Thank you so much. All the best, Bugrahan
-
Hi Percy, Thank you so much for your help with the issue. We managed to standardize the procedure for eliminating the problems that we have. Right now, in terms of the discussed problem, we are in a good position. There was just a small additional thing that I wanted to ask. In the application window, time to time (pretty randomly) the feedback light switches to red due to the closing of the feedback. In that case, also the second light from right hand side also closed and directly turns to black....
-
Hi Percy, Thank you so much for your help with the issue. We managed to standardize the procedure for eliminating the problems that we have. Right now, in terms of the discussed problem, we are in a good position. There was just a small additional thing that I wanted to ask. In the application window, time to time (pretty randomly) the feedback light switches to red due to the closing of the feedback. In that case, also the second light from right hand side also closed and directly turns to black....
-
Hi Percy, Thank you so much for your help with the issue. We managed to standardize the procedure that we have for eliminating the problems that we have. Right now, in terms of the discussed problem, we are in a good position. There was just a small additional thing that I wanted to ask. In the application window, time to time (pretty randomly) the feedback light switches to red due to the closing of the feedback. In that case, also the second light from right hand side also closed and directly turns...
-
Hi Percy, Thank you so much. We almost solve our issue I think. Right now stability-wise we are at a good position. Our only concern is that, even though we control the GVP with our new script to not be busy before the next one is executed(thanks to your guidance and suggestions), while we are gathering data. without a specific reason sometimes the save file just contains more data points, thus has a larger file size. When we check the average load for the system, it is around 0.36, so the system...
-
Hi Percy, According to your description and suggestions we have reinstalled gxsm-svn. Also, we now use time.sleep instead of gxsm.sleep in our code. The number of channels is 4 at the moment with 1000 data points per vector at most. Normal data size is around 418 kB during the execute of the GVP. However, we still have couple of issues regarding to the system. Occasionally, we encounter the double run of GVP (the one that I described as one starts before the previous one is finished and certain lines...
-
Hi Percy, Thank you so much for the tips, your time, and help. At this point we will go with your suggestion to see how installing the latest Gxsm3 from SVN will work. For this step, I think we can go with completely removing the current GXSM and getting the new one from scratch. Can you refer to a post, source, etc. that describes how to remove the software completely? I searched for it in previous posts but I think missed it if it was there. Since even though we get rid of the files in one of our...
-
Hi Percy, Our pc has 8 processorS, 32 GB ram 1.5 GB ram for gpu and 2TB ssd at the moment. In terms of capability, I think it is acceptable. If you have the chance to check it, I am also attaching our python code as well, in case the problem is caused by that. When we run the GVP with the script, approximately at every 20-25 data, we encounter an issue, in which the GVP goes away from the surface more than once(kind of executing the GVP two times before the first run finishes. So, the vec[00] line...
-
Hi Percy, Our pc has 8 processor, 32 GB ram 1.5 GB ram for gpu and 2TB ssd at the moment. In terms of capability, I think it is acceptable. If you have the chance to check it, I am also attaching our python code as well, in case the problem is caused by that. When we run the GVP with the script, approximately at every 20-25 data, we encounter an issue, in which the GVP goes away from the surface more than once(kind of executing the GVP two times before the first run finishes. So, the vec[00] line...
-
Hi Percy, We are not running the PAC-PLL as far as we know but in terms of being sure about that it is not running in the background somehow, can you describe us how we can stop or close it? Also the issue that we encounter in terms of the stability can be caused by the data points that we were trying to get inside the GVP. After we changed the number of points to be recorded for each line, the stability of the system definitely improved. However is there a way to increase the number of points( to...
-
Hi Percy, Thank you so much for your response. We tried the 'turbo' mode implementation but it seems like the issue is still there. I think at this point we can go for changing to the latest GXSM3 (SVN) update. Can you briefly explain how we can manage to do it? We were trying the 'purge' based codes to first uninstall the APT packages before switching to the SVN packages but probably we tried to do it in the wrong directory, since we couldn't manage the system to purge apt files for GXSM. Additionally,...
-
Hi Percy, Thank you so much for your response. We tried the 'turbo' mode implementation but it seems like the issue is still there. I think at this point we can go for changing to the latest GXSM3 (SVN) update. Can you briefly explain how we can manage to do it? We were trying the 'purge' based codes to first uninstall the APT packages before switching to the SVN packages but probably we tried to do it in the wrong directory, since we couldn't manage the system to purge apt files for GXSM. Additionally,...
-
Hi Percy, Thank you so much for your response. We tried the 'turbo' mode implementation but it seems like the issue is still there. I think at this point we can go for changing to the latest GXSM3 (SVN) update. Can you briefly explain how we can manage to do it? We were trying the 'purge' based codes to first uninstall the APT packages before switching to the SVN packages but probably we tried to do it in the wrong directory, since we couldn't manage the system to purge apt files for GXSM. Thanks...
-
Hi Percy, I would like to ask you a question about a saving issue that we encountered. We are trying to implement time-resolved experiments with our system by using the 'GVP' vector probe from the Application window and the 'GXSM Python Remote Console' for repeating the action consecutively. I am attaching the screenshots that we have for both windows as well. While completing these actions, a MATLAB script that we wrote retrieves the information from the last saved file to correct the frequency...
-
Hi Percy, I would like to ask you a question about a saving issue that we encountered. We are trying to implement time-resolved experiments with our system by using the 'GVP' vector probe from the Application window and the 'GXSM Python Remote Console' for repeating the action consecutively. I am attaching the screenshots that we have for both windows as well. While completing these actions, a MATLAB script that we wrote retrieves the information from the last saved file to correct the frequency...
-
Hi Percy, I would like to ask you a question about a saving issue that we encountered. We are trying to implement time-resolved experiments with our system by using the 'GVP' vector probe from the Application window and the 'GXSM Python Remote Console' for repeating the action consecutively. I am attaching the screenshots that we have for both windows as well. While completing these actions, a MATLAB script that we wrote retrieves the information from the last saved file to correct the frequency...
-
Hi Percy, I would like to ask you a question about a saving issue that we encountered. We are trying to implement time-resolved experiments with our system by using the 'GVP' vector probe from the Application window and the 'GXSM Python Remote Console' for repeating the action consecutively. I am attaching the screenshots that we have for both windows as well. While completing these actions, a MATLAB script that we wrote retrieves the information from the last saved file to correct the frequency...
-
Hi Percy, I would like to ask you a question about a saving issue that we encountered. We are trying to implement time-resolved experiments with our system by using the 'GVP' vector probe from the Application window and the 'GXSM Python Remote Console' for repeating the action consecutively. I am attaching the screenshots that we have for both windows as well. While completing these actions, a MATLAB script that we wrote retrieves the information from the last saved file to correct the frequency...
-
Hi Percy, Yes, we checked that box, which is in the advanced tab of the DSP Control menu. Even though we open the LDC feature, for values that we give for dx, dy and dz, nothing happens. We tried both positive and negative values in a range starting from reasonable values to excessively large ones to at least see a difference. Overall, we still observe a drift in the Z value throughout the scanning procedure after we approach to the surface and the values used have zero affect on that. We also made...
-
Hi Percy, Yes, we checked that box, which is in the advanced tab of the DSP Control menu. Even though we open the LDC feature, for values that we give for dx, dy and dz, nothing happens. We tried both positive and negative values in a range starting from reasonable values to excessively large ones to at least see a difference. Overall, we still observe a drift in the Z value throughout the scanning procedure after we approach to the surface and the values used have zero affect on that. The value...
-
Hi Percy, Thank you so much for the help about the slope correction. It works now. If you have the chance I want to ask an additional question towards a similar problem with LDC (Linear Drift Correction). Right now it is not working when we want to correct the Z value by changing dz parameter to a non-zero A/s value when we are in an engaged situation. I thought it may be solved with a similar approach so I wanted to ask for your opinion. Thank you so much in advance for your time and effort. All...
-
Hi Percy, We want to start scans one after the other since the aim is to observe influence of another parameters change. For this purpose, we need to start scans by writing a python code but we are not sure about the syntax that we need for it since it is not shown in a suitable form when we put the cursor on top of the start button in spm scan control menu. Can you guide us for finding the correct syntax ? Thanks in advance. All the best, Bugrahan
-
Hi Percy, Thanks for the suggestions. I am adding the settings that we got as screenshots to not miss a point while configuring the new settings and receive your comments based upon them. Thanks again for your time and help. Regards, Bugrahan Guner
-
Hi Percy, I was trying to use the slope corrections from the 'Advanced' menu in the application window. However, no matter which value that I inserted into the Slope X and Slope Y fields of Scan characteristics section, the system won't provide an affect on the scan. Is there a solution method that you can recommend to overcome this issue ? Thanks in advance. All the best, Bugrahan
-
Hi Percy, I wanted to ask you if it is possible to call matlab and matlab functions by using pyromote console for our software version of GXSM-3.53.0. If it is not possible to implement matlab utilities into the console, is there a way to open data files from pyromote console, mainly for tracking the frequency shift that we feed to the controller from an external PLL. Thank you so much in advance for your time and guidance. All the best, Bugrahan
-
Hi, We are trying to use the autosave option while using 'Z spectroscopy' and 'GVP' menu options for scanning. However, the function is not working while full ramp is on in both options. What can be the reason for that ? Thanks in advance All the best, Bugrahan
-
Hi, We are trying to use the vector probe, GVP, function of the software. However, after running the vector probe, the feedback controller is not turning on and controlling the output value that we have. Thus, it doesn't match with the initial value that we entered to the setpoint of the source that we have, which is in the 'Feedback & Scan section'. Through the operation, enable feedback controller option was always open. I believe there is a certain problem with the feedback controller. Thorough...
-
Hi, We are trying to use the vector probe, GVP, function of the software. However, after running the vector probe, the feedback controller is not turning on and controlling the output value that we have. Thus, it doesn't match with the initial value that we entered to the setpoint of the source that we have, which is in the 'Feedback & Scan section'. Through the operation, enable feedback controller option was always open. Is there a particular reason that may cause this problem ? Thanks in advance...
-
Hi @stm and @zahl, Omur and I are working together on the GXSM implementation. We had solved a previously mentioned issue that we got with DSP with the suggested method here, which is mentioning flashing the firmware. Everything was fine but we needed to close all the set up. After restarting, the program didn't open when we tried to open it directly from the terminal. We only managed to open the program by using administrative command of 'sudo gxsm3'. Even in this case, it didn't recognize the hardware...
-
Hi @stm and @zahl, Omur and I are working together on the GXSM implementation. We had solved a previously mentioned issue that we got with DSP with the suggested method here, which is mentioning flashing the firmware. Everything was fine but we needed to close all the set up. After restarting, the program didn't open when we tried to open it directly from the terminal. We only managed to open the program by using administrative command of 'sudo gxsm3'. Even in this case, it didn't recognize the hardware...
-
Hi @stm and @zahl, Omur and I are working together on the GXSM implementation. We had solved a previously mentioned issue that we got with DSP with the suggested method here, which is mentioning flashing the firmware. Everything was fine but we needed to close all the set up. After restarting, right now the DSP configurations and all the previous preferences are gone unfortunately. -Is it normal to encounter with a situation like this after a restart or is there a specific problem about the Ubuntu...
1 >
