Filter SC-2345: signal drift issues

Hello all,
Our lab has a NI filter SC-2345 (Signal Conditioning Connector Block) to filter out noise from motion sensors used in a MRI console. We also use LabView to gather this data in our computer. The problem is that when we set up our equipment (serial cables with motion sensor at end) the signal seems cleaner, but appears to drift- eventually going out of our field of view. This (floating) signal is drifting out of range over time. We are thinking it might be an issue with the grounding? Does anyone know how to properly ground this device? What could fix this problem? Would adding resistors help? and are there fixes without adding resistors?
Any help or advice is much appreciated.
Thank you!!
Sandra

Hello Sandra,
This is Marcus in Applications Engineering. Thank you for your post. I have attached a document which I think will be helpful. It has procedures for wiring your analog signals and also has a section on noise and floating signals which I believe will be relevant to your case.
Please let me know if you are still having issues and I will do my best to assist you.
http://zone.ni.com/devzone/cda/tut/p/id/3344#toc2
Regards,
Marcus
Marcus M.
PXI Product Support Engineer
National Instruments

Similar Messages

SC-2345 signal conditioner module

Has anyone worked with this hardware before?
DAQ interface to the [SC-2345] signal conditioner module. It is configurable with individual SC modules.
(2) Using equipment currently being procured: NI CompactDAQ 9181 over Ethernet housing one NI 9213 x16 channel thermocouple module.
Functionality should be such that a variable sample rate may be employed from 1 sample per second to 1 sample per minute for all channels. One sample per minute shall be the threshold requirement. Only temperature is expected to be measured. All available channels having temperature modules shall be measured and recorded. The data should be viewed on a graph for the current test mainly for troubleshooting and calibration purposes. All data shall be stored on hard drive to a data file in a usable file format, preferably *.csv file format. User interface shall support start and stop of a test in a single mouse or keyboard action. Each start of a new test shall create a new test data file not to overwrite other data.

What you are trying to do is possible with the equipment you have and LabVIEW. The 9213 has built in cold junction compensation for up to 16 thermocouple measurements.
To get started programming this try looking at the example under Help-> Example Finder-> Hardware Input and Output-> DAQmx-> Analog Measurements-> Temperature-> Cont Acq Thermocouple Samples-SW Timed.vi
This link may help you to program the start and stop for your measurements:
http://zone.ni.com/devzone/cda/tut/p/id/3331
Good luck!
Brian G.

Error 20020 - When trying to filter raw PPG signal

I've got some Raw PPG data points, I want to split these into its AC and DC components, I was told by my supervisor to use a band pass filter with the lower and upper cutoff frequencies as 0.7 and 1.1Hz respectively, I know why I'm recieving the error as my upper frequency is higher than the sample rate, but is there a workaround?
I've attached my VI and raw data, there are no headers on the data and the left column is time in ms, the right the intensity value.
Thanks in advance for any help
Solved!
Go to Solution.
Attachments:
Filtering Signal.vi ‏54 KB
Actual Raw data.txt ‏37 KB

Hi Seancassidy
I have attached a screen grab of how you can fix your issue.
I have included a constant of 0.001 to give you the resolution of 1ms.
You can find more info regarding this issue at the below link:
http://digital.ni.com/public.nsf/allkb/ABBD3A7BC25E17C8862561270058A4A0?OpenDocument
Regards,
Neil Crossan BEng (Hons) CLAD MIET AMIMechE
Applications Engineer
National Instruments
Attachments:
build waveform .PNG ‏6 KB

Mid 2010 iMac Wifi signal strength issue

