This has been happening to me for a long time now.

When I hook up my datalogit for some street tuning the commander freezes. I guess this is normal. My commander tends to revet back to the APEXI logo and stay that way for a days and then begins to work normal when it feels it like it.

Is there a way to get it to work correctly? Should I be "disconnecting" the laptop in a certain way?

 

When logging, mine freezes, but does not revert to the apexi splash screen.

Logging stops and commander directly comes back online.

I wish the commander could get a feed simultaneously!

 

Another thing, mine has reverted to the apexi splash, but only when the plug is not pushed in all the way.
Not sure if this is relevant, but maybe there is a defect that mimics this scenario.

 

Your laptop is fast enough to lock out the commander while its datalogging. If you had a slower laptop you'd be able to still use your commander. I have a P1-133 I can sell ya.

 

Thanks guys. I'll check the connections. As ususal my commander was off-line for about two days and then it's back again...weird & annoying.

 

So if a slower computer is used, the commander can read data at the same time the datalogit is logging?

What speeds {I am assuming down in the Mhz range) will allow this?
Does your logging resolution decrease significantly?

does anyone know if you can throttle down a faster computer to allow this if it is needed at times?

 

I run a P-133 (don't laugh!) and I can barely tell the commander's slower. And yes...I see now the sample rate sucks. I made the mistake of using a 3.0GHz laptop Friday night and the sample rate was insane. Probably 2.5 times more samples per second. It completely locked out the commander. Now I gotta upgrade.