Tektronix Technical Forums are maintained by community involvement. Feel free to post questions or respond to questions by other members. Should you require a time-sensitive answer, please contact your local Tektronix support center here.
I'm currently using the DMM4050 with Labview and communicating thru the RS232 port. When I try to get a reading from the DMM, using the example code from Labview, I get a time out error on labview and on the DMM the +511 error (Rs-232 framing/parity/overrun error detected). I've checked that both the example code and the DMM are configured with the same baudrate (9600), Flow control (none), Parity (none), Data bits (8) and stop bit (1), but I still get the same error.
I've also tried different configurations and cable, ending with the same results. Any ideas?
By permitting Flow control at paired modules the dmm stopped reporting such error.
Everything now seems good at 9600 / Flow control RTS / 8 Bit , but when I am trying to use LabVIEW SignalExpress 2.5.1 at 19200 the communication FAILS.
Unfortunately LabVIEW SignalExpress 2.5.1 does not offer higher settings than 19200 so to test them.
At 9600 Baud rate I get a number of 100 DCV logged measurements in 55 seconds (autozero Off), at ACV for 100 logged values it is required 2.19 minutes.
Now I am trying to understand if what limiting my speed this is the dmm (measuring speed at data acquisition ) Or the Baud rate ?
The true hint and answer this is not noticeable or almost hidden at fine print of page 1-26 DMM4050 User manual.
(Measurements rate chart IEEE448)
Note number 4: Mention that DMM4040 & 4050 both are Baud Rate dependable regarding remote logging speed.
I did unplug my fancy RS232 to Bluetooth adapters and use a cable instead.
I did set a number 60 iterations’ as mark and I did timing measurements at several Baud rates.
Integration time 0,02 / fixed range 10V DC / 4 ½ manual resolution / autozero off .
At 1200 --- 1m 17s
At 2400 --- 46s
At 4800 --- 28s
At 9600 --- 19s
In conclusion, since 12/2010 in which Tektronix TekDMM4040.msi (Support Driver) for Labview was lastly modified, this still is containing several unfixed bugs including few Baud Rate choices and 19200 which this is not working (never did).
The new question this is what stops your software engineers to truly fix once and for all this software driver?
This is unfinished software causing stress and driving mad your customers’ for ten long years.
Signal express for Tek, this is full of bugs too.
Cursors do not work properly.
Current measurements exported to excel with description Volts?
Graph range manual limits, this supports 3 ½ digits dmm and it does not accepts settings for 6 ½ digits resolution.
My suggestion before I lost my temper, this is TEK HQ to be notified and to take necessary actions and do something about it.
As for the NI Labview SignalExpress Tektronix Edition, that s/w package was discontinued as a offering in 2015.
Your link does redirect properly.
Therefore feel free adding it again.
I am using SignalExpress Tektronix Edition, which this is still usable at my WinXP Pro PC box which has loaded several paid software which this worth much more than the price of the operating system.
Software EOL date this is not something that it should bother End-users, where is the New TEK logging suite for these multimeter ?
And now I can hardly believe that Siglent a B brand this offers fresh and advanced logging suite with their benchtop dmm, and TEK does not.
From my end I did continue and finished my RS-232 homework so to get confidence and proofs that DMM4050-8846A hardware it does work properly up to 115.200 at which I was able to test.
- RS-232--high-speed-config.jpg (90.57 KiB) Viewed 7080 times
Interface(s): IEEE 488.2 (GPIB), Serial
Instrument Type(s): Meter
Driver Version: 1.0
Original Release Date: 05-OCT-2009
The new question this is why is so difficult for TEK ? some one to edit and correct this driver Baud Rate issues.
New Baud Rate options should be from 9600 up to 115.200
In summary due the bad work made on this driver, this it does limiting DMM performance to three measurements per second at DC.
Third-Party LAN software aloud DMM4050 to deliver 8.3 measurements per second at 0.02 Power-line cycle 50Hz.
I am now assuming that at 60Hz this DMM4050, it can do close to 10 measurements per second due LAN (or with non restricted Baud rate).
At AC signals mode, this DMM4050 slowdown allot due it in hardware design, which makes it not a great choice for inrush current measurements (remotely controlled).
Due my research, I am now aware that this is a true 8 1/2 digits multimeter at DC 10V range, and I do appreciate this almost hidden specification.
I was forced to do a fresh homework regarding NI software because of DMM4050 and now I am aware of these details:
LabVIEW this is capable using a multimeter driver this not including graphical representation (GUI).
Old SignalExpress 2.5.1 this requiring a multimeter driver with module (it own GUI), so the control module to be what the user will see and use.
Above link to NI page this is including DMM4050 available driver for Labview at registered users only (six download links at the bottom of the page).
Similar driver for Fluke 884x DMM has Update Release Date of 18-MAR-2018.
http://sine.ni.com/apps/utf8/niid_web_d ... 144FB7D21D
Even so neither this one it is a module driver that SignalExpress 2.5.1 this can use.
I did one experiment by using Labview 2015 & loaded Fluke 884x latest driver to it, my discovery this is that simulated NI fl884x IVI Specific Driver (with simulated GUI) this is very poor regarding control options.
DMM4050 driver & module this provided by TEK website, this is much better and working and it can be simply improved (bug fix), I am willing to help too by acting as beta tester, if a brave developer decides to play with it.
Who is online
Users browsing this forum: No registered users and 0 guests