I am having issues maintaining a robust Wifi signal on my 21.5 inch 2010 iMac with 10.6.5 installed.
my symptoms are very similar to what is described in this post:
http://discussions.apple.com/thread.jspa?threadID=2596933&tstart=0
in addition to that I am experiencing the following symptoms:
can't print to HP wireless printer
remote app for iphone doesn't find the iMac
mobile mouse remote app doesn't find the iMac
can't ping the iMac from Windows laptops on the same subnet or from the router itself
accumulation of send and receive errors in Network Utility
these symptoms occur after the machine has been connected to wifi for 30 minutes or so. Turning off Airport and turning it back on temporarily fixes the issue. the Mac firewall is turned off.
as reported in the post mentioned above, signal strength for my Windows laptops and other devices is consistently -25 but the iMac signal strength fluctuates wildly.
One more troubleshooting step that I have taken is to install Windows 7 on a boot camp partition to rule out the iMac hardware and physical location as the issue. While booted into Windows the iMac did not exhibit any of the above symptoms and held a steady -25 strength signal.
Lastly I am using a TrendNet Wireless N Access Point but have also tried an Apple Extreme and Express (both N). I've tried 2.4Ghz and 5Ghz on various channels. I've even tried dialing down to G mode.
I've read other posts about DNS settings, Static instead of DHCP addressing, etc. and none of these has solved this issue.
Thoughts anybody? TIA

Update concerning additional troubleshooting steps that I have taken.
1) did a clean install of OS 10.6.3 onto an external drive and managed to replicate the issue....so that rules out apps, preference files, etc.
2) managed to get a little bit more stability by setting up an Airport Express in 5Ghz mode with Interference Robustness turned on and the multicast rate set at 9Mbps....of course ios devices don't do 5Ghz so I still have to run another AP...so not an acceptable solution.
What else do I need to do to prove that it's a Mac OS software issue?

How to debug signal related issues with mdb

I have a C++ application and occassionally it core dumps receiving a SIGABRT signal. We are not able to find the source of the SIGABRT signal. All we have is the core. Is there a way to find out who sent SIGABRT to our process? For that matter if someone sends our application a SIGABRT using kill cmd asynchronously, how does one find out who has sent the same? We can't keep truss'ing the process as it's a production env. Is there a way to find this out from the core file?

I don't have a specific suggestion, but these ideas might help you.
I assume by 'cannot be resumed' that you are able to launch the application, but after leaving the application and returning back to it, the app crashes? Or is it that you can run the app once but never a 2nd time (even after it fully closes)?
What kind of app is it? WP7, WP8, WP8.1? Silverlight or WinRT? It might not make a difference but it might make it easier to find a solution. I suggest looking up the application life cycle relevant to the version you are targeting.
Is your app.xaml.cs doing anything out of the ordinary or is it just the default code?
Here's what I would try: put a breakpoint at the start of every method in App.xaml.cs/VB and hope one is hit! Not very helpful, but you might get lucky. I'm not too well versed in app resuming, but is the app navigating back to the page it was on when tombstoned?
Perhaps the issue is in the page OnNavigatedTo or the Loaded event handler (if you have one).
When my apps fail to launch and don't hit any breakpoints it usually ends up being an issue in XAML, not code behind. But I don't think your problem fits that becuase you can clearly launch the app, just not resume it.
I'm sure you've probably tried most of those things, but hopefully I thought of something you missed and it turns out to help :)
Visit http://blog.grogansoft.com/ for Windows development fun.

Iphone 5 signal dropping issue

Hi guys,
I just got my Iphone5 as a gift from my friend month ago.
It was really exciting when I first got it. However I found sometimes when I unlock the screen, the signal will suddenly drop to 1 bar and then searching, this will take seconds and then appears no service. If lucky, the signal will come back soon. But it still really annoying! And this happens more often recently.
I tried reset network setting few times but it didn't help at all. So I thought maybe is due to carrier's issue. I am with Vodafone, so I bought a Telstra prepaid sim and try to see if this fixed the problem. But still, keep lossing signals!
This is so frustrating!
And my battery is draining really fast as well, even I turned off wifi, bluetooth; minimum brightness; all background apps off. its still draining!!
Anybody got the same issue here? I tried google this but seems nobody got the similar problem
Could anyone help me please?!
Thanks!

