Eurotherm 3216 labview error

Hello,
I recently downloaded the euotherm labview driver from ni.com and I am using this USB to RS485 converter http://www.kksystems.com/english/html_files/product_pages/usb485.htm for communication, unfortunately I keep getting this error when using both example VI's.
1. When I use the process value monitoring example vi
Error -1073807339 occurred at VISA Read in Eurotherm 32xx Series.lvlib:Utility MODBUS RTU Receive Message.vi->Eurotherm 32xx Series.lvlib:Utility Read From Register - Floating Point.vi->Eurotherm 32xx Series.lvlib:Utility Read From Register - Float or Int.vi->Eurotherm 32xx Series.lvlib:Read Process Variables.vi->Eurotherm 32xx Series Process Value Monitoring.vi
2. When I use the temperature control monitoring example vi
Error -1073807339 occurred at VISA Read in Eurotherm 32xx Series.lvlib:Utility MODBUS RTU Receive Message.vi->Eurotherm 32xx Series.lvlib:Utility Read From Register - Integers.vi->Eurotherm 32xx Series.lvlib:Utility Read From Register - Float or Int.vi->Eurotherm 32xx Series.lvlib:Configure Instrument Mode.vi->Eurotherm 32xx Series Temperature Control Monitoring.vi
Can someone please help with this?

And did you check that you have the right cable?
rs485 is not equal to rs232 !
you need two wires for sending and receiving and they should be terminated when the distance is long.
Furthermore your rs485 card should switch from send to receive in time.
greetings from the Netherlands

Similar Messages

Running two Eurotherm 3216 temperature controllers using the driver available from Labview

Hi All,
I am trying to control two Eurotherm 3216 temperature controllers using the driver provided by NI at http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=7F14CDCB24923797E04400144F1EF8.... Specifically, I am using the "Temperature Control Monitoring" example.
I have been able to operate a single temperature controller using this code. However, I need to operate two controllers, and I havent been able to modify the code appropriately to do it.
I initially tried just repoducing the entire code and running it but that provides me with an error. However, if I run the code while using "highlight execution" it works just as I need it to...except to slowly for my purpose.
If anyone has any insight as to how I may run both controllers, I would really appreciate it.
Thanks

Here something’s to try.
1)      Make sure both controllers have RS485 comms modules installed
2)      Connect both controllers in Daisy Chain configuration using the EIA485 instructions from Page 16 of the Manual you mentioned.
3)      Ensure both the KD458 and the 3216 controllers have identical Comms configurations. ie Baud Rate, Parity etc
4)      Verify your setup: In the "Temperature Control Monitoring" example” change the Unit Address, Baud Rate, Parity and Break Length to match the 1st controllers values. Verify that you can communicate with the 1st controller.
5)      Using the Same "Temperature Control Monitoring" example”, NOT a second copy, change the Unit Address, Baud Rate, Parity and Break Length to match the 2nd controllers values. Verify that you can communicate with the 2nd controller.
Comms problems are difficult to fault find so be methodical and you will succeed.

Labview error GPIB controller not adressed correctly

I get this Labview error: GPIB controller not adressed correctly (LV5.1, win NT4) when i try to send data to a HP4275A LCR meter. How ever it works on an older system running with LabView 5.0 (also NT)!!!
How can I get rid of this problem????

Hi Diego, thanks for the hints!
I tried to configure (GPIB) everything standard.
when I try a 488 command initialze, I get the controller conflict, when i don't do this I get atime out problem either by 488 write-command or by 488.2 send-command.
the differences between the systems where it works and where not are:
working: Win 95, LV 5.0, GPIB-card/TNT (plug & play)
not-working: WinNT, LV 5.1, GPIB-card/PCI
i tried to set baord config to the same parameters...
on the faulti system however I see the instrument with the MAX and I can send commands, without problems !!!!
Also the driver you posted does not work (but the NI-communicate program ;-)
i have no clue what else to do!
btw. how do I copy the spy output when running the program? I may provide
this to find errors.
Since MAX indicates the board is all right I guess it is not necessary to reinstall the boarddrivers?!

LabVIEW error code3: Could not load front panel.

