Thermistor conversion formula is wrong?

There is a VI found in the DAQ>>Signal Conditioning subpalette called "Convert Thermistor Readings" (I have LabVIEW 5.1.1 and 6.0.2). There seems to be some blatant inconsistency with the thermistor formula inside.
The standard thermistor formula is 1/T = a + b(lnRt) + c(lnRt)^3. (This agrees with all the documentation I've seen, including within this VI!) However, the formula node contains a different equation:
T = 1/ (a + lnRt*(b + c*(lnRt**2)));
Note the bracket position around the 'b' and the exponent '2' vs the '3'.
What gives?

David,
Equations written in plain text are always hard to get a grip of. However, I guess the two equations you mentioned,
1/T = a + b(lnRt) + c(lnRt)^3
and
T = 1/ (a + lnRt*(b + c*(lnRt**2)))
are identical.
First invert the second eq. and multiply lnRt with c*(lnRt**2) in it. You will then get the first equation since
lnRt*c*(lnRt**2) = c(lnRt)^3.
I guess the confusion is that
lnRt**2 =(lnRt)^2 and not ln(Rt^2).
Hope this helps. /Mikael

Similar Messages

Multiple Unit of Measure (No Fix Conversion Formula)

Dear All,
Cilnet has given me requirement to book the sales document for the particualr product in unit of mesure 'Nos/PC', and the stock is maintained in Base Unit of Measure 'Qtl' (100 Kg = 1 Qtl). Price is also applicable or calculated on the basis of QTL but there is no fix conversion formula of 1 PC = How Many QTL.
Please guide me on this point.
Regards
Rahul

Hi,
I was facing the same Problem ,well for this you need to define a character and associate the same to a Class .
And Finally need to assign Combination of these to material in material master classification view.
Define Charter :
http://wiki.sdn.sap.com/wiki/display/PLM/Howtocreateacharacteristic
Assign the Char to Class :
Tcode : CL02
Under Char Tab Give the Charcter Name and Place "S" in Org. Area.
Thanks.
Edited by: C.Ankit on Mar 7, 2012 8:18 AM
Edited by: C.Ankit on Mar 7, 2012 8:18 AM

FX conversion formula [AS_IS]

Hi all,
I am having a bit of a problem with the currency conversion in a consolidation application.
I have a flow F_OPE which is the opening balance, it is the only flow marked as OPENING. In my currency conversion business rule I have defined that OPENING is converted [AS_IS] with no specified target account and flow. (According to the SAP HELP
[AS_IS]: Leave untouched a value already existing in the destination currency.
As a first step I enter data onto another flow F_ADD which is converted at the average rate from LC to KONZ ( my currency dimension is called CONSOLVIEW and KONZ is defined with CURRENCY_TYPE G and GROUP_CURRENCY EUR.). This works fine. As a second step I copy my opening balances, which copies the values in LC and KONZ from F_TOT (which includes F_ADD where I have just entered data) into the next year and onto flow F_OPE. This works absolutely fine. When I check via an EVDRE or in MS SQL I can see both values.
I then run the currency conversion (*RUN_STORED_PROCEDURE=SPRUNCONVERSION('%APP%',[%CATEGORY_SET%],[%ConsolView_SET%], 'GLOBAL','%SCOPETABLE%','%LOGTABLE%')).
If I then check via an EVDRE there is no converted value on F_OPE. Checking in MS SQL I can see that the original value from copying is still there, but the currency conversion has created a new entry with the same value but the opposite sign, so the total is 0.
I was expecting the system to not do anything for F_OPE on currency conversion. Was this a wrong expectation or am I doing something wrong?

found the problem, I misunderstood the use of currencies

Conversion formulas from RGB to CMYK

Hi,
I've been writing a Colour swatch tool (in excel! hell yeah!) which allows me to pick a bunch of colours, generate complimentary colours from them, blend between 2 colours in a set number of steps and a whole bunch of other cool stuff, and then output this as a photoshop or illustrator swatch file.
As part of this tool I want to be able to covert the rgb values to cmyk. There is very little information on this on the web and what there is is fairly inaccurate.
For example,
RGB:50,128,128
Converts to CMYK 61,0,0,50 (%) using the formula found at easyrgb.com (this formula is the most prevalent one on the web/web forums)
Photoshop converts these RGB values as CMYK: 80,33,48,8 (%)
While these two colour values are *similar* the ones generated by the easyrgb formulas are nowhere near the photoshop values.
See? stupid useless formulas. (I am aware of the differences and overlap of the two gamuts)
Whilst I know that the conversion done in photoshop is done using ICC templates, and that often these conversions are device dependant, there must be a more realiable way of converting from one colour space to another using good old reliable cold hard maths.
Does anyone know what that might be? you guys at Adobe: I AM LOOKING AT YOU.
Hope you guys can help,
~silvery~
For reference I have included and commented the easyrgb formulas:
First: RGB -> CMY
C = 1 - ( R / 255 )
M = 1 - ( G / 255 )
Y = 1 - ( B / 255 )
Second: CMY -> CMYK
var_K = 1
Initally sets var_K as 1, although this is dependant on variables below
if ( C < var_K ) var_K = C
if ( M < var_K ) var_K = M
if ( Y < var_K ) var_K = Y
This bit finds the smallest value from the CMY range and sets this value as var_K
if ( var_K == 1 ) { //Black
 C = 0
 M = 0
 Y = 0
If var_K (the value that K is calculated from) is 1, then all the CMY values are reset to 0
else {
 C = ( C - var_K ) / ( 1 - var_K )
 M = ( M - var_K ) / ( 1 - var_K )
 Y = ( Y - var_K ) / ( 1 - var_K )
If the value of var_K is anything other than 1 then use the smallest value from the CMY range
K = var_K
The value of K as filtered out from the conditions above

Oliver,
I'm not sure what you mean by the term 'meta' color profiles, but I'll take a stab at what I "think" you are asking. There are some fairly widely accepted "standards" out there for both RGB and CMYK.
In the RGB world, for example, sRGB, Adobe RGB (and to some extent, ProPhoto RGB) have a fairly wide following. These are all ICC profiles, which nail down the boundaries of the color gamut and the definitions of any tri-stimulus combination of red, green and blue. Basically, they are matrix profiles that establish the positions of the Red, Green and Blue primaries, and these positions define the outer limits, or color gamut, of the color space. sRGB is a relatively small color space, so some viewable and printable colors get clipped (sRGB is the general internet, email standard and is widely assumed for many non-color managed appplications, printers, etc). sRGB can handle a fairly wide range of colors, but does clip some colors in brightly colored originals. It has the advantage of being the most widely adopted standard, plus the steps between colors are very close together. I use sRGB for average images, most people pictures, etc. Adobe RGB spreads the primaries further apart, so it describes a wider color gamut. Because the primaries are further apart, the steps are slightly larger from one color to the next, but marginally so. I use Adobe RGB for most of my brightly colored images that will get clipped in sRGB. Adobe RGB is also generally a good choice for images that will ultimately go to a printing press or inkjet. ProPhoto RGB pushes the primaries WAY apart, so it describes a HUGE color gamut...in fact, many of the colors that can be defined in ProPhoto fall outside human vision, and certainly monitors and printers.Due to the wide spacing of steps in ProPhoto RGB, images should be worked in in 16 bit, otherwide you may see some banding and posterization if large edits are made.
In the CMYK world, certain "standards" have been established, mainly for commercial offset printers (both web and sheetfed presses). By creating a standard, they are trying to establish the ink limit, densities, color gamut, dynamic range, gray balance, etc, of a "generic" sheet of commercial printing paper on the average well-maintained press using standard ISO inks, using good process control, mesurements, etc. By it's nature, this process has to encompass a wide cross section of presses, so it may act as a limitation on what some modern presses are capable of, but that's what standards usually do. If a good printer, with a modern press and great process control decides to sidestep the standard, they can probably extend color gamut, dynamic range, etc, but at the cost of no longer being "standardized". If commercial printers are "truly" trying to meet the standard, they will run tests, take measurements, and adjust their entire workflow so it matches the standard, within acceptable tolerances. Lots of shops "claim" to adhere to SWOP or GRACoL standards, but the majority of them don't. Standards for presses make some sense, because blending CMYK inks together (especially if they use ISO standard inks) on paper usually has a reasonably narrow range that works, though the paper makes a huge difference. (the same cannot be said for inkjets, monitors and many other processes, so they generally do not have standards). So for presses, there are standards for matte and coated papers, web presses, sheetfed presses, newsprint, etc. Each of these standards has its own ICC profile (or a family of profiles) that establishes ink limits, color gamuts, etc.
All ICC profiles have the necessary tags and data to comply with the ICC specification. One of those requirements is a "profile connection space", which is usually L*a*b* or a variant. So, an file on your computer may be tagged as an Adobe RGB file, and if you wish to prepare it for a sheetfed press using glossy stock, you could convert the file to GRACoL2006_Coated1v2.ICC (an industry standard profile for No. 1 coated stock on a sheetfed press). Since both files have the ability to "speak Lab" a translation can be made from one color space to the other. The numbers in the Adobe RGB file will be converted to L*a*b* (the universal translator), and then the L*a*b* numbers will be converted to CMYK, specifically GRACoL2006_Coated1v2.ICC. So, now you have a file in CMYK space with new numbers. It is worth noting that RGB has only three colorants to define colors, but CMYK has four. So, while in RGB there is only one way to define a specific color, in CMYK, there are many possible combinations that can generate many colors. This adds complexity to the equation. The CMY colors are called subtractive primaries, and are opposites of RGB (additive primaries). The "K" (black ink) is added for text, line art, neutrality, extra Dmax, and because the CMY inks are not pure and don't deliver a true black all by themselves. If the inks and paper were perfect, you could theoretically get away with CMY all by themselves, except for registration issues, text, line art, etc. Also, the additional "K" ink can help reduce the total ink limit, save ink, reduce costs, and improve quality.
Sorry for the book. This is not a simple subject, and we have only touched the surface.
Lou

FOX formula works wrong. Why?

Hello,
My scenario:
My planning layout filled with data:
0CMMT_ITEM: 0FM_AMOUNT1 0AMOUNT(data from fact cube)
 A.2.2.2____________0_____________500
 A.3.3.3____________0_____________0
 A.1.1.1____________0_____________0
FOX Code:
DATA CI TYPE 0CMMT_ITEM.
DATA CI_VAL_1 TYPE 0CMMT_ITEM.
DATA CI_VAL_2 TYPE 0CMMT_ITEM.
DATA K. TYPE F.
CI_VAL_1 = 'A.2.2.2'.
CI_VAL_2 = 'A.1.1.1'.
FOREACH CI.
IF CI = CI_VAL_1.
{0FM_AMOUNT1,CI,PLANAREA}={0AMOUNT,CI,FACTAREA}.
K={0FM_AMOUNT1,CI,PLANAREA}.
ENDIF.
IF CI = CI_VAL_2.
{0FM_AMOUNT1,CI,PLANAREA}=K.
ENDIF.
ENDFOR.
After executing this planning function i get result:
0CMMT_ITEM: 0FM_AMOUNT1 0AMOUNT(data from fact cube)
 A.2.2.2 ___________500___________500
 A.3.3.3____________0_____________0
A.1.1.1____________0_____________0
But A.1.1.1 0FM_AMOUNT1 = 0, it should be equal to 500.
For example, if there are some data in columns, not equal to 0 in the A.1.1.1 row, everything works fine; 0FM_AMOUNT1 = 500 with commitment item A.1.1.1.
Could you give me an advice? What i am doing wrong?
Thanks in advance.
Best Regards,
Arunas Stonys

Hello, Sunil,
If i write fox code like that:
FOX Code:
DATA CI TYPE 0CMMT_ITEM.
DATA CI_VAL_1 TYPE 0CMMT_ITEM.
DATA CI_VAL_2 TYPE 0CMMT_ITEM.
DATA K. TYPE F.
CI_VAL_1 = 'A.2.2.2'.
CI_VAL_2 = 'A.1.1.1'.
*1st loop--
FOREACH CI.
IF CI = CI_VAL_1.
{0FM_AMOUNT1,CI,PLANAREA}={0AMOUNT,CI,FACTAREA}.
K={0FM_AMOUNT1,CI,PLANAREA}.
ENDIF.
ENDFOR.
*2nd loop--
FOREACH CI.
IF CI = CI_VAL_2.
{0FM_AMOUNT1,CI,PLANAREA}=K.
ENDIF.
ENDFOR.
In the first loop i get value K and in the second loop i put it into cmmt_item 'A.2.2.2', but there's the same problem: i can't see my value 500.
Value 500 in cmmt_item A.2.2.2 appears just when i manualy put some value in the same row next column.
Best Regards,
Arunas

Currency conversion with the wrong exchange rate type

Hi,
I need a currency conversion in my bex query. I have defined a currency translation key with a assignment to the exchange rate type "M".
When I check the results in the query it works with exchange rate type "EURX".
Exchange rates are in the TCURR.
Can anyone help me.
Thanks in advance
Jürgen

Hello,
We just had the same issue, and in checking the Currencies: Translation Ratios in transaction OBBS, I noticed that the currency translation key in question was set up with an entry of "EURX" in the "Alt. ERT" column.
I copied the line and created a new entry with a "Valid From" date of the current month, but without the "EURX" Alt. ERT alternate and that seemed to solve it.
Anything entered with a date after the new Valid From date would use the manually entered exchange rate, while anything with a prior date continued to use the EURX rate.
It appears to me that the "Alt. ERT" functions more as an override than an alternate, so if you want the system to actually use the "M" rate, I believe you have to ensure there is nothing in the "Alt. ERT" column.
I hope this helps.
Blaine

Date Conversion- Formula

Hi All,
I have Info Object 0DOC_DATE - Data type (DATS ) Length - 8 ; in transfer rules i need to write a formula to convert the date format as MM/YYYY Instead of DD/MM/YYYY.
Please suggest to write formula in transfer rules ASAP.
Thanks

Hi,
DD/MM/YYYY is a display format, the storage is always without "/", you wanna change it to MM/YYYY, means you only wanna to display month rather than whole date, so you can use formula DATE_MONTH to get the month, and it will display as MM/YYYY automatically if you set your own data date format as DD/MM/YYYY.

Trend line formula totally wrong - did someone else discover that?

Values used
14
85
45
59
98
48
175
7
220
-16
regression line formular in Numbers: y=-25.4x+112.8 (way to steep)
regression line in Excel y=-0.4664x+88 (way better)
The regression line in the diagram is displayed correct but the formular (by the way also for non linear regressions) fail.

You have done something wrong.
What I suspect you have done is put your X data into a header column. You should also see that the X axis on your chart is plotting the X values 1 through 5, not your actual X data

BPC Netweaver version - Conversion File Formulas

BPC (Netweaver) Expert,
When creating formulas on the Data Conversion File that is called by the Transformation File, the Formulas are not working on the Netweaver Version. Does anyone have any idea what may not be set up correctly?
Thanks,
Greg Rotvold

Hello Greg,
BPC Netweaver uses somewhat different syntax for conversion formulas, and uses javascript for complex formulas, so formulas written using Visual Basic on the MS version will not work, though the basic *IF logic should work (I think I'm remembering MS conversion formulas correctly, but it's been a while). You can find the relevant Netweaver version documentation here: [http://help.sap.com/saphelp_bpc75_nw/helpdata/en/81/94a8a5febd40268d5c59b4fc31be37/frameset.htm]
If you want help specifically on the Netweaver version I suggest you ask your question in the Netweaver forum. I'm not sure what forum is most appropriate for questions about the differences between the two versions
Ethan

[solved] Video conversion problem: Mencoder on Arch versus Windows XP

I have a cheap portable video player which (according to a supplied Windows software configuration file) requires any video to be converted (say from a YouTube .flv) using a command line like:
mencoder myfile.flv -ofps 15 -vf-add scale=160:128 -vf-add expand=160:128:-1:-1:1 -srate 44100 -ovc xvid -stereo 0 -xvidencopts bitrate=300:max_bframes=0:quant_type=h263:me_quality=0 -oac lavc -lavcopts acodec=mp2:abitrate=128 -o myfile.avi
If I do the conversion on Linux - my fully-upgraded Arch - the resulting .avi file has the audio and video out of sync when played with Mplayer (on Linux and Windows), and no audio at all when played with Vlc (on Linux and Windows). But if I do (supposedly) exactly the same conversion using Mencoder on Windows, the resulting .avi file plays perfectly on everything on both Linux and Windows (and also the portable video player).
Here's the version information for the Mencoders being used:
Windows: MEncoder Sherpya-MinGW-20060312-4.1.0 (C) 2000-2006 MPlayer Team
Arch: MEncoder SVN-r32492-4.5.1 (C) 2000-2010 MPlayer Team
I'd be grateful for any ideas as to how to make my Mencoder conversion work as well on Linux as it does on Windows XP! (Or is there something wrong with the way I'm playing the file with Mplayer and Vlc on Arch?!)
Last edited by ninian (2010-11-16 23:28:02)

Aha! I think I've cracked it, but using ffmpeg instead, with options prompted by this blog post:
ffmpeg -i infile.flv -r 15 -vcodec mpeg4 -vtag XVID -s 160x128 -aspect 4:3 -qmin 3 -qmax 5 -ar 44100 -ab 128k -ac 2 -acodec mp2 -g 1 outfile.avi
This seems to work everywhere, and the writer specially notes that:
The most important option is the -g 1 to force every frame to be a keyframe
which may well be where my conversions were going wrong. So I'll mark this as 'solved' even though mencoder is still a mystery, but I have learned to keep Vlc up my sleeve, so thanks for that tip again.

Want to crate a dynamic formula depending characteristics

Hi experts,
I want to create a query which calculates the following:
I have some products, some factories and the variable month.I want to find what percentage of product A is produced in factory A month by month.(also for product B in factory A, product A in factory B and so on)
The problem is that I can not select the characteristic values in query designer while creating a formula.I also tried to calculate it in workbook but I failed.Because the number of rows and columns is not constant depending which month the user selects.So the formula calculates wrong things as the place of the things changes.
Thanks in advance...
Regards,
Sunny

You will have to create "selections" or "restricted KF" for each factory product combination e.g FAC_A_PRD_A. Using these selections you can build a percentage formula as FAC_A_PRD_A / Total qty.
When you suppress zeros on the query it should only display combinations where qty is not 0.

Formulas for blending modes

Hi,
I want to truly understand layer blending modes so I can use them better and predict their impact. I know from Bruce Fraser's books that the formula for the Multiply Mode is:
result = (top_pixel * bottom_pixel) / 255
This is great for me (I have a BS in Math). The question is: how are the other modes calculated? For instance, i am having trouble figuring out the Color Burn Mode...
Thanks,
Juan Dent

Color burn is a little easier to calculate in CMYK because the numbers are expressed as %
Base % / (1 – Blend %)
For example, bottom layer is 40M. Make a layer above with Color Burn, fill with 50M
.4 / (1 – .5) = .8
The color result is 80M
Because of this relationship, if the base % is half of the blend % the color result matches the blend color:
.25 / (1 – .5) = .5
You could probably arrive at a reliable result using a similar formula in RGB, but the numbers get crunched differently when dealing with 0 - 255
To get multiply in CMYK I always use
(Base % + Blend %) – (Base % x Blend %)
So if bottom layer is 40M. Layer above is multiply, 50M
(.4 + .5) – (.4 x .5) = .7
Perhaps this formula is wrong somehow but it seems to work for me.

Seconds to Time Conversion for Display on a Cross-Tab

Post Author: [email protected]
CA Forum: Formula
I am doing a cross-tab report of login times for hours logged into a system. In the cross-tab if i use the time, I can't sum. So i have the time converted to seconds to allow for a sum and totals. Now I need to change the display of the field to time. When I go to my Format Field of the field in seconds, under Common tab i go to Display String. I put in the following formula: totext((/60)/60,0,"","") & ":" & totext(truncate(remainder(/60,60)),0) & ":" & totext(remainder({Secondin_Logins.T},60),0); My problem is it changes all to report the same time; no time is different. And the formula is wrong becuase when i do the hours if it is .501 or high it rounds up. Anyone have any solutions to convert seconds to Time?

Post Author: V361
CA Forum: Formula
Part of the probem may be the crosstab, any way, this example uses a group but should be generic enough to give you some ideas.
whileprintingrecords;
StringVar Hours1;
StringVar Minutes1;
StringVar Seconds1;
NumberVar time2;
time2:= 0;
if Sum ({Work Time}, ) = 0 then 0 else
time2:= Sum ({Work Time}, );
If time2 <= 0 Then
"00:00:00"
Else
( Hours1:=ToText(Truncate(time2/3600),0);
Minutes1:=ToText(Truncate(Remainder(time2,3600)/60),0);
Seconds1:=ToText(Remainder(Remainder(time2,3600),60),0);
//Display the time formated.
(if length(Hours1) < 2 then '0') + Hours1 + ":" +
["0",""][length(Minutes1)] + Minutes1 + ":" +
["0",""][length(Seconds1)] + Seconds1);

Spot-to-CMYK conversion: Pantone vs. ID

I know this is not a new issue, and was discussed here, but more from the point of view of the visual aspect of colors on one's screen.
I'm baffled as to the conversion of spot colors for printing purposes (sheet-fed).... My client wants me to use PMS 322c in a CMYK job, and she's been always very picky about colors and the way they print. The difference in the conversion formulas between ID and using Pantone's website -- is striking.... See how ID has a significant amount of M, yet low K, while Panton suggests ZERO M and lots of K.... So I'm asking, WHO CAN I TRUST???....

Part of the “problem” is that of how you actually represent the Pantone spot colors. Yes, Pantone provide CMYK equivalent values, but in exactly what CMYK color space? According to what I have been told by Pantone, those CMYK values are nominally SWOP.
You didn't indicate what your full workflow looks like, but the most reliable method of dealing with spot colors, whether used as real spot colors (i.e., you actually have those spot color inks at the press) or you are simulating them, is to pass through the spot color information in the PDF file exported from InDesign or at least as LAB colors otherwise. Preferably, you are using a PDF/X-4 workflow.
Bring in the swatch at follows:
The swatch will then look like:
When you export PDF, you have two choices. If you are actually printing spot color or if you don't know whether real spot color inks are available, set the Ink Manager as follows:
In this case, the RIP will use the spot color if available or if not, it will convert Pantone's more precise LAB color values specified as the “alternate color space” to the press' CMYK color space.
If you know that the press definitely won't have the spot colors, set the Ink Manager as follows:
On PDF export, all references to PANTONE 322 C will be output to the PDF with the exact LAB color values which your RIP will convert to CMYK and no references to the spot color at all.
This is the method getting precisely what Pantone defines for the spot colors and how they will look in process color.
Note that many Pantone spot colors cannot precisely be matched in process color simply because such colors are outside the gamut of whatever process CMYK color space your printing workflow supports.
- Dov

Formula to convert Hex to Decimal

Hello All,
I have "upgraded" from AppleWorks to iWork Numbers. Yes I've read all about how somethings didn't get ported over, etc. What I need is a formula to convert base 16 to base 10. Any ideas how to do this? I see that numbers has a formula editor so is it possible to make up a conversion formula? Someone done this who would like to share?
Thanks,
Dan

Dan,
Here's a brute-force solution. There may be more elegant ones out there.
DEC formula is: =IF(ISERROR(LOOKUP(MID(A2, 1, 1), LOOKUP TBL :: A$1:A$16, LOOKUP TBL :: B$1:B$16) * 16^3+LOOKUP(MID(A2, 2, 1), LOOKUP TBL :: A$1:A$16, LOOKUP TBL :: B$1:B$16) * 16^2+LOOKUP(MID(A2, 3, 1), LOOKUP TBL :: A$1:A$16, LOOKUP TBL :: B$1:B$16) * 16+LOOKUP(MID(A2, 4, 1), LOOKUP TBL :: A$1:A$16, LOOKUP TBL :: B$1:B$16)),"", LOOKUP(MID(A2, 1, 1), LOOKUP TBL :: A$1:A$16, LOOKUP TBL :: B$1:B$16) * 16^3+LOOKUP(MID(A2, 2, 1), LOOKUP TBL :: A$1:A$16, LOOKUP TBL :: B$1:B$16) * 16^2+LOOKUP(MID(A2, 3, 1), LOOKUP TBL :: A$1:A$16, LOOKUP TBL :: B$1:B$16) * 16+LOOKUP(MID(A2, 4, 1), LOOKUP TBL :: A$1:A$16, LOOKUP TBL :: B$1:B$16))
Be sure to Format Col A of both tables to Text.
Regards,
Jerry

Thermistor conversion formula is wrong?

Similar Messages

Maybe you are looking for