Thank you for your answer!
Did your phone just fixed itself?! How long did it takes?
I'm worried if it's actually no signal after we lock the screen? I mean once I left my phone in the bathroom and I forgot so I called up but it just directly into voicemail! I thought I lost my phone!!
And what if I need to make a emergency call??

Problem with Diffuse Glow filter PSE mac (Intuit Tablet Issue?)

The problem that I am having is that when I use the diffuse glow filter it is using a "grey" instead of "white" glow. The program was installed and working fine for weeks until I used my walcom intuit tablet and the diffuse glow filter turned to grey. As far as I can tell there is no way to change what color the glow is so I am not sure how to fix it. I tried support at walcom and they claim to have never heard of this issue. I also have a notebook running Vista and CS3 and the same thing happened to it but I didn't realize it was the tablet until I tried to use the tablet with my new imac for the first time and the same thing happened.
Any ideas? Anyone else have this problem?

So I found the answer on another thread, I didn't realize that diffuse glow used the color chosen for your background as the color for the glow. The colors must have swapped when I started using the tablet. Ooopps! lol

Signal Quality issues - totally stumped

My first post so apologies if I step on anyones toes.
I've had a browse through and can't find an existing post that covers my scenario.
For a while now my box has been having issues on certain channels. The exact scenario is that the signal quality drops to below 25% which causes picture blocking / freezing.
Before anyone says its a MUX issue, I have tried.
1) New cables
2) Rebooting
3) Factory reset
4) A known good cheapie freeview receiver from Asda shows a static 95% quality on the channels where the BT Vision box has problems. With both the old and the new cables. No signal bouncing - stays solidly at 95% (or thereabouts)
The specific channels it has issues with are Channel 21 (VIVA),Channel 38 (quest +1). I am on Waltham transmitter and other channels on the MUXes have 85% quality and higher on the BT Vision box. On VIVA and Quest +1 the quality bounces all over the place between less than 25% upto 87%.
If it was all channels on the MUX then I'd know it was time for aerial reposition, but with it being on only specific channels and a cheapie receiver working perfectly I'm a bit stumped??
Additionally, since the new firmware, I use a 4:3 TV through SCART and the screen real estate now seems wrong as it chops the bottom off the screen when in the new menu system - so things telling me what to press are lost - ie: to delete a recording from the recordings section I can't see any advice at the bottom of the screen as was there on the old firmware, I basically found it was the red button by trial and error. I'm guessing BT think we all have HDMI TV's and maybe the menu works OK on HDMI.
Its as though the tuner has just decided it doesn't like channels 21 and 38 - maybe its telling me to to watch some better quality programs... Or more seriously, maybe its cooked and has a specific frequency reception issue? Unlikely but I can't think what else it could be.
If anyone can advise I'd appreciate some guidance as I've pretty much exhausted my limited knowledge of TV transmitter behaviour.
Pete

Hi Pete65,
It could be possible that if you are in the Northampton/Milton Keys/ Bedford/ etc areas, that particular mux could have some signal interference .
There was a post earlier which I can't find right now, where the author talks about signal quality vs signal strength.
It could also be possible that the signal is too strong which could cause a detrimental effect on the quality.

Non-Scientific Evidence for Signal Loss Issue

I just did a test with my phone. I started a speed test to assure some steady data flow, and then put the phone next to a PC speaker to create the interference noise through the speakers. It came through loud and clear.
I touched the spot in question on the phone (lower left corner, black strip), and the sound stopped, and it coincided with a drop in my speed test. I repeated this a few times, and repeatedly moved my finger to and from the problem spot, and each time I would do that, the sound coming through the PC speaker would stop.
This, to me, shows that the hand is in fact blocking the signal to the device, causing the signal attenuation, and that it is more than just bars being misreported.

