|
|
Post by bryanr on Oct 15, 2019 17:57:06 GMT -5
Hello, Our company acquired an F71 3 axis probe a couple of months ago and would like to log data in a file. I tried 2 solutions but running out of luck. Solution No 1 - Chart Recorder (not able to connect to the device) - I have connected F71 to our network (wifi) and got the current IP address for it.
- Turned on SCPI over TCP
- Used Test connection in Char Recorder - came back with failure (see below)
- Question : Will Chart Recorder work with F71? If yes please advise for guidance.
 Solution No 2 - Connecting to device with Socket - device refuse connection - I am still using Wifi connection this time. while trying to connect to the device's IP and port 7777. I got failure to connect still
- I have turned on SCPI over TCP.
- I notice that SCPI over TCP did not show any port number as suggested in the manual. I assumed it is listening at port 7777.
- Question: How can I connect F71 using sockets (Qt Sockets , a C++ socket implementation) or sockets in general.
- Request: Video link or other links regarding this topic is much appreciated as those "collaboration..." link found in the forum is not valid anymore.
|
|
|
|
Post by bryanr on Oct 16, 2019 11:16:54 GMT -5
Just a quick follow up. I tried connecting my PC and the F71 directly through ethernet by using static IP on both. Turned off windows firewall (just to make sure its not blocking it) I can ping F71, but still once I open a socket at 7777 I will have "connection refused" message. It seems to me that my F71 port is not openned for connection.
Since I did not see any PORT number in SCPI over TCP status display does this mean port was NOT enabled in this device?
Is this the right forum to ask this kinda question? Pardon my being new here.
|
|
|
|
Post by Lake Shore Ryan on Oct 16, 2019 11:23:46 GMT -5
Are you comfortable with Python scripting? Or LabVIEW? We have drivers for the teslameter using these options ( python link) ( LabVIEW link). My preference is Python, and I could help with a starter script. Could you tell me a little more about what you want to achieve? Unfortunately, Chart Recorder does not support the teslameter. As for your connection issues, you may be having trouble connecting to the teslameter due to the operating system being a little out-of-date. We changed from port 8888 to 7777 in a recent update to be more consistent with our older instruments. One way to test this would be to test communications using our Instrument Communication Utility. Use 192.168.200.121:8888 as the address and confirm the connection by typing in *IDN? or FETC:DC?. To bring your teslameter up to the current version, please download the latest OS version from the teslameter download page. Instructions can be found there too. This update comes with a bunch of extra benefits in addition to port manipulation, which you can read about in the changelog below the software download links. 
Please let me know what you find. Thanks! |
|
|
|
Post by bryanr on Oct 16, 2019 12:11:05 GMT -5
Thanks Ryan for the reply
I am really up to making like a "Chart Recorder" application where the user has the option to save samples ( as fast as we can ) into a file so they can look at and review it for research purposes. Now, the I am not in the SCPI point yet but once i am on it, Do you have any suggestions on how can I get probe data as fast as I can? Even a pseudo code will help.
I will be upgrading our teslameter to the latest and greatest and check if 8888 is open. I will keep you posted.
Again thank you.
|
|
|
|
Post by bryanr on Oct 16, 2019 12:19:13 GMT -5
I have not done the upgrade yet but it seems like the device is listening at 8888. I was able to connect to it using this port number. Again If you have some suggestion on how can I get the sample data using SCPI please let me know.
|
|
|
|
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? |
|
|
|
Post by bryanr on Oct 16, 2019 14:10:27 GMT -5
Yes I would like to visualize it as it is being collected. Since I can talk to the device now I will test the fastest sampling rate I can get from the device. Thanks for the links.
As for the use case from my app point of view,
As a user I would like to visualize the data as its being sampled.
As a user I would like to have the option to save the selected or all samples from the visually inspected samples.
As a user I would like to load and view (multiple) saved samples and add/edit notes into it.
Let's keep each other posted with our progress.....
|
|
|
|
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 bryanr on Oct 16, 2019 17:01:23 GMT -5
Ryan, I am actually interested on option 1 as "the user" of my application is our physics researcher. We are not planning on integrating this product as customer deliverable. This is strictly for research purposes by the company. But it doesn't hurt if you will give me an access to a preview on option 2. By the way I was using the datastream capability (by sending FETCh:BUFFer:DC?;*OPC?) and I got some column back that I can not figure what data it is? sample below [date time] , [Magnitude] , [ X ] , [ Y ] , [ Z ] ,[  ?] ,[ ] 2019-10-16T13:28:47.931,4.96958657E-1,-7.61798499E-2,4.81795032E-1,9.50688403E-2,9.91E+37,0; Can you please fill in the column in ?? |
|
|
|
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 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 bryanr on Oct 23, 2019 11:40:20 GMT -5
I actually made a pretty good progress on my end.  One question - I suspect after the firmware upgrade, I been getting a message from the device "Invalid low pass frequency , Value must be greater than 1 and less than 9000" - How can I fix this as I was not able to find the low pass frequency settings. |
|
|
|
Post by bryanr on Oct 29, 2019 11:50:36 GMT -5
Ryan, FYI here is my final product owned by Enduro. I actually like working with your device. Again thanks for your support.  Kind Regards, Bryan R. |
|
|
|
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 1000This 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. |
|
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.
?] ,[