Hi
I am getting second time the "LabVIEW error code3: Could not load front panel." when working with the development environment of LabVIEW 2009 SP1.
It is really annoying as I loose time as I have to revert to saved previously code.
Does anybody know where it may be coming from and how to avoid it?
Thanks
Pawel
Solved!
Go to Solution.

Pawel,
the panel has an origin which you can see in your VI:
Every element will be placed in a position in regard to this origin:
The position has a limit in regard to the bound. I am not sure about the value, but it should be around -35k...35k (or the double of it)....
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

General Labview Error Handler question discussion

Recently two functions were brought to my attention, the General Error Handler and the Simple Error handler.
And I cannot wrap my hand around these two features. While I have been using Labview I have always used the Labview error cluster. When would you use these two features? As I feel the cluster error is much help.
Maybe it is my defnition that I have confused:
The general error handler will display a dialogue box describing the error that will be passed and shuts down the code?
The simple error handler notifys the operator that an error has occured but it can be customized for adding functionality, it takes the error cluster input and determines if an error was generated. "If an error has been generated, the VI displays a dialog box with the error code, a brief description of the error, and the location of the error." How is this not the same as an error cluster?
If anyone has any simple code examples for this or knowledge I greatly appriciate it.
Caleb

Jacobson wrote:
Psireaper9 wrote:
The simple error handler notifys the operator that an error has occured but it can be customized for adding functionality, it takes the error cluster input and determines if an error was generated. "If an error has been generated, the VI displays a dialog box with the error code, a brief description of the error, and the location of the error." How is this not the same as an error cluster?
You are correct that they give the same information. The difference is that if you want to use an error cluster you will need an indicator on your front panel. If you use the simple error handler you won't have to have an error cluster on your front panel but the user will be notified if an error does occur.
Think about all the programs you normally use (excel, chrome, etc.). As a user you expect that errors aren't happening, and if errors do occur then the application will usually just close out and you get an error dialog about the error.
I use the simple error handler with no user interaction to extract the error text. Is there an easier way of doing that?

How to force TestStand to ignore LabVIEW errors

Hi,
usually where there is an error in the LabVIEW code module TestStand stops and gives a pouup message .
Is there any way to force TestStand to ignore LabVIEW errors and contiouse testing?
Thanks

You can also work more globally - go to the Configure menu item and select Station Options.
At the bottom of the execution tab, there's a section for what to do on Run-time errors. -> Show dialog, Cleanup, Ignore or Abort.
Whilst not specific to steps configured to use the LabVIEW adapter (assuming you're mixing some programming languages) that at least get you continuing on to the next step without the dialog.
If you need to assess if it's specifically LabVIEW modules causing the error, then you need to use the Station, Process Model or Sequence File callback for On run-time error, and the step gets passed as a parameter. That would allow you to work out if the step was LabVIEW specifically and then make a decision as to what to do next.
Hope that helps.

How to terminate TestStand Application after a LabView error.

We've just started launching TestStand from a command line, and when it (TS) stops sequence execution due to a LabView error, the command window doesn't know its status. So, I have a two part question:
1) Is there a way to COMPLETELY STOP the TestStand application when a LabView error is encountered? (I have been able to get the error popup to stop, but TestStand is still active and the command line is still sitting there thinking everything is fine).
2) Assuming that there is a solution to #1, is there also a way to get LV or TS to report the error to an external command prompt or batch file?
Thanks,
   - Paul Iovanna
Solved!
Go to Solution.

Hi Manooch,
We've managed to get the TestStand sequence to stop when we want it to (by using the /quit option in the command line), but now we can't seem to get Reports to generate.
Specifically what we are doing is including a particular test sequence in a fully automated Build/Test/Report system. After an automated build of our product completes, we have tools and command files that load all appropriate code into the various components of our system, and then we lauch a TestStand sequence that exercises much of the newly imaged system. Since we are running from the command line - and that command line is being monitored by other processes within our Build/Test/Report system, we need to have TestStand stop AND exit, or else the command line just hangs.
So, we really need two things to happen:
1) Get TestStand to stop execution AND exit - and we seem to have this working.
2) Report the results from the test sequence:
   - We have no problem doing this when the Sequnce Editor is launched directly, and the sequence is started from its GUI.
   - However, when we use the command line to launch the sequence via your "TestExec.exe" - there's no report! All of the Report Options settings are the same as for the Sequnce Editor GUI.