The ratio of dBm to power (watts) is logarithmic, which means as dBm decreases the power of the signal decreases exponentially. You can get wattage from dBm by this formula:
P = 10^((x - 30)/10) where x is in dBm.
http://en.wikipedia.org/wiki/DBm
If you calculate the wattage (for example, -91 dBm as a base, -91 - 10 dBm = -101 dBm for Nexus One, -91 - 20 = -111 dBm for iPhone 4), you will see that while the Nexus drops to 1/10th of its power while held, the iPhone 4 drops to 1/100th of its power.
But it's not just power that matters in this case, its the thresholds of acceptable power levels that counts as well. Cell phones and towers can accommodate even big drops in power as long as the resulting power is enough to maintain a secure signal between the phone and the tower. If your signal strength is -51 dBm, you can drop to 1/100th of the power you had before and still have a usable signal because your phone can still make a reliable connection with that power level. The problem is that a drop to 1/100th of your original signal strength simply by holding your phone with your palm touching that lower left gap seems unusual and potentially unacceptable. Cell phone users already have to deal with many other factors that may hurt the ability of their signal to stay within the acceptable threshold, such as distance from a tower or being inside of a building, this issue only makes matters significantly worse.
The question is, is this issue acceptable or not? If other phones do not have this level of signal drop simply by holding them in a normal way, then this phone is deficient. You should be able to exchange your phone for another that does not have this deficiency.
If the phone isn't deficient, then AT&T needs to correct its coverage maps to accommodate this phone's deficiency, or create a "special" map for iPhone 4 coverage. At both my work and home, AT&T's coverage viewer says I have "Best" coverage. If I hold my phone at work or at home though, my coverage drops to 1 bar and I cannot make calls or use data. AT&T's coverage should be showing my area as "Moderate" coverage (or worse), then I wouldn't have a complaint because I could have clearly seen that AT&T has crappy coverage in my area.
Holding the iPhone 4 in your hand with the palm touching the lower left gap in the steel band is not abnormal user behavior. Although I am aware of the issue and do my best to avoid touching it, sometimes I adjust the way I hold the phone out of habit or for comfort and my palm just ends up resting against that gap and I either end up dropping the call or losing the data connection before I notice. It's disappointing because I never had this problem with my iPhone 3G, and I really like the iPhone. As an iPod Touch it is faster and better looking that the previous generation, but, for someone in a weak "5 bar" area that AT&T considers to have "Best" coverage, as a phone it is actually worse than the iPhone 3G.
Imagine if your computer completely crashed every time you hit the "t" and the "h" keys at the same time. You'd find that most of the time it wouldn't be an issue, but occasionally your fingers are so quick that you hit both keys virtually at the same time (assuming you are a fast typist); your computer crashes and you potentially lose any unsaved work. You can do two things, learn to hit the "t" key and "h" key slower, slowing down to do full taps of each, or save your work repeatedly and just accept that the computer will crash. People who type slower anyways probably wouldn't have an issue, but fast typists would find it uncomfortable and inefficient.

Can cascading power to FP AI and counters cause signal drift

I am using the following hardware:
FP-1000 > (3) FP-TC-120
|
FP-1001 -> (3)FP-AI-111 -> (2)FP-RLY-420 -> (3)FP-CTR-500
All my AI's are 2-wire 24V loop powered 4-20mA devices (pressure transducers).
Everything is powered by one 50W power supply.
With all sensors at rest, I get 4mA on all channels; when signals are applied to transducers, some channels will drift to 7 or 8mA. Some sensors read only 15-16mA at full span, but work fine on my bench. I am seeing no drop-off in power supply voltage, so I don't think I am over-driving my supply.
Could cascading the power from the network modules to the AI and the counters be causing these problems?
It reminds me a ground loop problem, but all the sensor
s are floating and the only ground is through the AC supply to the Power supply.

