Sensor acting up

Hi all,
I have my Incredible for 3 weeks now. The past week, the sensor on my Incredicle is acting up. It would press certain keys or application without me touching any of it and would go on like that until I have to turn it off and on again.
Anyone else have issues like these?Is this a malfunction?
Thank you.

Clean the optical track ball sensor by lightly blowing some air into it. Maybe use a dry q-tip to clean it a little. It's got dirt or something it it making it go crazy.... Been down that road.

Similar Messages

How do you use a hall effect sensor to act as a trigger to start the aqusition of data ?

On a 4 stroke engine, a hall effect sensor acts as a trigger to instigate the aquisition of data. Data is recorded from a pressure transducer on both the compression and exhaust cycle.

Paul,
Here is a great resource the help you get started:
http://zone.ni.com/devzone/devzone.nsf/webcategories/327C75ED77E1B8E5862567E80051CF83
Additionally, if you need more help, please supply information such as:
1. What daq board are you using?
2. What kind of signal does your hall effect sensor output?
3. What have you tried?
Best Regards and good luck!

Previous Shutdown Cause: 3

Does anyone have any clue what this means? I don't understand computer-speak. My MacBook shuts down unexpectedly if it is left inactive for more than a couple minutes--sometimes the fan is running, most of the time it's not. Sometimes there are active applications, sometimes there aren't. Sometimes it's plugged into the adapter, sometimes it's on battery. Nothing is consistent except the fact that I can't walk away for 2 minutes to answer the phone or get a snack without returning to a shutdown computer.
Help!
Thanks.
Here's what the system console says when I search for the term shutdown:
Sep 5 14:30:56 localhost kernel[0]: Previous Shutdown Cause: 3
Sep 5 15:13:18 localhost kernel[0]: Previous Shutdown Cause: 3
Sep 6 09:16:26 localhost kernel[0]: Previous Shutdown Cause: 3
Sep 6 09:17:58 localhost kernel[0]: Previous Shutdown Cause: 3
Sep 6 12:42:08 localhost kernel[0]: Previous Shutdown Cause: 3
Here are my specs:
Model Name: Mac
Model Identifier: MacBook2,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.16 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache (per processor): 4 MB
Memory: 1 GB
Bus Speed: 667 MHz
Boot ROM Version: MB21.00A5.B06
SMC Version: 1.17f0
My Macbook was purchased in mid August 2007, and it runs 10.4.10, so the earlier firmware problems shouldn't be the problem. I would call Apple Support, but I'm in the Middle East, so wherever I call will be long distance. I'm trying to resolve this problem independently. It will be a tremendous inconvenience if I have to travel to Rosh Haayyin (near Tel Aviv) to take it to an authorized repair location...or worse ship it back to the U.S.

If you can get it to run long enough, try running your hardware tester. It sounds like it may be going into 'thermal shutdown.' You may have a thermal sensor acting up.
-Bmer
Mac Owners Support Group
Join Us @ MacOSG.com
YouTube.MacOSG.com
iTunes: MacOSG Podcast
 An Apple User Group 

IDS/IPS logging, and SDM replacement?

I'm reviewing for my CCNA Security exam. I've got several books that I'm using for study materials..the Cisco press blue softcover, CCNA Security Study Guide by Tim Broyles...
Now, I've seen arguments about how the IDS "pulls" data. The books are unclear, and I'm trying to get a definitive answer.
In the IDS chapter in Cisco's book, discussion at the end of the chapter talks about how the IDS uses SDEE to pull the data. But it shows two examples of config lines, SDEE and Log, and it goes on to say that SDEE and Syslog are the protocols used to grab the alerts. But then, in the next paragraph, it says to that it uses HTTP (and further says HTTPS is more secure) to gather the data.
So, in googling to try and find resolution, I made the water murkier. I saw everything from those dreaded " I just took the exam..." and various other answers.
I'm thinking that syslog is not a protocol. Syslog is a venue where data is stored and can be retrieved and viewed by various applications like Solar Winds, etc. So, I'm thinking SDEE uses HTTPS (which is a protocol) to grab the data. But, I want to ensure I have my ducks in a row before the exam.
So, can someone with AUTHORITY please advise what the heck IDS uses to pull the data?
Now the 2nd part of this concerns dreaded SDM. SDM is at v 2.5, and there have been no updates/tweaks to it. I never see anyone in the RW use it. I'm sure that there's something better out there, yet Cisco is insisting on hammering that home on their CCNA security exam. What is SDM being replaced with? What should I start working with if I want to go on and get my CCNP Security certification?
Thanks much...testing on Tuesday