So, at a minimum, we need to get the usual report to be generated and saved when we launch from the command line - and the preferred option would be to have any error codes from TestStand (or LabView, since the test sequence uses only LV steps) reported directly to the stdout, in this case the command line.
Hopefully that explains our setup and requirements a little better - and thanks in advance for the assistance.
FYI - TestStand version 4.1.1 running on Windows XP.

Watch the NI-Week 2009 Presentation: Updating the LabVIEW Error Handling Core

The resources for the "Updating the LabVIEW Error Handling Core" NI-Week 2009 Presentation are now online.
See them here: http://lavag.org/topic/10741-updating-the-labview-error-handling-core/
Copyright © 2004-2015 Christopher G. Relf. Some Rights Reserved. This posting is licensed under a Creative Commons Attribution 2.5 License.

I have always gone the latter route when I needed it. I usually use an action engine to keep track of the error messages. Said action engine can be used to combine and suppress errors, as well. I have posted an example below (LabVIEw 7.1). In this case, the error propagation is occurring in a task handler which is processing multiple command/data pairs. The command is set at the beginning of the task and the error handler is sprinkled liberally throughout the task code. In this particular case, the desired behavior is to continue execution on error, but log the errors.
I prefer this type of method because it gives me complete control over the error propagation. It has the down side of requiring more code and effort, but I think it is worth it. I like functionality to be explicit on my block diagrams. It makes long-term maintenance much easier.
This account is no longer active. Contact ShadesOfGray for current posts and information.
Attachments:
ErrorPropagation.llb ‏65 KB

How to disable drive upon LabView error

I'm running a closed loop PD position controller in Labview 8.5 and NI PCI-6259 M series card and BNC-2120. I'm sending an analog voltage signal (+/- 10) to a Copley Xenus amplifier (current command) as well as a +5v signal to enable the amplifier. The controller uses position for feedback. When labview errors out, the daq card stays in its current state (and keeps sending the 5v enable signal). For safety reasons, how can I configure my system so that this signal stops being sent out, and the amp is disabled?
Maciek