Yes, cascading power may be the cause of the problems. FieldPoint IO modules are isolated from the IO stage to the inter-module communication bus. The communication bus ground is linked to the C terminal of the network module. By cascading the power from the V & C terminals of the network module to the V & C terminals of IO modules, the isolation barrier is bypassed and the IO modules no longer have floating commons. Additionally, the RS-232 port of the FP-1000 is not isolated, so it shares it's ground (linked through the C terminal) with the controlling computer. Thus, in your scenario, you have two fixed grounds, the computer and the power supply. Additionally, the input stages of the AI and CTR modules, which are normally floating with respect to the inter-mod
ule communication bus are directly tied to it (and ground) through the power cascading. Thus, as you suspect, you most likely have a ground loop from one or more of the sensors.
Regards,
Aaron

Audio sync drift issues within Premiere Pro CS6, even with 48kHz project & source material?

Evening guys and Merry Christmas to those who follow the tradition. I'm currently doing a few last minute tweaks to a live dance show that I recently shot. The show featured music that was recorded in camera (via additional mic) from the speaker setup within the theatre. This was always intended as a guide track as the original music would then be synced in the edit to give a cleaner sound to the audio during the dance sequences. I have the original CD that the music was played from on the night, however when the files are imported into Premiere Pro (or even Audition), they sync for the first 10 seconds or so and then gradually drift out of sync as the track goes on.
My project is set to 48.000 audio, which was what the original footage was shot at, as well as the audio tracks being imported as 48.000 too. Now on paper there should not be any issues with this sync drift occuring right? I've even tried with 44.100 audio files and naturally they drift out of sync.
At a loss here really as I'm not sure where i'm going wrong. Can anyone shed any light on this situation please?
Thanks!

What are you editing, and does your project match your video?
Read Bill Hunt on a file type as WRAPPER http://forums.adobe.com/thread/440037
What is a CODEC... a Primer http://forums.adobe.com/thread/546811
What CODEC is INSIDE that file? http://forums.adobe.com/thread/440037
Report back with the codec details of your file, use the programs below... a screen shot works well to SHOW people what you are doing
http://forums.adobe.com/thread/592070?tstart=30
For PC http://mediainfo.sourceforge.net/en or http://www.headbands.com/gspot/
For Mac http://mediainspector.massanti.com/
Please NOTE that the PPro CS6 screen may look a bit different (I use CS5)
For CS5 and later, the easy way to insure that your video and your project match
See 2nd post for picture of NEW ITEM process http://forums.adobe.com/thread/872666
-and a FAQ on sequence setting http://forums.adobe.com/message/3804341

IIR filter, not contiguous, signal processing

Hello!
I am acquiring data countinuously from several voltage output sensors. I am sending the waveforms through an express vi filter (bandpass) and I am using the default setting for IIR filtering. The program is setup such that data acquisition is done with a while loop. The DAQ wile loop is inside of a bigger while loop which is related to program start and stop.
Every time I am doing data acqusition through the filter I get a warning that tell me the waveforms are not contiguous. Again, this is not flagged as an error but rather as a warning. The attached example might clarification.
The question is: is the IIR filter uses previous waveform information to judge the current waveform? If this is true, then I do not like the solution; if this is not true, the I should probably just ignore the warning...
Does the express vi has some type of reset that would activate when the whole program stops because I do not see the warning message first time I start the vi?
Thanks
Attachments:
FIlterCase.zip ‏58 KB

Thank you for your answer.
From your answer I deducted that whenever I restart the data acquisition while the main program is still running I'd better make sure I reset the filter such that it will now "know" that it is new data coming in. I did not have a chance to check inside the express vi yet but from what you are saying it must be some sort of reset button in there that I could 'pull out' in the connector block of the subvi..
The band widths I am using are anywhere between 100 Hz to 40000 Hz so the transient duration will be short to very short and the system, the way it is setup now, will allow enough time to the IIR filter to handle correctly new data.
Finally there is always the option to acquire just the raw data. later I could read it back and filter it if necessary. However, there are situations when I want to filter out noise and possible alising frequencies; moreover, I acquire vibrations and forces in the same time on the same board - if I need the 40kHz sampling rate for vibrations, automatically I will have it too for the "low end" signals as well (0 to 10V from power and force sensors). I believe doing some filtering and maybe some decimation after filtering will help me keep the amount of data low on the 'low end' signals side. Am I correct in my assumptions?
Thanks again.