The confusion you are seeing is because IPS (or IDS) exists on two entirely different platforms; the router IOS and the IPS sensor appliance. These two types of IPS devices are managed and report events very differently.
The Router IOS PS feature can report events (signature hits) via syslog (and yes, that is a real protocol, just not a very secure one for carrying sensitive information like signature events) and SDEE. The Appliance IPS Sensors can only report events via SDEE (and SNMP Traps, if optioned on a per-signature basis to do so).
SDEE is a "pull" protocol, meaning the Sensor acts as the host and the client "asks" for signature events. This allows multiple clients to get a feed off one sensor and not have to maintain message synchronization. SDEE is an XML formatted protocol (so it's self documenting) and is carried over HTTPS.
- Bob

TCP segment Overwrite

Recently, I've been seeing a ton of messages on the IPS Event Viewer stating that TCP Segment Overwrites have been detected. The events are from either the IPS-A to our DMZ or vice versa. It just started whenever we added some servers to the network. Does anybody have any suggestions? We traced the packets, it's not hacker related. It seems like maybe a server or app. may be causing the issue. The problem is isolating it. I would appreciate any feedback you could provide. Thanks!

TCP normalization
Through intentional or natural TCP session segmentation, some classes of attacks can be hidden. To make sure policy enforcement can occur with no false positives and false negatives, the state of the two TCP endpoints must be tracked and only the data that is actually processed by the real host endpoints should be passed on. Overlaps in a TCP stream can occur, but are extremely rare except for TCP segment retransmits. Overwrites in the TCP session should not occur. If overwrites do occur, someone is intentionally trying to elude the security policy or the TCP stack implementation is broken. Maintaining full information about the state of both endpoints is not possible unless the sensor acts as a TCP proxy. Instead of the sensor acting as a TCP proxy, the segments will be ordered properly and the normalizer will look for any abnormal packets associated with evasion and attacks.
http://www.cisco.com/en/US/products/hw/vpndevc/ps4077/products_configuration_guide_chapter09186a00804cf52e.html

Processor Overheat Shutdowns

My 1st gen. (spring 2006) MBP has been great but it's been plagued for years by a really frustrating problem that no one really believes until they see it.
It's simple:
It hard-shuts down (99.9% sure due to heat, as I monitor the heat with smcfancontrol) during the following tasks:
*Rendering video in FCP
*Converting audio files in iTunes
*Certain flash-based video players (not all - youtube is generally fine)
*Certain flash-based webgames
*Etc
Basically it seems that certain processor-intensive tasks cause the heat to go up above 100 celsius for enough time that it hard shuts down.
I have tried a lot of fixes. I have disassembled the MBP and re-applied the thermal paste. I have tried managing the fans manually. I have cleaned the fans and even replaced one. I have not tried to do a restore from disc, however, as I will lose some software I no longer have the licenses to reinstall... and thusly can't afford it.
It works beautifully for other tasks, and now I absolutely need the MacBook to be able to render video for work. And there's no reason why I should have to get a new MBP (not that I could) just because of such a strange problem. Maybe there is a known fix for this out there that someone is aware of????? I've read everything I could via google, off and on for 2 years, with no results. So, again, cash reward if you can lead me to a solution.
<Edited by Host>

First of all, a MacBook is not designed to do processor-intense work like that. My old MacBook used to get real hot simply watching a YouTube video. The fan would run wide open at 6000RPM. It's the main reason I moved to a MacBook Pro. With that being said, the unit should not be shutting down like that.
Have you monitored the exact time the unit shuts down and checked your System logs in your Console application for clues to the cause?
Have you ever ran your hardware tester for an extended period of time? It sounds like you may have a thermal sensor acting up.
I have not tried to do a restore from disc, however, as I will lose some software I no longer have the licenses to reinstall... and thusly can't afford it.
You can work around that to see if the issue is software-related. Simply take an external drive, load a basic system on there and run from that to troubleshoot. If you are still having the same issue, then it's most likely hardware-related. At that point, I'm 99% sure replacing the logic board will solve your problem.
I know that's not what you want to hear, but I'm afraid that's what it might ultimately take.
Dave M.
 MacOSG: An Apple User Group  iTunes: MacOSG Podcast  Follow us on Twitter: MacOSG

Fans, fans, and fans

Can anyone PLEASE explain to me why would my fans kick in from 2000+ to 6000+ while doing absolutely nothing. Sure I am on the internet, but I could simply be reading an article and half way through it the fans simply kick in. I check the CPU and its still sitting idle, no extra load showing.
I have only noticed this increase in FAN-ning ever since I swapped my internal drive from 5400 to 7200. Please note that the fans kick in WITHOUT accessing HD work.
Your input would definitely alleviate my frustration.
Thank You

Try resetting your SMC and PRAM.
Resetting the System Management Controller >>
Your hard drive may be getting hot. Run your hardware tester for an extended period of time. Maybe you have a temperature sensor acting up.
Dave M.
 MacOSG: An Apple User Group  iTunes: MacOSG Podcast  Follow us on Twitter: MacOSG

Cross post from IT Jobs and Careers forum - IT Infrastructure Engineer

http://community.spiceworks.com/topic/1053062-it-infrastructure-engineer-bracknell-united-kingdom
This topic first appeared in the Spiceworks Community

What mean 3' long for someone how nows only metric? 3 foot (bigfoots?) 3inch ??
VFDs come in two tastes, some with some without output filter.... Have you tried another one, maybe the filter doesn't work ?
My guess about the grounding cable was just because people are laisy. If you put in and out the VFD, why not only change the cabling for the three phases and keep the ground where it was ?!.. I'm pretty shure that there is a big nice grounding screw right beside the VFD output, and it makes sense to use it
How is the reading if you (can) place (hold) the sensor near the VFD driven motor without contact to the rigg?
According the sensor: 90-95% grounding problems ... BUT just an idea: If the sensor acts with metal objects, then by a change in the electric or magnetic field (field weakening by eddy currents...) the sensor produce. What if the one of the switching frequences of this VFD correlates with the frequence of the sensor? Just like some TVs goes mad if your new poversaving electronic lamp hits the IR main frequence
Greetings from Germany
Henrik
LV since v3.1
“ground” is a convenient fantasy
'˙˙˙˙uıɐƃɐ lɐıp puɐ °06 ǝuoɥd ɹnoʎ uɹnʇ ǝsɐǝld 'ʎɹɐuıƃɐɯı sı pǝlɐıp ǝʌɐɥ noʎ ɹǝqɯnu ǝɥʇ'

Losing network connection and NIC acts weird from warm/hot weather/temperatures?

Hello.
Is there a known issue on MSI P43 NEO3-F (MSI-7514) motherboards' onboard RealTek RTL8168C (P)/8111C(P) PCI-E Gigabit Ethernet NIC network disconnecting and acting weird during warm/hot weather?
I noticed lately and back on 1/11/2009 night when weather got warm/hot (e.g., my room can get over 85F degrees, but lately it has been 80F degrees), my network would lose its connection. See http://img9.imageshack.us/img9/5580/screenshots.gif for a few SpeedFan's sensor readings when the incidents occurred. I have never seen this happen when the weather is cooler (60-70F degrees in my room).
I also think this only happens if I am using the PC lightly (nothing intensive) like watching fullscreen videos (video overlay), surfing the Web, etc. I don't see any errors or evidences that it happens when idled (e.g., asleep or out). Uptime doesn't seem to matter since I have seen days to 3.5 hours.
I tried upgrading network driver twice (e.g., Realtek_XP_5714_0219 from
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false ...), disabling Kerio Personal Firewall v2.1.5 (XP's disabled already), releasing and renewing IP address (works, but still no network -- can't even ping my router!), unplugging and replugging the cat5 cable (do see the network port lights on), touching the network jack and hardware inside and outside of the case (not hot), trying another cat5 cable and a network port on a switch instead router's), changing from "Minimal Power Management" to full power (no underclocking/slowing down when idled), etc.
During the disconnections, I tried:
C:\>tracert 192.168.0.1
Tracing route to 192.168.0.1 over a maximum of 30 hops
1 * * * Request timed out.
2 * * * Request timed out.
3 * * ^C
IPCONFIG.EXE /ALL when having network problems:
Windows IP Configuration
Host Name . . . . . . . . . . . . : FOOBAR
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter VMware Network Adapter VMnet8:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet8
Physical Address. . . . . . . . . : 00-50-56-C0-00-08
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.134.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Ethernet adapter VMware Network Adapter VMnet1:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1
Physical Address. . . . . . . . . : 00-50-56-C0-00-01
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.80.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Ethernet adapter HDTV Tuner 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TechniSat DVB-PC TV Star PCI #3
Physical Address. . . . . . . . . : 00-D0-D7-30-19-C1
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 169.254.178.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 169.254.178.1
Lease Obtained. . . . . . . . . . : Saturday, February 28, 2009 6:55:04 PM
Lease Expires . . . . . . . . . . : Monday, July 13, 2009 11:28:08 PM
Ethernet adapter HDTV Tuner 1:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TechniSat DVB-PC TV Star PCI
Physical Address. . . . . . . . . : 00-D0-D7-30-1A-1D
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 169.254.178.4
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 169.254.178.1
Lease Obtained. . . . . . . . . . : Saturday, February 28, 2009 6:55:21 PM
Lease Expires . . . . . . . . . . : Monday, July 13, 2009 11:28:25 PM
Ethernet adapter Local Area Connection 15:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8168C(P)/8111C(P) PCI-E Gigabit Ethernet NIC
Physical Address. . . . . . . . . : 00-21-85-1A-C6-72
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.82
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
4.2.2.1
I checked Windows XP Pro. SP3's event logs and noticed these during the disconnections:
Event logs showed:
Event Type: Information
Event Source: Tcpip
Event Category: None
Event ID: 4201
Date: 2/28/2009
Time: 6:42:23 PM
User: N/A
Computer: FOOBAR
Description:
The system detected that network adapter \DEVICE\TCPIP_{51FDDE0F-0935-416E-8FE0-3E1A50847D41} was connected to the network, and has initiated normal operation over the network adapter.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 02 00 50 00 ......P.
0008: 00 00 00 00 69 10 00 40 ....i..@
0010: 02 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
Event Type: Information
Event Source: BROWSER
Event Category: None
Event ID: 8033
Date: 2/28/2009
Time: 6:47:22 PM
User: N/A
Computer: FOOBAR
Description:
The browser has forced an election on network \Device\NetBT_Tcpip_{89F40100-0D8D-4C33-A32D-3D91CAEB3FBD} because a master browser was stopped.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Event Type:   Information
Event Source:   Tcpip
Event Category:   None
Event ID:   4201
Date:      3/1/2009
Time:      6:19:08 AM
User:      N/A
Computer:   FOOBAR
Description:
The system detected that network adapter \DEVICE\TCPIP_{51FDDE0F-0935-416E-8FE0-3E1A50847D41} was connected to the network, and has initiated normal operation over the network adapter.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 02 00 50 00 ......P.
0008: 00 00 00 00 69 10 00 40 ....i..@
0010: 02 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
Event Type:   Information
Event Source:   Tcpip
Event Category:   None
Event ID:   4201
Date:      3/1/2009
Time:      6:19:20 AM
User:      N/A
Computer:   FOOBAR
Description:
The system detected that network adapter \DEVICE\TCPIP_{51FDDE0F-0935-416E-8FE0-3E1A50847D41} was connected to the network, and has initiated normal operation over the network adapter.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 02 00 50 00 ......P.
0008: 00 00 00 00 69 10 00 40 ....i..@
0010: 02 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
I also noticed the disconnections usually start with red X icon in my taskbar with its bubble and then later the long disconnection even though no red X (1 GB and connected). If I were to disconnect the cat5 cable from NIC, then it wouldn't even detect it is missing the cable!
The only way to fix this was to reboot (best way and last longer) OR disable network connection and re-enable it (Windows XP's Network Connections) or the NIC itself (Device Manager), but that doesn't always last long (maybe a minute). Example of my pings right after disabling and re-enabling NIC:
C:\>ping 192.168.0.1 -t
Pinging 192.168.0.1 with 32 bytes of data:
Request timed out.
Reply from 192.168.0.1: bytes=32 time<1ms TTL=150
Reply from 192.168.0.1: bytes=32 time<1ms TTL=150
Reply from 192.168.0.1: bytes=32 time<1ms TTL=150
Request timed out.
Reply from 192.168.0.1: bytes=32 time<1ms TTL=150
Request timed out.
Request timed out.
Reply from 192.168.0.1: bytes=32 time<1ms TTL=150
MSINFO32 in case it helps (seems OK to me, but I am not a hardware expert):
[Conflicts/Sharing]
Resource   Device
I/O Port 0x00000000-0x00000CF7   PCI bus
I/O Port 0x00000000-0x00000CF7   Direct memory access controller
I/O Port 0x000003C0-0x000003DF   Intel(R) 4 Series Chipset PCI Express Root Port - 2E21
I/O Port 0x000003C0-0x000003DF   ATI Radeon HD 4800 Series
IRQ 21   Intel(R) ICH10 Family USB Universal Host Controller - 3A38
IRQ 21   OHCI Compliant IEEE 1394 Host Controller
IRQ 21   TechniSat DVB-PC TV Star PCI
IRQ 23   Intel(R) ICH10 Family USB Universal Host Controller - 3A34
IRQ 23   Intel(R) ICH10 Family USB Enhanced Host Controller - 3A3A
I/O Port 0x0000B000-0x0000BFFF   Intel(R) 4 Series Chipset PCI Express Root Port - 2E21
I/O Port 0x0000B000-0x0000BFFF   ATI Radeon HD 4800 Series
IRQ 16   Intel(R) 4 Series Chipset PCI Express Root Port - 2E21
IRQ 16   ATI Radeon HD 4800 Series
IRQ 16   Intel(R) ICH10 Family USB Universal Host Controller - 3A37
IRQ 16   Standard Dual Channel PCI IDE Controller
IRQ 16   Intel(R) ICH10 Family PCI Express Root Port 2 - 3A42
IRQ 16   Intel(R) ICH10 Family PCI Express Root Port 6 - 3A4A
IRQ 16   ASUS TV880 Video Capture (NTSC)
IRQ 17   Microsoft UAA Bus Driver for High Definition Audio
IRQ 17   Intel(R) ICH10 Family PCI Express Root Port 1 - 3A40
IRQ 17   Realtek RTL8168C(P)/8111C(P) PCI-E Gigabit Ethernet NIC
Memory Address 0xD0000000-0xDFFFFFFF   Intel(R) 4 Series Chipset PCI Express Root Port -
2E21
Memory Address 0xD0000000-0xDFFFFFFF   ATI Radeon HD 4800 Series
IRQ 18   Intel(R) ICH10 Family USB Enhanced Host Controller - 3A3C
IRQ 18   Intel(R) ICH10 Family USB Universal Host Controller - 3A36
IRQ 19   Intel(R) ICH10 Family USB Universal Host Controller - 3A39
IRQ 19   Intel(R) ICH10 Family USB Universal Host Controller - 3A35
IRQ 19   Intel(R) ICH10 Family 4 port Serial ATA Storage Controller 1 - 3A20
IRQ 19   Intel(R) ICH10 Family 2 port Serial ATA Storage Controller 2 - 3A26
Memory Address 0xA0000-0xBFFFF   PCI bus
Memory Address 0xA0000-0xBFFFF   Intel(R) 4 Series Chipset PCI Express Root Port - 2E21
Memory Address 0xA0000-0xBFFFF   ATI Radeon HD 4800 Series
Memory Address 0xFED90000-0xFED93FFF   System board
Memory Address 0xFED90000-0xFED93FFF   System board
I/O Port 0x000003B0-0x000003BB   Intel(R) 4 Series Chipset PCI Express Root Port - 2E21
I/O Port 0x000003B0-0x000003BB   ATI Radeon HD 4800 Series
[IRQs]
Resource   Device   Status
IRQ 9   Microsoft ACPI-Compliant System   OK
IRQ 16   Intel(R) 4 Series Chipset PCI Express Root Port - 2E21   OK
IRQ 16   ATI Radeon HD 4800 Series   OK
IRQ 16   Intel(R) ICH10 Family USB Universal Host Controller - 3A37   OK
IRQ 16   Standard Dual Channel PCI IDE Controller   OK
IRQ 16   Intel(R) ICH10 Family PCI Express Root Port 2 - 3A42   OK
IRQ 16   Intel(R) ICH10 Family PCI Express Root Port 6 - 3A4A   OK
IRQ 16   ASUS TV880 Video Capture (NTSC)   OK
IRQ 17   Microsoft UAA Bus Driver for High Definition Audio   OK
IRQ 17   Intel(R) ICH10 Family PCI Express Root Port 1 - 3A40   OK
IRQ 17   Realtek RTL8168C(P)/8111C(P) PCI-E Gigabit Ethernet NIC   OK
IRQ 21   Intel(R) ICH10 Family USB Universal Host Controller - 3A38   OK
IRQ 21   OHCI Compliant IEEE 1394 Host Controller   OK
IRQ 21   TechniSat DVB-PC TV Star PCI   OK
IRQ 19   Intel(R) ICH10 Family USB Universal Host Controller - 3A39   OK
IRQ 19   Intel(R) ICH10 Family USB Universal Host Controller - 3A35   OK
IRQ 19   Intel(R) ICH10 Family 4 port Serial ATA Storage Controller 1 - 3A20   OK
IRQ 19   Intel(R) ICH10 Family 2 port Serial ATA Storage Controller 2 - 3A26   OK
IRQ 18   Intel(R) ICH10 Family USB Enhanced Host Controller - 3A3C   OK
IRQ 18   Intel(R) ICH10 Family USB Universal Host Controller - 3A36   OK
IRQ 23   Intel(R) ICH10 Family USB Universal Host Controller - 3A34   OK
IRQ 23   Intel(R) ICH10 Family USB Enhanced Host Controller - 3A3A   OK
IRQ 20   Creative SB Audigy 2 ZS (WDM)   OK
IRQ 22   TechniSat DVB-PC TV Star PCI #3   OK
IRQ 0   System timer   OK
IRQ 8   System CMOS/real time clock   OK
IRQ 13   Numeric data processor   OK
IRQ 4   Communications Port (COM1)   OK
IRQ 6   Standard floppy disk controller   OK
IRQ 1   Standard 101/102-Key or Microsoft Natural PS/2 Keyboard   OK
IRQ 12   Microsoft PS/2 Mouse   OK
IRQ 14   Intel(R) ICH10 Family SMBus Controller - 3A30   OK
My detailed computer configurations can be found here: http://alpha.zimage.com/~ant/antfarm/about/computers.txt (primary computer).
Thank you in advance.

Quote from: NovJoe on 02-March-09, 23:10:05
Force your NIC to run at 100Mbps full duplex and see how it goes.
Check your router / switch ports as well as cables.
I will try 100 Mbps if it happens again. So far, it hasn't occurred after installing the driver supplied by MSI's Web site and not RealTek's Web site. The room temperatures even got warmer like 83F degrees.
As for router and switch, what am I checking for? Other computers didn't have any problems. As for cat5 cables, I already tried another one like I said in my original post.

K8600 Printer Cartridge Failure: Printhead or Sensor??

I have an Officejet Pro K8600 that ejects the print cartridge, cartridge light flashes, when I print. The supply levels say 80-100%. This happens even with a new cartridge. The diagnostics say the printheads are "good." I cleaned the print heads three times. All printing (when it does print) is clean and crisp, with no lines. HP support says I need to replace the printheads (yes, they are expired, but print quality is excellent). Office Depot rep says the print sensors are bad and motherboard needs to be replaced (actually says printer needs to be replaced, as it's not worth fixing). I love the printer (when it's not acting up) and speed and print quality is great. I don't want to pay $150 for two new printheads if this is not the problem. So, if print quality is fine, and cartridges are being ejected automatically in the middle of printing, is this a printhead problem or sensor problem? Thanks for any insights you might have on this....not ready to buy a printer for one that is only 2 years old.

Hi there,
This can usually be resolved by cleaning the printhead thuroughly. Check this article out which may help.
Best of Luck!
You can say thanks by clicking the Kudos Star in my post. If my post resolves your problem, please mark it as Accepted Solution so others can benefit too.

MacBook Pro acting weird at startup

Hi,
First of all thank you for reading this, it's quite a long story. And sorry for any grammatical mistakes, I'm Dutch.
Summary
My MBP suddenly has been acting really weird: kernel_task eating 150-200% of the CPU which caused a super slow MBP, power button not working well, and MBP shutdown after ten minutes without touching it and with the battery on 90%. I did a clean install of OS X Lion, some PRAM and SMC resets and removed the MacBookPro7_1.plist file from the system library. The kernel_task high CPU problem is now fixed. But the power button is still not working: most of the time my MBP shuts down three seconds after I push the power button in a first attempt. In the second attempt I hold it for like five seconds and this works. Sometimes it works fine on the first attempt. Restarting the MBP from the desktop works fine. I'm also worried about the random shutdown. What could probably cause the problem with the power button and the MBP shutting down when I don't touch it, and is there a way to fix this myself? I'm not really into tech, so please keep your answer simple.
My MacBook Pro "13 (mid 2010) with OS X Lion has always been a charm since I bought it. I've never had any problems with my MBP until now. Two weeks ago I was going on a holiday and had to check a few things on my MBP in a hurry right before I was leaving. I'm afraid I forgot to turn off my MBP before I went on my holiday, but I can't remember this exactly. When I came back after a week, my MBP started acting weird at startup and then became really slow. The kernel_task was eating my CPU with 200% and I've tried many things to fix the MBP myself but it still isn't working well. I hope you can help me with this.
This is what happened:
1. When I push the power button to start my MBP, the first time it shuts down three seconds after I push the button. After the first attempt I hold the power button for five seconds, and my MBP turns on the right way. After all the fixes I've done this is still an issue.
2. When I finally got my MBP started the first time after my holiday, it was really really really slow. I later found out that the cause was the kernel_task eating my CPU. It was using 150-200% with no applications running.
3. The MBP was acting normally (not slow) in safe mode, but in safe mode I couldn't open some sites in Google Chrome, like Facebook and Google Maps. So this didn't work either (and was not the solution to my problem).
4. I did some things with PRAM and SMC reset but this didn't work.
5. A clean install was already on my mind for weeks, so I decided that this was the right moment. After I did a manual backup (not with Time Machine) I restarted my MBP holding some buttons to startup the OS X Utilities screen. I first erased my Macintosh HD and then I wanted to install Mavericks because that was the only option from the menu. It took me five hours and at the end it came up with a 'can't download Mavericks, try again' screen. The MBP wasn't starting up anymore because OS X Lion was already erased.
6. So I became annoyed and decided to use my original Snow Leopard dvd which came with my MBP. Installing Snow Leopard took me two days!!!!!!!
7. When I finally got Snow Leopard installed, it still was really really slow and the kernel_task was messing up my CPU again.
8. After some hours of searching on the internet, I read the following thing: fixing the kernel_task problem was easy by removing a file from the system library (http://www.rdoxenham.com/?p=259). Of course I've researched this solution because I'm not a fan of changing things in the system. But I decided to give this a try and it worked! Like a charm!
9. I still was on Snow Leopard and decided to upgrade to Lion again, because I did know for sure that my MBP could handle Lion and I wasn't sure with Mavericks. So I first downloaded Lion from the App Store and then opened the installation program. This took me one day again, probably because the file from the system library was put back with the installation of Lion...
10. When I finally got Lion running, the kernel_task was using a high CPU% again so I removed the file from the system library again and restarted my MBP. This worked.
11. I'm working on Lion for a day now and I've installed some applications (Adobe CS5 Master Collection, Office for Mac, updated my 17.000 mails in Mac Mail, and installed some browsers). It's working fine and the kernel_task is at 1-10%. The issue with the power button is still there but sometimes it works fine at the first attempt. Yesterday my MBP suddenly shut down when I didn't touch it for like ten minutes. The battery was still on 90%. Maybe this was caused by the fact that my MBP was running for four days non stop because of the OS X installations, and it was a hot day yesterday.
So this is what I've done so far in this order:
1. First of all I did a manual backup on my external HDD. Not with Time Machine.
2. I tried to restart my MBP multiple times. Restarting from the desktop worked well, but shutting it down and than turning it on with the power button didn't work well.
3. I did PRAM and SMC resets multiple times.
4. I decided to do a clean install and erased my Macintosh HD from the OS X Utilities screen at startup.
5. Then I wanted to upgrade from Lion to Mavericks but Mavericks couldn't be downloaded.
6. I've installed Snow Leopard from the original dvd, this took me two days.
7. I've followed the instructions from http://www.rdoxenham.com/?p=259 (remove the file MacBookPro7_1.plist from the system library) and this worked for my MBP.
8. Because my MBP was working fine again, I decided to upgrade to Lion. This took me one day.
9. My MBP was really slow again: Lion put the MacBookPro7_1.plist back in the system library so I removed it again. This worked.
10. The problem with the power button still holds so I did a SMC reset again. Didn't work. My MBP also shut down yesterday when I didn't touch it for like ten minutes. I hope this was caused by the fact that the MBP was running for four days non stop, and it was a hot day so maybe it was overheated.
So everything is working fine again, but the power button still isn't. Most of the time my MBP shuts down three seconds after I push the power button. In the second attempt I hold it for like five seconds and this works. Restarting the MBP from the desktop works fine, and the kernel_task is now using 1-10%. I'm also worried about my MBP suddenly shutting down. Is there a way to fix this myself?
Thank you!
Regards,
TokkieTor

TokkieTor,
This is the full error message I got from the test:
4SNS/1/40000000: IP0R-9:166
I read that those letters (IP0R) stand for different errors in the hardware, in my case it's something with the Power Bus according to this website: http://www.cnet.com/news/how-to-invoke-and-interpret-the-apple-hardware-tests/.
Again, I'm really not into tech so what is a Power Bus and should I be worried?
what you have is a problem with a sensor which monitors power bus current. The power bus is the main pathway along which electricity travels in your MacBook Pro. If the sensor isn’t individually repairable, then you could have reason to worry — if they tell you that a logic board replacement would be needed, then that could cost hundreds of euros. (One would hope that replacing a sensor would not require a logic board replacement, but only hardware experts can say for sure.)
I think that posts here are only editable for ten or fifteen minutes after replying.

I2C interface (Sensor Data Acquisition) LabVIEW

Hi all!
Hope you are doing great!
Well I have a question which is more about asking all you for an idea!
The Situation:
I have a circuit board which has an On-Off Valve, Digital pressure sensors (manufacturer AMD) and Humidity/Temperature Sensors (make- IST Hygrosens). On the board all the sensors communicate as I2C slave devices and all the data from the sensors is read into an I2C --> USB adapter chip which further connects to the PC via normal USB cable.
Additional to this board, There is a Relay circuit with a simple 1-pole relay which controls an on-off valve on the above Circuit board. This valve is controlled totally separate via a coaxial cable from the relay directly to the Valve. But the relay board has a I2C interface and it also acts as a slave device. The relay board has the same I2C --> USB adapter chip.
Both the Relay board and Sensor board connect via USB to the PC which I suppose is the Master device.
The software code written for this arrangement and Sensor data acquisition is too old and there are a lot of problems coming. I have almost given up troubleshooting..
I now want to translate this automation system onto LabVIEW. I searched the NI website where there is a DAC card called - USB8451 which supports I2C interface... I am a beginner in LabVIEW and cant really make sense out of how should I go about implementing this system on LabVIEW..
If you guys can please help me out to atleast start (like what all hardware I would need etc..), to have a clear picture, it would be great help!!
Looking forward to your inputs and Thank you so much in advance!
Cheers!
Pramit

NI provides a LabVIEW API for the USB8451. If you use the USB8451, you would use the provided API to write a program that controls the USB8451 and you would do all of the I2C communication in your program. This would mean using functions / SubVI's to connect to the USB8451 and then perform I2C operations through it.
If you use USB already on your device, then you would probably use NI-VISA as the driver and have to get / write your own API to talk to the specific device. The manufacturer may have a LabVIEW (or other) API available for talking to the device that you could get. If not, then you would have to understand the details of how to communicate with the device and then write an API using NI-VISA serial functions. This would mean making NI-VISA be the assigned driver for the device and then using VISA Serial functions / SubVI's to send the messages and receive the responses.

VFD noise on other sensor output such as : Thermocouples, Accelerometer, Torque meter

Hi,
I'm using a PCIe-6351 Daq board (and SCB-68) for my test rig. I'm collecting different kinds of sensor outputs through this DAQ board such as temperatures, acceleration, and torque meter output.
beside that, I have connected a VFD (Baldor H2 inventor) using a USB cable to the PC case. I use this VFD to control motor speed. (http://www.baldor.com/products/accontrols/vs_inverter.asp)
Here is my problem:
when I turn on the VFD I get a lot of noise on every signal. This noise is like a peak which repeats every 5-6 seconds.
So it's not 50-60 HZ noise of outlets.
You can see related uploaded video clips on :
http://www.megaupload.com/?d=4NHDIVV7
http://www.megaupload.com/?d=2461Z7KN
I have uploaded some pictures too.
Is there any way that I can filter this noise in Labview? ( I have tried Filtration VI in labview, but couldn't find a correct setting)
How can I get rid of this noise?
I really appriciate your help on this matter.
Thanks.
-Jeff
Attachments:
Pics.zip ‏585 KB

I can very much identify with this issue. I have a test bench with two motors and corresponding Baldor H2 VFD's on it. I have a variety of sensors such as accelerometers, hall effect sensors, and a torque meter. The bench was put together "professionally" but still get this kind of noise.
The *only* sensor that I have this trouble with is the torquemeter. I get an impulsive EMI blast every 12 seconds on this signal with just one drive turned on. With the other drive turned on, the noise is excessive. I have spent weeks troubleshooting assumed ground-loop faults with the torque meter company's tech rep - to no avail.
I have confirmed that this EMI is from the drive. I hooked up a wire to the signal lead of an oscilloscope's VFD (acting as an antenna) and the noise I get on this oscilloscope is very similar to what I get on my torquemeter. (The noise is present only when the drive is powered up)
The noise from the VFD will not be cured by using a low pass filter. Impulsive type events have very broad band noise.
My new approach is to try and use adaptive noise cancellation to get rid of the the VFDs' EMI on the torquemeter. I gather the noise signal on my DAQ card (PCI-7851-R) by plugging just one wire into the positive port of an AI port and tying a 1 mega Ohm resistor from that port's ground to the AI port; this provides a means of collecting the EMI from the drive with an "antenna." The wire dangles by the side of the VFD with the other end taped up. See the following for a description of adaptive noise cancellation with labview (also possible on an NI FPGA device):
http://zone.ni.com/reference/en-XX/help/372357A-01/lvaftconcepts/aft_noise_cancel/
I believe this to be the only sound signal processing means of addressing this issue. I am still struggling to get it to work myself. I'll advice as I progress.
Cheers
Jordan McBain, PhD
LabVIEW Controls Engineer
Revolutionary Engineering

My NI-6031E card acts as if the multiplexer is stuck.

Dear Folks,
My NI-6031E 64 channel card acts as if the multiplexer is sticking. I see the same voltages on little groups of 2-3 channels. All the channels are connected to inputs, and there are no overvoltages. The output impedence of the sources should be low, because its the output of an op amp from some optical sensor boxes we build in-house. So all the things listed in the knowledgebase as possible causes are eliminated. I even tried replacing the cable, based on a suggestion from someone on info-labview, but that had no effect. I also ran the on-line E-series diagnostic and all checked out fine.
Now here is the kicker. These same exact systems, same sensor hardware, same cards, have run for the last 5 years in Macs with never a sign of this problem. Now we decide to migrate to PC's running WinXP, and we run into this very large snag. Any helpful ideas out there?
Thanks,
Alvin.

AWMoore,
I have an idea about what might be happening.
When you swtiched from Mac machines to PC machines, you changed the DAQ
driver. If you currently are using NIDAQmx 7.5, your
interchannel delay will be set to a minimum value. In previous
versions of the DAQ driver the interchannel delay was set to round
robin by default which meant the interchannel delay was always the
maximum value. The decrease in interchannel delay might not be
giving your channels enough settling time and thus causing your problem.
There are a few easy ways to test this
1. Change the interchannel delay (convert clock rate) using property nodes, so that it is longer.
2. Remove every other sensor and short the input to the DAQ card it was using (the problem should go away).
To calrify, interchannel delay is the amount of time between each channel's sample.
For example (I am pretty sure you know what interchannel delay is, but
this is for other people who might be reading the posting.):
If you are using 10 analog inputs and are sampling at 10 Hz, a
sample from each channel will be taken every 100 ms. Since the
channels are multiplexed to the same ADC, the samples cannot be taken
at the exact same time. So, we have to take 10 samples one after
another within the 100 ms. In the past we would spread the 10
samples out across the entire 100 ms. This would result in a
sample taken from a channel every 10 ms. Now, we take the samples
as fast as possible. This means that at the beginning of the 100
ms period we take 10 samples with a delay of something like 5 us
between each channel. After the 10 samples are taken (this would
take 5 us times 10 samples = 50 us) the DAQ board does nothing for the
rest of the 100 ms period (99.95 ms would be left over) and then would
repleat the process for the next 100 ms period.
The new setup for the interchannel delay means there is less tolerance
for a sensor's impeadance, but it also means that the samples are taken
at much closer to the same time as one another. Like I said
above, this is just the default setting and it can be changed within
LabVIEW using property nodes (DAQmx Timing Property Node: more->AI
Convert->Rate).
This is just a shot in the dark, but it was what came to my mind
as a possible cause for your problem. I realize you said your
sensors are low impeadance, but they may not be low enough. It is
worth a try.
Lorne Hengst
Application Engineer
National Instruments

4.1 update completely screwed my proximity sensor

I have an iPhone 4 and never suffered any issue with the proximity sensor.
After the 4.1 update the behavior is totally random. I make several calls and I saw
the screen turn on and off permanently with the phone a half an inch of my head.
I also noted that the apparently solution implemented by Apple to solve this issue
is add some delay in the operation of the sensor. I see that the response is slow.
Any one with this problem too?
Thanks!

Test 3 is the main test, simply because it is fairly consistent and is one of the quickest ways to get the worst results. The other tests are essentially variations, such as the one where it shows the problem even if you don't move it fast after the screen comes on.
You're the first one to provide feedback with something besides 4.1 so I really appreciate it.
Okay, so it turns off between 1.25 and 1.5. Almost every test I've done or I've seen reported with 4.1 has it turn off at 2 inches. I have had as high as 2.5 once and been a bit below 2 a couple times. If I ever got down to 1.5, it was only once.
This fits various comments made when the phone first came out - that the screen lights up sooner than prior phones and I think your numbers match some of those reports.
For this part of the test, if you haven't upgraded yet, I would just say run it a few more times from scratch - I don't even know if that OS does a reset if pulled far away for a few seconds, though I suspect it does. The repetition helps us recognize if one try is giving unusual results.
You said you dropped the card and that the screen reactivated at 5/8". Did you just do that once? Or, after it lit up again, did you drop it again and see if it kept getting lower? This is what I did on my video - I could keep getting it lower and lower, at least to a certain point.
Also, when you raise it and the screen comes on, you could also slowly put it back down to see where it is before turning OFF again. I suspect that if it turned on at 5/8" that it will stay on down below a half inch. That is, ultimately, the critical figure.
If you really want to take the time, you could also just try making some regular call and see if it acts up (I find I need to turn the brightness up all the way to really see it without having to make a special effort to look out of the corner of my eye).
But some people won't have the problem affect them in normal use right away (some almost never). So, unfortunately, a limited testing time on real calls only tells us anything if it is so bad for you that it hits you right away!
When you do upgrade, same tests so we can see how the numbers change. Assuming you aren't one of those who have it get worse, I would expect that your starting distances are higher and, maybe, it either takes more up and down action to get it as low or it never gets as low - or both. Knowing how low you can get it now is really important for comparison later.
Of course, once updated, you have the experience in the real world on every call you make thereafter for that part.
Now, I really hope you don't start with a working phone (from the numbers you gave so far, I would say it isn't) and then, after 4.1, have it stop working right.
But if that happens, the data you can then give from this test will be the most important we could have at this point.
Thanks.

Sensor acting up

Similar Messages

Maybe you are looking for