|
Post by Lake Shore Ryan on Jan 3, 2020 11:43:01 GMT -5
Well that's something. Not a great solution long term, but something to get you past this hurdle for now. I'll see if we can get a fix for our software and will update this thread when it's out.
|
|
|
Post by Lake Shore Ryan on Jan 2, 2020 17:09:47 GMT -5
It could also be possible to apply some initial settings to the 240 module using a serial communication program like Termite, which could be enough to snap MeasureLINK out of disabling all the controls. The following steps will just enable excitation on the 2 inputs of the 240-2P and should prompt the software to give access to all additional settings. 1. Disconnect from MeasureLINK. You can't have two programs communicating with the same serial device at the same time. You don't have to shut down MeasureLINK, just click the disconnect button. 2. Connect to module using the appropriate serial configuration. The example below is my configuration where my 240 is on COM4 3. Send the *IDN? command to the instrument as I've done above to make sure you're connected and communicating. 4. Send the following commands to sent both inputs to active: INTYPE 1,2,0,0,1,1,1INTYPE 2,2,0,0,1,1,1This command is explained on page 47 of the 240 Series manual. The first command sets input 1 to be a platinum RTD, with autorange off, current reversal on, displayed units to kelvin, and input enabled. The second commands does the same thing for input 2. 5. You can test that the commands were stored by sending INTYPE? 1 and INTYPE? 2 Both commands should return 2,0,0,1,1,1. The default values are 0,0,0,0,3,0. 6. Close down Termite and reconnect using MeasureLINK. The two inputs should now be enabled, allowing access to the curve entry buttons.
|
|
|
Post by Lake Shore Ryan on Jan 2, 2020 15:49:12 GMT -5
Here is a link to the installation files for version 2.0.0 of MeasureLINK. First, uninstall your existing version of MeasureLINK. Then, unzip this file to your downloads folder and run the setup.exe file. It should install and place a new icon on your desktop. When it opens, make sure it shows version 2.0.0 at the bottom of the screen. Let me know how that goes. Sorry for this inconvenience and for this band-aid solution. It's our first day back for the year and the people responsible for software hosting on our website are not back at work yet.
|
|
|
Post by Lake Shore Ryan on Jan 2, 2020 14:31:40 GMT -5
OK, I was able to recreate your problem. It looks like a significant bug has been introduced in the latest version of MeasureLINK. I'll see if I can get a copy of 2.0.0 for you while I work on rolling the version back on our website and getting this current version fixed.
|
|
|
Post by Lake Shore Ryan on Jan 2, 2020 13:17:56 GMT -5
Hmm. That’s strange. Just noticed you have a newer version of software to me. Let me see if I can replicate.
|
|
|
Post by Lake Shore Ryan on Jan 2, 2020 12:00:44 GMT -5
Try turning the "Sensor Excitation" toggle to "ON". I can't remember the reason behind this, but the rest of the input settings are locked when the channel is disabled.
|
|
|
Post by Lake Shore Ryan on Nov 6, 2019 17:27:58 GMT -5
The only bug that is likely to trip you up relates to the new 'smart mode': Loading a curve onto the instrument works, but then when using smart mode again to load another curve, the first loaded curve doesn’t show up in the list of present curves. You have to close Curve Handler completely and reload to have it show up.
|
|
|
Post by Lake Shore Ryan on Nov 6, 2019 17:18:37 GMT -5
Hi martinezsg87 Thanks for the feedback. There are a few known bugs that I want to see removed before I list it as a suggested release, but if this version is working for you now and you want to roll it out onto other computers, I've added a link to the Curve Handler page under the heading of "Beta version 9.1". You'll have to download the zip file, extract and then run the setup file, so not as streamlined as the usual install process, but it should work for now. Let me know if you have any trouble, or if you want to report any bugs.
|
|
|
Post by Lake Shore Ryan on Nov 6, 2019 16:04:20 GMT -5
Sorry for the inconvenience. I'm happy to hear this is a feature you liked! It looks like you were an unintentional beta tester . The software was unintentionally released before it had finished verification and validation testing. We pulled it back in case there are any big issues and will release it soon when we finish testing. It won't be long. Did you happen to notice anything that was confusing or not working as you expected when you used it?
|
|
|
Post by Lake Shore Ryan on Nov 4, 2019 15:24:55 GMT -5
Hi bryanr, Sorry for the delayed response. I missed the notifications. Love the look of the chart recorder! That error message happens sometimes when updating firmware as you mentioned. A setting gets corrupted into an error state that stops you from being able to change filter settings. This can be fixed by doing a factory reset on the instrument, however, I can see this being annoying for you if you've already setup the Wi-Fi connection. You could try the following command to switch this value to something valid. SENS:FILT:LPAS:CUT 1000 This should set the low-pass filter to 1 kHz (default setting) without you having to get past UI elements that perform error checking. If it doesn't work, then I guess a factory reset is what you should try. This can be found in system settings in the bottom right corner.
|
|
|
Post by Lake Shore Ryan on Nov 4, 2019 13:34:59 GMT -5
|
|
|
Post by Lake Shore Ryan on Oct 23, 2019 10:51:42 GMT -5
Hi bryanr, so I wasn't able to fit the plotting and logging feature into our next sprint, but it's top of the backlog for the next one. So it looks like it might be another month or more before we could realistically get you a preview build of the feature. This sounds like a long time to me if I was trying to get something working now, so I wanted to see if you getting anywhere with building your own solution.
|
|
|
Post by Lake Shore Ryan on Oct 18, 2019 16:04:10 GMT -5
Thanks for pointing this out. It looks like we don't put enough information in our manual about this command. A good source for more information is this app note about fast field mapping. The first number is used for field set-point if you have a field control module installed. Because you don't, this variable is reporting as 'not a number'. See below for a bit from the manual that explains this. The final number is a bitwise representation of the digital inputs. This is useful if you want to synchronize your magnetic field measurements with some external event that causes a digital line into the teslameter to go high. Section 3.5.6.2 of the manual goes into more detail about this if you're interested. I'll let my colleague (who's responsible for the software package) know about your interest in the software approach. Might be a race to see who can deliver a solution first .
|
|
|
Post by Lake Shore Ryan on Oct 16, 2019 16:31:47 GMT -5
I like your use of user story language in defining your needs. You forgot all the "so I can" statements though . Are you planning on using this as a tool for new product development, a component of your production QC/QA process, or are you actually planning on integrating this into product you ship to customers? I think as you step through these scenarios, the required quality of the solution in terms of UX is going to ramp up quickly, and your desire for a fleshed out Lake Shore application may decrease and transition to something custom. We have two different active developments that could be useful here: - A fairly involved software package that runs on your PC and is capable of collecting and visualizing measurement data from multiple sources while also controlling environment variables. Its support for the teslameter is not quite there yet, but it's coming. This solution is probably going to be a bit heavier in terms of learning curve and capability than you're looking for, since it's targeting physics researchers who are making electrical measurements while controlling field and temperature environment variables.
- Live field plotting on the teslameter, that allows you to freeze the measurement and export the collected data to a USB flash drive for transfer to a PC in a .csv file format.
I think that second option could be a great solution for you if you're using the teslameter as part of your new product development process. Transferring individual field samples to your computer would allow you to plot and compare them however you like in something like Excel.
Let me know if Option 2 is something you'd be interested in trying or hearing more about. I'm expecting to have a beta version of this ready in a few weeks and I could arrange to get you access.
Two more questions for you: What does fast mean to you? Is 100 samples/second fast enough? Or are you measuring very fast field variations such as pulses? And are you interested in the vector component information (X,Y,Z) or just overall magnitude?
Sorry for all the questions, I'm just very interested in understanding your application. Feel free to DM me if you feel you need to share something that you don't want on a public forum.
|
|
|
Post by Lake Shore Ryan on Oct 16, 2019 13:08:26 GMT -5
If you're looking for speed, you're best off going with buffered data streaming. The lowest level implementation (SCPI) can be read about in the manual. Section 3.5.3 Buffered Data Streaming on page 27 and section 4.5.2.4 Measurement Queries on page 75 of the manual ( link). Parsing out the data coming back to you from this command can be tricky, but it can be done. Alternatively, we have an application note that uses Python to get this done really easily ( link). If you're looking to be able to visualize the field as the data is being collected, I don't have something convenient just yet, but it's something we're working on. Could you share a little about what you're trying to accomplish, so I can keep it in mind as a use case?
|
|