IPhone signal aquisition issue in/out of building

This is a very recent development with my iPhone 3G.
Everytime I get leave my apartment (where I have great signal), go down the elevator into the garage (where I lose the signal) and drive out where I would normally regain my signal (to a full healthy signal) - the iPhone no longer finds a signal.
This used to not be an issue, regardless of wether I was in just Edge mode or with 3G enabled.
Now every time I lose signal for either a short time or a long time - the iPhone does not get it back once I am in an area with a signal. (In/out of building, subway, etc..)
My attempts to solve the issue:
- I tried being in just Edge mode (turning 3G off) - the issue is still there
- I tried turning on and off Airplane mode (waiting a few seconds in between modes)
- I reset and restored the iPhone that didnt solve the issue either.
I am out of ideas at this point - so I come here and see what my options are.
Sorry for the trouble and thank you in advance.
-Dmitriy

I am in DC also.
Now my iPhone 3G is working fine in those areas of DC where I use it. It worked fine when I first bought it months ago, then about a month ago, for about 5 days, I noticed the problem you did sometimes. Also then, sometimes I had to turn off 3G to get a signal. Sometimes it would revert back to GPRS (not 3G or EDGE). Sometimes it would connect to 3G and there would be no data connection. Then after 5 days it was fine. I expect I just experienced some side-effects of network adjustments from AT&T. I let it go and it resolved itself.
Now I see AT&T and other carriers bringing in temporary portable cell sites to the National Mall and downtown to handle the crowd expected at the inauguration January 20 (you can see one with the AT&T logo at the intersection of Constitution and Louisiana Ave. NW on the Mall). I think those are being turned on and adjusted, and I expect there are some hiccups when doing that.
I'd let it go for a few days and then call AT&T if it does not clear up or if it is a big problem for you now.

Signal Handling Issue with OCI

Greetings.
I have a library using OCI with Oracle 10g.
I am not doing any signal handling inside the library.
I have realized after a connection is made to Oracle 10g server and successfully terminated, the ctrl+Z signal (SIGTSTP) would not be honored. If I use the same library and make no connection to database, then the signal is honored. Other signals such as SIGINT etc are OK even if I make connections to database server.
Operations that I do using OCI are simple:
1- initialization of context (standard env creation, set attributes, handle allocation etc)
2- making connection
3- inserting using SQL insert method (statement prep, defineByPos, execute)
4- simple selection of last value of a sequence (statement prep, defineByPos, execute)
5- clean up (OCISessionEnd, OCIServerDetach,and freeing handles)
Again, I have no signal handling inside the library. I am using this over Solaris OS and the functionality is correct except for this signal issue.
My questions:
1- Is this a known issue or is this something that has been seen before?
2- what sort of signal handling is in OCI that could potentially impact my app?
3- Is there any solution that you could suggest?
thank you in advance.

I'm trying to migrate from oracle 9i HP unix to oracle 10G AIX5.3
I'm trying to create a connection pool. Then create Many threads, with each of these
performing an OCI Session Get at thread initialization.
Then handing the threads work to perform on their existing OCI session to the connectionpool.
Same thing was working fine in oracle 9i but if I try to do the same in oracle 10G seems to get locked up,
unless the sessionget/sessionrelease are in the same working
thread subroutine. I am trying to avoid getting a session and releasing for each unit of
work.Instead I'd like to acquire a bunch of session against the connection pool.And then have the threads (with persistent sessions) perform periodic work....
If utilizing a get/work/release all in the same thread and subroutine call.Then everything works, except performance is very poor.
please find the function I'm using to achive the same.
Experts please help me ,I'm totally struck here....
int ConnectionOpen (Connection conn, char username, char password, char server) {
** Functionality : Opens a new session with Oracle.
** Parameters : conn - pointer to the struct Connection. It is an output parameter
** returns the handle to the new session.
** username - pointer to the char array has username.
** password - pointer to the char array has password.
** server - pointer to the char array has database name.
** Returns 0 on success, 1 on success with information and non-zero value on error.
int status = 0;
boolean sesfnd;
text errbuf[512];
sb4 errcode = 0;
if (!conn) return OCI_INVALID_HANDLE;
if (!strcasecmp (USE_SESS_POOL, "YES"))
/* PLC44050021 Session Pool Changes*/
if (conopen==0)
status = OCIEnvCreate((OCIEnv **) &envhp, OCI_THREADED,
(dvoid *)0, (dvoid *(*)(dvoid *, size_t))0,
(dvoid *(*)(dvoid *, dvoid *, size_t))0, (void (*)(dvoid *, dvoid *))0,
(size_t)0, (dvoid**)0);
if (status != 0 && status != 1) return status; /*error in creating environment*/
status = OCIHandleAlloc((dvoid *)envhp,
(dvoid **)&errhp,
OCI_HTYPE_ERROR,
(size_t)0,
(dvoid **)0);
if ( status != 0 && status != 1 ) return status; /*error in allocating error handler*/
status = OCIHandleAlloc((dvoid *)envhp,
(dvoid **)&authp,
OCI_HTYPE_AUTHINFO,
(size_t)0,
(dvoid **)0);
if ( status != 0 && status != 1 ) return status; /*error in allocating error handler*/
status = OCIHandleAlloc((dvoid *)envhp,
(dvoid **) &poolhp,
OCI_HTYPE_SPOOL,
(size_t)0,
(dvoid **)0);
if ( status != 0 && status != 1 ) return status; /*error in allocating CPOOL Handler*/
status = OCISessionPoolCreate((OCIEnv*)envhp,
(OCIError*)errhp,poolhp,
&poolName, (ub4*)&poolNameLen,
(text*)server, (ub4)strlen(server),
sessMin, sessMax, sessIncr,
(text*)username, (ub4)strlen(username),
(text*)password, (ub4)strlen(password),
OCI_DEFAULT) ;
if ( status != 0 && status != 1 ) return status;
conn->envhp=(OCIEnv*)envhp;
conn->errhp=(OCIError*)errhp;
status=OCIAttrSet((dvoid *)authp,(ub4) OCI_HTYPE_AUTHINFO,
(text*)username, (ub4)strlen(username),
(ub4) OCI_ATTR_USERNAME, (OCIError*)conn->errhp);
if ( status != 0 && status != 1 ) return status;
status=OCIAttrSet((dvoid *) authp,(ub4) OCI_HTYPE_AUTHINFO,
(text*)password, (ub4)strlen(password),
(ub4) OCI_ATTR_PASSWORD, (OCIError*)conn->errhp);
if ( status != 0 && status != 1 ) return status;
status = OCISessionGet((OCIEnv*)conn->envhp,
(OCIError*)conn->errhp,
(OCISvcCtx**)&(conn->svchp),
authp,
(OraText *)poolName, (ub4)strlen((char*)poolName),
(OraText *)"", (ub4)0,
NULL, NULL,
0,
OCI_SESSGET_SPOOL);
if ( status != 0 && status != 1 ) return status;
conopen=1;
/******* if the session pool is already established, reuse sessions out of it ********** /
else
conn->errhp=(OCIError*)errhp;
conn->envhp=(OCIEnv*)envhp;
/******* Hanging in this call ********** /
status = OCISessionGet((OCIEnv*)conn->envhp,
(OCIError*)conn->errhp,
(OCISvcCtx**)&(conn->svchp),
authp,
(OraText *)poolName, (ub4)strlen((char*)poolName),
(OraText *)"", (ub4)0,
NULL, NULL,
0,
OCI_SESSGET_SPOOL);
if ( status != 0 && status != 1 ) return status;
else
status = OCIEnvCreate((OCIEnv **) &conn->envhp, (ub4)OCI_DEFAULT,
(dvoid *)0, (dvoid *(*)(dvoid *, size_t))0,
(dvoid *(*)(dvoid *, dvoid *, size_t))0, (void (*)(dvoid *, dvoid *))0,
(size_t)0, (dvoid**)0);
if (status != 0 && status != 1) return status; /*error in creating environment*/
status = OCIHandleAlloc((dvoid *)conn->envhp, (dvoid **)&conn->errhp, OCI_HTYPE_ERROR, (size_t)0, (dvoid **)0);
if ( status != 0 && status != 1 ) return status; /*error in allocating error handler*/
status = OCILogon((OCIEnv*)conn->envhp, (OCIError*)conn->errhp, (OCISvcCtx**)&(conn->svchp),
(text*)username, (ub4)strlen(username),
(text*)password, (ub4)strlen(password),
(text*)server, (ub4)strlen(server));
return status;
}

