Products > Test Equipment

Agilent E7495 linux root account

<< < (35/91) > >>

TheSteve:
I am thinking that the GPS used to lock fine on the E7495A as that surely would have been a fixed bug if it was always present. I also didn't find any service note related to it.

technogeeky:
I learned a little bit more. First:

* We can be 100% sure the time resetting is caused by elgato itself.
* If you kill elgato and run your own copy, you get a shell. This isn't the most friendly shell, but we might be able to find useful commands by searching through the elgato binary.

First of all, we can directly see this system time problem:

System time less than minimum allowed. Setting clock to Thu Jan  1 00:00:00 2004

Second, we can do the one thing they suggest doing, which is:

debugIPub=1; (or 2, or maybe 3?)


--- Code: ---Samplers/timeLicense.p1 publishing {argArray with 10 elements} as 'timeLicense'
gui1.s23 receiving data as timeLicense

System time less than minimum allowed. Setting clock to Thu Jan  1 00:00:00 2004

Samplers/timeFreqRef.p1 publishing {argArray with 10 elements} as 'timeFreqRef'
gui1.s9 receiving data as timeFreqRef

--- End code ---


With the same setting to 2, we get:


--- Code: ---Samplers/timeFreqRef.p1 publishing {argArray with 10 elements} as 'timeFreqRef'
<ArgArray length="10">
<UInt32>1</UInt32>
<UInt32>1072915200</UInt32>
<Int32>3397774</Int32>
<Int32>-8440589</Int32>
<Int32>32993</Int32>
<Int32>4</Int32>
<UInt32>2</UInt32>
<UInt32>1</UInt32>
<UInt32>0</UInt32>
<UInt32>3</UInt32>
</ArgArray>

--- End code ---

We've seen this before, this is the data gotten directly from the GPS unit STIM.

And we also get:

--- Code: ---Samplers/timeLicense.p1 publishing {argArray with 10 elements} as 'timeLicense'
<ArgArray length="10">
<Int32>-1</Int32>
<Int32>-1</Int32>
<Int32>-1</Int32>
<Int32>-1</Int32>
<Int32>-1</Int32>
<Int32>-1</Int32>
<Int32>-1</Int32>
<Int32>-1</Int32>
<Int32>-1</Int32>
<Int32>-1</Int32>
</ArgArray>

--- End code ---

I don't think turning off the hack has any effect on this problem, but maybe someone should double check that.

In any case, there are a *bunch* more symbols to turn on and off. Certainly anything that starts with debug. I'll keep looking...










kirill_ka:
Today I have some progress in decoding serial protocol used to communicate with power meter.
Below is the shell command to enable 50 MHz power reference. GUI shouldn't be in power meter mode while you run it.

--- Code: ---(stty 38400; sleep 2; printf "\x83\xf8\x04\x08\x01\x00\x01") < /dev/ttyS4 > /dev/ttyS4
--- End code ---
Turn it off with

--- Code: ---(stty 38400; sleep 2; printf "\x83\xf8\x04\x08\x01\x00\x00") < /dev/ttyS4 > /dev/ttyS4
--- End code ---
However, it turns off when you open the port. Opening the serial port seems to reset some power meter state.

Puffin:
Has anyone else had issues with the remote GUI not responding to clicks on the right-side buttons?   I had it working once, but struggling to make those buttons work again which severely limits what you can do with the GUI.

On the subject of the date reset, it's every 30 seconds, not every 60.  Done by the elgato process itself (killing that stops the time getting reset anyway).    A crude hack to run hwclock --hctosys every few seconds is a kind of work-around.

I'm also noticing the GPS seems somewhat unreliable - and even when it does get 6 sats locked, I've never seen the GPS indicator with anything other than the yellow triangle.

I'll likely prod at this some more, but I'm somewhat nervous to try hacking things further due to fear of bricking this otherwise nicely functional kit.

lectrohamlincoln:
Hello Everybody,

I picked up an E7495A described as "LOCKS UP ON POWER UP." I suspected that the firmware was corrupted and it would be easy enough to flash the latest A.06.25 version. I've tried using both a Sandisk 512MB and a 8Gb Compact Flash formatted to FAT32. With no luck :(

So, I followed the "Update via Load Firmware Utility" procedure described in the Service Guide. I removed the RF section and set the DIP Switch as instructed. I tried again with both Sandisk CFs, but my E7495A would only turn on with a blank display. Is it possible this factory reset requires a PCMCIA instead of CF?

I'm beginning to suspect there might be a hardware problem. I also noticed that there was a red LED lit on the controller board. I'm hoping for any suggestions before I start doing a component level debug tomorrow.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod