Error -1073807253 occurred at VISA Read in transient SR830.vi VISA: (Hex 0xBFFF006B) A framing error occurred during transfer.

Hi,
I am have written a program with labview to make transient c-v measurement using a stanford research SR830 lockin amplifier. The program seems to be runing fine, but sometimes it is givvibg an error:
Error -1073807253 occurred at VISA Read in transient SR830.vi
Possible reason(s):
VISA: (Hex 0xBFFF006B) A framing error occurred during transfer.
Error -1073807253 occurred at VISA Read in transient SR830.vi
Possible reason(s):
VISA: (Hex 0xBFFF006B) A framing error occurred during transfer.
but if I press ok, the program again starts running. What might be the poblem? BTW I googled a bit and I see that in the labview topic "RS-232 Framing Error with HP 34401A Mulitmeter" by pkennedy32 this is what is said about framing error:
""Framing Error" in an RS-232 context means a very specific thing - when the receiver was expecting a stop bit, the line was not in SPACE condition. This can be the result of:
1... Baud rate mismatch (although other problems would likely crop up first).
2... Data Length problem, If I send 8 data bits and you expect 7, the stop bit is in the wrong place.
3... Parity setting mismatch - If I send 7 data bits + parity and you expect 7 data bits and no parity, the stop bit is in the wrong place.
4... Mismatch in # Stop bits - If I send you 7 Data bits + parity + one stop bit, and you expect 7 data bits + parity + TWO stop bits, the second one might not be correct, although most devices do not complain about this.
But, I must say that this is the same com port setting that I use to measure c-v hysterysis, but I never gt this error there.
I attach the program herewith for your kind perusal. Please help me resolve this issue.
Thanks in advance.
Solved!
Go to Solution.
Attachments:
transient SR830.vi ‏94 KB
csac.vi ‏8 KB
sr830 initialize1.vi ‏15 KB

@Dennis Knutson you are right I checked the read indicator in backslash mode, and instead of a \n it is sending \r. So I changed the \n in my write strings to \r. But, if I keep the CLOSE VISA outside my loop instead of inside as you suggested, the termination character appears to come in the middle of the read string instead at the end. And since the read terminates at the \r so it is displaying some junk value before the \r, but if I put the CLOSE VISA outside the loop and play along with the bytes at the read buffer, I see the whole read string with the \r at the end of the string. But, whenever the values are in exponential form (when close to zero) like 6.938839 e-5, I always get a time out error whatever be the timeout that I put at the VISA initialize. And subsequently, if I stop the program and run it again the machine program hangs and I donot get any reading. Then after I close it again and start, sometimes it hangs for some more or starts working. If I put an arbitrarily large byte count at the READ VISA, then I always get the time out before the operation completed error.
@ Ravens Fan I have removed the CSAC VI altogether and taking the CH! And CH” reading separately, instead as one string. So, no more issues with that.
I use the control at the delay so that I can choose how much delay I want to set, and I use the math operation because I am using adding up the delay time to keep track of the time elapsed. Because in the end I have t plot a time vs. CH! And CH” readings.
I am not sure but probably I am making some silly errors. Please help me out.
Attachments:
transient SR830-2.vi ‏103 KB
sr830 initialize1.vi ‏15 KB

Similar Messages

VISA: (Hex 0xBFFF006B) A framing error occurred during transfer when read write done in lab view

Hello LabViewians,.
I am getting this error. when i run this program in lab view7.1 the data i'm sending it not read but it read randomly any character . So, please help me out great minds out there. .
Thanks,.
rajesh
Attachments:
read_frame.vi ‏485 KB
read_frame.vi ‏485 KB

Framing errors usually indicate you have a problem with the serial port settings used, such as parity, data bits, or stop bits. Verify the values you use in your VI match what the instrument is expecting.

VISA Read over USB Problem: After a while the xBFFF0015 Timeout Error occurred

Hi,
I have trouble using labview with my non-NI USB device:
The device is an analog input DAQ board. I was able to setup communication with the board using a VISA driver specifically created for this board and direct FW calls using the product's firmware specification provided by the manufacturer.
This method has been working pretty good so far, but when I try to get large amount of data (64k samples @100ksps), the VISA Read returns the 'VISA: (Hex 0xBFFF0015) Timeout expired before operation completed.' error.
Please see the attached screenshot of the block diagram for details.
First, an 'analog input scan start' command is sent to the DAQ device, and then the vi tries to read all collected data from the device, once the right amount of data retrieved, or no more data is available the data collecting process (the while loop) ends and an 'analog input scan stop' command is sent to the DAQ device.
The data collection starts with no problem, but after a while, in loop# 400, the VISA Read hangs and then returns the error mentioned above.
I tried to increase the time out value, but it didn't help, the error occurred after the same number of loops, the VISA Read got hosed and the error occurred after the longer timeout expired.
I also tried to add some delays in the loop, but it didn't help either.
I am not sure what do I miss here and I would highly appreciate if anyone could give me some guidance how to solve this issue.
Thanks,
John
Attachments:
usb-read.png ‏18 KB

I just wanted to specify that this is not an NI board avoiding to make people think this is a hardware issue. And I think that the rest of the code is irrelevant in this case.
I believe that I don't use the VISA functions correctly. I assumed that someone who used these functions before would be able to point out the obvious steps missing in the data collecting process using the VISA functions.

The vi is identifyng the number of bytes to be read but the VISA Read vi is not able to read the data from the port.

We are trying to communicate with the AT106 balance of Mettler Toledo.The VI is attached.
We are sending in "SI" which is a standard command that is recoginsed by the balance. The balance reads it.The indicator after the property node indicates that there are 8 bytes available on the serial port. However, the VISA read VI fails to read the bytes at the serial port and gives the following error:
Error -1073807253 occurred at VISA Read in visa test.vi
Possible reason(s):
VISA: (Hex 0xBFFF006B) A framing error occurred during transfer.
The Vi is atttached.
Thanks
Vivek
Attachments:
visa_test.vi ‏50 KB

Hello,
You should also definitely check the baud rates specified; a framing error often occurs when different baud rates are specified, as the UARTs will be attempting to transmit and receive at different rates, causing the receiving end to either miss bits in a given frame, or sample bits more than once (depending on whether the receiving rate is lower or higher respectively). You should be able to check the baud rate used by your balance in the user manual, and match it in your VI with the baud rate parameter of the VISA Configure Serial Port VI.
Best Regards,
JLS
Best,
JLS
Sixclear

Error 1073807253

Hi guys!
I´m back with another question. When I try too recieve my my signal in the waveform chart a get an error It says: "Error 1073807253 occured at VISA Read in Basic Serial Write and Read.vi Possible reason(s): VISA: (HEX 0xBFFF006B) A framing error occurred during transfer". I recieve the signal but every now ang then this messeage comes up. I read from the serial port. I´m using the example "Basic serial Write and Read" from "Hardware Input and Output". I´ve tried to put a flush buffer in this example after the Visa configuaration but this won´t help. And I´ve already checked that the configuaration (baud rate, stop bit, flow controll etc) is matched I hope someone can help me.
Thanks

Hi again...I send you the code and give you a picture of the front panel...
Thank you for your time!
Attachments:
Error_picture.JPG ‏138 KB
Basic Serial Write and Read1.vi ‏64 KB

How to run vi continuously when VISA read timeout happens

Hello,
I am using LabView 2010 to read an Agilent 6000 series Oscilloscope. The Oscilloscope reads data from another experimental machine which fails occasionally due to sample failure. When the machine fails, it stops sending signal to the oscilloscope and leads to the VISA read timeout error and the whole vi is terminated. Is there a way that I can continuously run the vi when the error happens? For example, when the error happens, it stores the error in the error wire. When the vi read the error code from the wire, it sends a command to stop my experimental machine then stop the vi.
So far, it just simply stops during executing the visa read function. In this case, why do we have error in and out? The vi simply stops when the error happens.
Thanks
Lawrence
Solved!
Go to Solution.

I'll start of with automatic error handling. By default, LabVIEW enables the automatic error handling. So consider the case like the one below,
If let's say the VISA Read returns an error, but you did you pass the error information to VISA Close, what will happen is that LabVIEW will highlight the VISA Read (since the error comes from that function), pause the execution at the VISA Read and an error dialog box will appear. From the dialog box, it will prompt to either continue (Move on to the VISA Close) or stop (LabVIEW will stop the VI at VISA Read)
Now, consider another scenario like this,
By passing the error information from one function to another, let's say if VISA Read returns an error, that error will pass to VISA Close and finally to Simple Error Handler.vi. So Simple Error Handler will generate error dialog box after all the VISA operation is completed. This is called manual error handling (It can be enabled by just wiring the error information from one function to another and terminates at Simple Error Handler).
http://www.ni.com/gettingstarted/labviewbasics/handlingerrors.htm
As for VISA Close, here is the information about VISA Close.
http://zone.ni.com/reference/en-XX/help/371361K-01/lvinstio/visa_close/
See that button on the left side of this post...
If you feel my post is helpful, all you need is just (at most) 2 seconds to click that button, to show your appreciation. Thank you~~

Parity error occurs in VISA read when building an executable

Hi,
I am doing some serial communication in LabVIEW and have battled for a long time with parity error where it appeared as a lot of 0's were added to the data I read through VISA read. I fixed my problem according to this description:
Can I Do 9-bit Serial Communication Instead of 7 or 8 bits?
Where i modified the visa ini file to disable error replacement. This seemed to help out the problem - at least i got the data i expected, until i built an application.
When i build and EXE the problem occurs again when i run the application on another computer - not the computer on which it is built. I have made sure to include a customed configuration file, i.e. to include the modified visa.ini file to make sure that the error replacement is disabled in the application as well. When i look in the configuration file that follows the application it also appears as if the error replacement is disabled, however, it seems not to work since a lot of 0's are once again filled into my dataset.
I have of course made sure that the serial port setting are set up correctly.
I am using LV2013.
Anyone tried this before or is able to help somehow?
Thank you
Nicolai

Sure, I have attached my VI - however i'm not sure it provides any useful information in this case. What I am doing is simply reading a serial port every 750 ms, accessing specific data in it and plotting in graphs. The VI works perfectly fine on the development computer.
I don't think the VI or the serial port are what's preventing me. It seems like the configurations in my visaconf.ini file are not transferred to the deployment computer. I have tried the following from the knowledge base:
How to Include VISA Settings in a LabVIEW Installer
Why Does Serial Communication Not Work on my LabVIEW Deployed Executable?
Storing VISA Aliases and Moving Them to Another Machine
I can also see that the 'DisableErrorReplacement' parameter is set in the .ini file that comes along with the application, but it seems like it is not applied since I keep receiving all these annoying 0's that ruin my data.
As you can see in the VI i configure my serial port in the 'false'-state, and then on the development machine I have just added 'DisableReplacementError=1' to the visaconf.ini file which solved my problem before trying to distribute the app.
Hope some of you guys can help.
Best regards
Nicolai
Attachments:
Read datablock.vi ‏55 KB

Visa Read Timeout Occurs with multiple Reentrant VI Calls

I have written a test application in Labview (6.1) which will be used to test (burn-in) up to 15 serial instruments through a 16 Port USB->RS232 Hub. Here's how it works:
When the App loads, I am transmitting a Connect command to each of 15 com ports (one-at-a-time) using VISA. If I receive the proper response from the unit on that port, I add the port to an array and continue on to the next system. Once I've found all systems on the hub, I wire my array of active Visa references to a for loop in which I open up to 15 reentrant VIs which will run in the background in parallel. Each of these reentrant VIs (all are idential with the exception of the Visa Resource they use) running in the background are sending commands to the the respective instrument and receiving a response. One Function in particular "Get Unit Status" is important and the response determines whether or not the instrument is functioning correctly. Here's the problem -- In my Main Loop, I am continuously acquiring indicator values from each of the reentrant VIs that are running in the background. After a period of time (not consistent) I will lose communication with a port (the symptom is no response from the unit). I've looked closely at the COMM engine I created and found that the Visa Write function is completing without error, then when I perform a Visa Read I immediately get the "Timeout occured before operation completed" error (please keep in mind that this occurs after 100-5000 successful attempts at writing/reading). Eventually another port will drop out, followed by another. This seems to stop occurring and the remaining systems run to completion without a problem.
Some background on what how I'm setting up my Visa Sessions...
When I originally scan for systems (before I load and run the Reentrant VIs)
- Init Visa Port
- 19200, 8, N, 1
- Use Termination = True
- Timeout = 400mS (I've tried larger values already) 400mS should be plenty
- Termination Char=13 (/r)
- Open Visa Session
- Visa Write "CONN18/r" (the command required to connect to my instrument)
- Visa Read with 1 for requrested byte count to read 1 byte at-a-time, concatenating the results until /r is received (or 1000mS timeout occurs -- this is not a VISA timeout) I've also tried 16 for requested byte count and just waiting for Visa to timeout -- both methods work.
Once all 16 ports are scanned I Close ALL of the ports using the Visa Close Function.
It is important to know at this time that I "AM" using proper wiring flow to ensure open occurs before write, write occurs before read, etc.
I'm assuming at this time that all of my Visa sessions are closed.
On to the Reentrant VIs:
Inside each reentrant VI I first Initialize all of my variables and Init/Open a 'New'? Visa session using the same parameters mentioned above.
Then I enter the "Run" case structure where all of the communication begins.
I am using the same Communications Engine to operate the instrument as before (the only difference being that all of the VIs in the comm engine are now reentrant and operate at higher priorities) I have actually saved two different versions of the engine (one for the reentrant calls and one for when I first scan for systems from my Main GUI).
When I init the reentrant VI, I am placing the Duplicate Visa Resource output of my Visa Open Function on a shift register. When I enter the Run case, it takes the Resource from the register on the left, wires through any Comm Engine Vis then back out to the shift register on the right and keeps going for a 12-hour period or until "Get Unit Status" has returned 60 naughty results.
On my Main GUI I am continuously (every 500mS) I am Getting certain Indicator Values from each reentrant VI AND I am also setting some control Values on each reentrant VI. There is no VISA interaction between each Reentrant VI, and the Main GUI.
As I said earlier, up to 15 systems will run for a time, then one will stop responding, followed by another, and another until a few remaining systems will run to completion.
Any advice as to why I'm encountering the timeouts with the VISA read fucntion as I have metioned would be appreciated. I managed to find one suggestion which uses the Bytes at Port function to ensure there is data at the port before doing a Read otherwise, skip the read and retry the whole operation -- I haven't tried this yet.
Sorry for the wordiness of my question. If anyone would like some screen shots of portions of my code (I can't submit the actual code because some of it is confidential) I'd be happy to post them.
Doug.

Hi Doug,
The first thing I would recommend is the solution you have already found, to check and see if there is data at the port before attempting a read. I would be interested to see if this will solve the problem. Does there seem to be any trend to which ports have this timeout error? How many ports does it cut down to before operation seems to continue as expected? Does this number vary, or is it always the same number of ports? I think the best thing to do will be to identify constant attributes of how the error is occurring so that we can narrow it down and see what is going on.
John M

Error 56 occurred at TCP Read in MB Ethernet Receive.vi

My sensor uses MODBUS TCP and operates as a slave device. Currently I'm using Labview 7.1 on my PC and would like to communicate w/ sensor as a Master. I downloaded MODBUS library from ni developer zone. I want to read 14 discrete outputs (coils). I believe MB Ethernet Master Query.vi is most appropriate to use for my application. I put this block into my *.vi inside of a while loop, hooked up the connection ID, configured it with address start/quantity, and ran. The error I got says: "Error 56 occurred at TCP Read in MB Ethernet Receive.vi->MB Ethernet Master Query.vi->...*.vi". I have confirmed that TCP is working with Labview because I can receive other non-MODBUS sensor data from my device via TCP/IP using a different *.vi I created. However this data is received though a different port than the typical 502 MODBUS port. I have also confirmed MODBUS is working on my device using a 3rd party Polling Utility that reports register status.
I currently do not have NI-VISA 3.0.1, VISA Server 3.0.0, or Measurement & Automation Explorer (MAX) version 3.1.1 installed on my PC. Do I absolutely need these products to do what I need to do?
Any thoughts why I am not able to get this setup working?
Also, I am embarking on developing several MODBUS applications after this. Would it be a good idea to upgrade my version of Labview to gain more MODBUS functionality w/ Labview? I'm somewhat new to Labview and am a little confused on which products would really help me for working on MODBUS applications and if those products are compatible with my 7.1 version.

Hi cwallis2,
If you can use TCP/IP in Labview then you should be okay as far as that is concerned. The Ethernet Modbus VIs use LabVIEW TCP VIs underneath; the Serial Modbus VIs use VISA underneath. So unless you want to try the serial VIs if that's a possibility, then you should be okay without VISA.
The error 56 is a time-out error and is generated when an operation
exceeds the user-specified time limit. This error is caused by the
LabVIEW code not receiving a network response in the defined time
limit. The default time-out limit is 5 seconds, which should be enough,
although you can increase this time-out value as an input for the MB
Ethernet Master Query.vi. Since you get the time-out when you are
reading instead of the initialization lets us know that you are able to
open the TCP port correctly.
What is the address you entering into the MB Ethernet Master Query.vi in the Modbus Command constant? You may need to use relative addressing instead of absolute addressing, or vice versa.
Hope this helps!
Adam W
Applications Engineering
National Instruments

Visa Read Issue Code -1073807253 - myRIO - PmodGPS

I'm very new to LabVIEW. I'm a senior, so I have had two measurement classes that used data logging equipment. I have had my hand held twice creating new programs. I just bought my first myRIO and I'm trying to datalog gps at 10 hz.
With the help of a few on here, I have been able to switch the Baud rate (I believe) but now I'm getting the Visa read error code 1073807253
I have attached my full program, but below are screen shots of things I have changed. The initial program worked fine at 1 hz, so I know the problem isn't the code itself, but it relates to what I'm changing. I did a bunch of searching and I found this page http://digital.ni.com/public.nsf/allkb/F3E0621CB71AA16786256F970000FC57 that talked about adding a buffer in the system.
I added the pause but that by itself didn't do anything. So, then I completed the modification and added the buffer.
That still resulted in the same error. After doing quite a bit of additional research, I found where someone said they just ignored the error. So, I gave that a shot and added an ignore error code.
Now the program runs without throwing up the error, but it isn't running correctly and it isn't running at 10hz. See the NMEA coded is it now displaying below.
Anyone have any ideas? I'm really stuck on this one and I'm behind schedule on completing this project. Any help is greatly appreciated!
Attachments:
Main.vi ‏94 KB

Ok, So, I got ride of the buffer and error ignore and went back to what I was using before.
I added in the close and put in a new Visa Config. I connected the error out of the Visa close to the Error in of the Config. Do I need to do that?
As you expected, the time between samples is still 1 second. Thoughts?

ERROR 1073676294 ????? VISA READ...!!

Dear All
I am Writing and Reading the data from one EEPROM,interfacing with a PIC16F690,like this i am swiotching 240 EEPROM with MUX,through LabVIEW serial communication pallets,I am controlling the Reading/Writing, but some times ERROR 1073676294 ????? VISA READ...!!,once this error occurs next all EEPROM chip are not able to READ /WRITE,if unplug the powersupply and plug it back,then LabVIEW can Read/Write,i am not able to fix this error,please advise me whether problem is from LabVIEW or MICROCONTROLLER,I used delay function but also same problem.
Raikar A G

1073676294 is not an error but a warning saying that you got exactly the number of bytes you requested in the Visa read, and that there might be more bytes still remaining in a serial buffer. (Which I've always considered this a stupid warning, because as a programmer, I'm going to assume that there might be more data in the buffer than I have just pulled out.)
The warning should not cause any problems in your LabVIEW code, nor should it cause a problem with your serial communication. So if you lose communications with your microcontroller, it must be something else going wrong.

NI VISA read stops at zero character, returning an 0xBFFF003E error

Hi
I’m trying to read some serial data from a UUT using the NI-VISA read function. The data is mostly text but does include some control codes. The first of these appears after the ‘OK’ in the Serial Bytes window on the front panel. More text should follow but for some reason, the read function stops at the first zero character (index 144 in the Byte Array), and returns an 0xBFFF003E (-1073807298) error. I found another thread where someone had a similar problem and I’ve tried the fix for this plus a few other things, but nothing’s worked. If I use Hyperterminal, the entire data block is returned as it should be.
I wondered if this was anything to do with the 7.1 version of Labview I’m using (upgrade is on the cards). The version of NI VISA I’m running is 4.2.
Very much appreciate any thoughts.
Thanks
Bruce

The error code itself is a generic VISA error which often happens with USB to RS-232 interfaces. Does your device connect to the PC through USB as a virtual COMM port? If so what chip and Windows driver is it using?
Also your function somehow looks wrong. The only criteria for the read loop to terminate is if there is an error on the VISA read or the Teststand termination status gets true. Generally if you use VISA Bytes at Serial Port you are almost always doing something wrong! That function does absolutely not synchronize with anything in your data. You will read whatever is there at that moment and that could be a partial message, no bytes at all (LabVIEW is typically many times faster than any serial device even if it is super high speed), or multiple messages.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

How do I avoid Error 85 in Scan From String scanning VISA read buffer?

I have encountered an Error 85 with my Scan From String VI. I have a timed
loop to read data from a device (flowmeter) using a serial port. This device takes
periodic measurements and sends the reading which contains a numerical value to the serial port COM1. It cannot be read continuously, and the period
between measurements may vary, so I decided a timed loop would be better than a while loop.
The VI begins with VISA Configure Serial Port and then
goes to a VISA Write which sends the message to the device to begin
taking measurements. After this, the device usually says "TAKE FLOWMETER READINGS" to the terminal, thereafter only sending numbers. Then begins my timed loop containing VISA Read. I
am taking the read buffer two places.
First, I am taking it to an Array to Spreadsheet String with the
Format String %.3f, as was in the Write to Text File example. Then I am
using Concatenate Strings with this string and also a string containing
the System Time. This string goes to Write to Text File, which I have
configured using Open/Create/Replace File outside of the loop.
Second, I am taking the read buffer to a waveform chart. I thought
it would be a good idea to use Scan From String to convert the string
into a DBL which I am then sending to the waveform
chart.
I am not sure if the initial "TAKE READINGS" message is giving me an error. I was able to get one reading saved to my text file from the device.
Also the format string for my Scan From String is %.3f
I am getting the Error 85 at the Scan From String only sometimes.
When this happens, there is no data being written to the text file. But
other times, I get data and it writes to the text file just fine (but
rounds to nearest whole number).
Any help would be greatly appreciated! This serial port device has been giving me a lot of trouble.

Is this what you mean? Did I wire the shift registers correctly?
I didn't know if you meant to Concatenate before Scan From String or Concantenate before or after VISA Read?
Message Edited by YeungJohn on 11-20-2008 03:48 PM
Message Edited by YeungJohn on 11-20-2008 03:49 PM
Attachments:
SerialShiftVI.JPG ‏87 KB

An internal error occurred in adobe reader

an internal error occurred in adobe reader.

I was frustrated by this problem as well. I even uninstalled and then resinstalled a fresh download: SAME Problem.
Now the problem seems to have been RESOLVED on my Windows Vista Laptop.
Instead of trying to open by double-clicking on file icons, I opened the Adobe Reader from the Windows Explorer. On the first screen appeared the usual Adobe Licence & Terms that I had to ACCEPT. This screen NEVER showed up before after either upgrading to the Adobe Reader X or after reinstalling. After accepting the License and TERMS. this problem does NO longer reproduce.
I have successfully opened fewer than 10 PDF files without the annoying error so far. I hope others will reproduce this "FIX" before claiming this was the root cause of the problem.
Hopefully Adobe will display a more meaningfull error message for such a problem.

Suddenly, I am seeing an error message that reads: "The iTunes Library cannot be saved. An unknown error occurred (-54)". Can anyone tell me what that means?

Suddenly, I am seeing an error message that reads: "The iTunes Library cannot be saved. An unknown error occurred (-54)". Can anyone tell me what that means? Am I in danger of my iTunes library being lost?

== Error -54 ==
From an OS9 reference, error -54 is a software lock on a file or a permissions error. (Some of the old codes still apply to OSX although there is no formal list of OSX error codes.)
First, try simply restarting your computer.
iTunes Library cannot be saved (Error -54) - https://discussions.apple.com/thread/1912814
Unknown error (-54) while syncing ipod - https://discussions.apple.com/thread/1082953 - problem was locked files
Why does iTunes keep showing a -54 error when I sync my iPad? - https://discussions.apple.com/thread/3727114
Error -54 possibly related to Touch Copy - https://discussions.apple.com/thread/3727114 - cleared by deleting preferences on iPad.

Error -1073807253 occurred at VISA Read in transient SR830.vi VISA: (Hex 0xBFFF006B) A framing error occurred during transfer.

Similar Messages

Maybe you are looking for