Firmware 2.0 Video Signal Monitor Issues

This is a story of woe regarding my issues with the histogram "video signal monitor"Everything described below is using CineEI Since purchasing the camera, I was never able to get the VSM to display consistently. There seemed to be little rhyme or reason to when it displayed and when it didn't. As with any other issue, I put my faith in the second coming, firmware 2.0. Today, I excitedly downloaded and installed 2.0. So far, only disappointment. Initially, I was able to get the VSM to display in every 23.98 recording format (I didn't try other framerates)I even tried turning on all the outputs, and was happy to find that my VSM stuck around. - Everything that follows is XAVC-L 1080 @ 23.98 - Then I tried turning on a LUT and everything went to ****** in a hand-basket. After turning on a Viewfinder LUT, I ony got that lovely "cannot proceed" message every time I tried to enable the VSM. I tried turing off all the outputs, turning off output displays, nothing helped. Frustrating, needless to say. But, because the VSM would be sampling the post-LUT image anyway, I wasn't heartbroken...yet. Defeated, I turned OFF the viewfinder LUT. Got excited to see my new friend the VSM. But now, even with the LUT off, I get the "cannot proceed" message. I've switched every related setting in the camera, outputs, output display, output formats, other LUT settings. Nothing helps. Now I can't do anything to get the VSM to display on my camera. I've tweeked every setting imaginable. I've tried restarting multiple times, even switching between Cine EI and custom. the VSM won't even display in custom mode now... The only fix I've found is to do an All Rest. Doing so allows the VSM to display without a LUT. But, once I turn on a LUT, the VSM disappears for good, even after I switch the LUT back off. I wouldn't wih this frustration on my enemies but has anyone else experienced this after upgrading to 2.0? Sony, is there a matrix somewhere that can educate us on when the VSM can and cannot be displayed? It's hard to discern when I'm experiencing nominal behaviour without knowing what to expect from normal operation.

ok, I found an output combination that I must have missed earlier which narrows my issue. My VSM won't display unless an SDI output is enabled. HDMI output setting makes no difference. So, after enabling SDI in "Output On/Off": SDI 2048x1080Psf HDMI --- VSM: YESSDI 1920x1080Psf HDMI --- VSM: YESSDI --- HDMI 1920x1080P VSM: NOSDI 1920x1080i (2-3pd) HDMI 1920x1080i (2-3pd) VSM: YES The same concept holds true for UHD and QHD. Without an SDI output enabled, no VSM. Erik, I suspect that if you enable an SDI output, you'll be able to display the VSM in all recording formats.

Filter SC-2345: signal drift issues

Similar Messages

Maybe you are looking for