The program crashed. I shut off the amp. The actuator shaft, which is positioned vertically, dropped to its lowest position due to gravity (it's a linear actuator). The daq card kept pumping out a high force command, due to the large position error created by the disturbance, as well as the 5v enable signal. Upon turning the amp back on, the PD controller saw a large difference between desired and actual position, and the actuator shaft shot up forcefully, creating a very dangerous situation. In the program, I have a case structure which won't enable the amp. unless the difference between desired and actual position is small enough. But the amp stays enabled when labview crashes.
m

Problem with Vision Builder and LabView: Error -1074395995, File not found

I have created an inspection with Vision Builder AI 2009 SP1. In it I load some pictures from the HDD and run some checks over it. It works fine. Then I have migrated it to LabView 2010, I get a message that the migration is successfull, but when I run the VI on LabView I get a fail status. I have been checking my program and I have found and error when I try to load the picture from file: Error -1074395995 occurred at IMAQ ReadImageAndVisionInfo
Possible reason(s): IMAQ Vision: File not found.
But I am not sure which file it refers to. At first I thought it was the picture I wanted to load, but I have checked the path and it is correct, so maybe it refers to another thing. What puzzles me most is that it works perfectly on Vision Builder and I have changed nothing in LabView, maybe it is a problem with the migration. Any clues?

Here's a screenshot of what I'm talking about. Put a break point here and see what the path is and compare that with what Vision Builder AI is using (described where to find this in the previous post). You could find where this global is used to make debugging easier.
Hope this helps,
Brad
Attachments:
Generated Code.png ‏43 KB

How to handle a LabVIEW error in TestStand cleanup code

When a LabVIEW VI in TestStand's main sequence (Main) has an error, I would like to access this error cluster in the TestStand clean up sequence (Cleanup). It the error cluster information stored somewhere?
Solved!
Go to Solution.

The problem is that the Cleanup section cannot see that Step.Result.Error.
In order to pass that Step.Result.Error information to the Cleanup section, I could copy it into a StationGlobals variable I create, but I would have to do that for every LabVIEW module in the Main section. I'm hoping that information is automatically available to the Cleanup section without me having to add code to every single LabVIEW module in the Main section.
Is that Step.Result.Error information available to the Cleanup section somewhere without me having to add code to the Main section?

LabVIEW error 10899 when testing a virtual channel

I am setting up a virtual analog voltage output channel in the "Measurement and Automation Explorer". I am able to get throught that process and it shows up under "Traditional NI-DAQ Virtual Channels" on the left. When I right
click on the channel and then go to "Test", I get the message "Error - 10899 occured at AO group config".
Sometimes when clicking on test, the MAX crashes and a random window from LabVIEW pops up on the screen. Then I
have to open the MAX again.

Hello bberma01,
I don't like to give you this type of answer, but in this case I think the best think to do is to unistall and reinstall your driver. While we are at it, DAQmx is the newest driver and is very user friendly. I would suggest using it for your data acquisition development.
If you need to download the driver, you can find it Here

Labview error 2500

Hello all,
I am trying to read a channel from a TDM file and send the data continuously over an analog port. This seems to function when I have only one analog output but when i try to use two channels, it shows an error 2500. This error is not part of the documentation and the exact message at my end is:
Invoke Node in _saveFloat64Channel.vi-
I am using Labview 8.0 with DAQ 8.3.1. The hardware in question is the NI USB 6251.
Please advise.
Regards,
Shailesh.

Things you can improve,
1. Start the AI task probably just before you start the AO task, else if the read from file and genration takes time, you may get buffer overflow error.
2. Change the AO write to N Channel>>Multiple Samples>> 2D Double/ 1D Waveform depending on whether u are using Double or waveform data type.
3. The error that you mentioned in the first post is most likely to come from the TDM write inside the while loop. There may be other errors, but you may be getting only the first one. So it will be a good idea to put a probe on all the three error wires inside the while loop and se if you are getting in in them or not.
4. Inside the while loop after AI Read, the DBL conversion is not required. You can remove it.
5. I am not very sure what you are trying to do in the file read part?You can use array of DBL only if the number of elements that you read from the file and the number of elements from the lookup table are same. Else it is better to use waveform.
Can you try these things and let me know?
"A VI inside a Class is worth hundreds in the bush"
യവന്‍ പുലിയാണു കേട്ടാ!!!

Using cin node in labview error happen

my name is Juan Chen , I wish to use cin node to calculate crc check code in la view. I use an array as input and a unsigned word as output. when I use while loop, error not enough memory or the memory can only read happen. what is the reason,please.

how to use the call library function node ? in vcplusplus6 environment , if I only do rebuild all that can generate a dll, and don't use command to convert to lsb file. could I need add files cin.obj, labview.lsvb,etl to the project ?

LabVIEW Error in DLL with pointor

Hi,
Sorry for my very very bad english....
I developped a DLL in Visual C++. In this DLL, I call functions with pointors like parameters. The DLL works very well under Visual but when I call it under LabVIEW 7.1, LabVIEW gives an error when a pointor is read or modify.
Can someone help me? Thanks
Bonjour,
J'ai développé une DLL sous Visual C++. Dans cette DLL, j'utilise des sous-fonctions en leur passant des pointeurs. La DLL fonctionne très bien sous VIsual C++ mais sous LabVIEW 7.1, LabVIEW retourne une erreur (l'exécution s'arrête) quand la DLL veut modifier ou lire un de ces paramètres.
Avez-vous déjà rencontré ce problème et avez-vous réussi à le résoudre? Merci

Ok Dynamik, I understand your answer. I knew these properties for "Call Library Function". The pointers aren't in LabVIEW but in the DLL: I pass under LabVIEW an parameter with "Type" adapt to the type in LabVIEW (I have a French LabVIEW and it says "Adapter au type"). This parameter is a cluster of clusters. In the DLL, it becomes a structure of structure with the same order as the cluster.
Then, I pass the address of this structure in an other function of the DLL for modify it.
Perhaps, it isn't a pointer's problem but an problem of cluster transfert. What do you think?
Attachments:
DLL call.JPG ‏356 KB

Eurotherm 3216 labview error

Similar Messages

Maybe you are looking for