Author Topic: Agilent E7495 linux root account  (Read 89207 times)

0 Members and 1 Guest are viewing this topic.

Offline Urs42

  • Supporter
  • ****
  • Posts: 142
  • Country: ch
Re: Agilent E7495 linux root account
« Reply #50 on: February 25, 2015, 08:07:21 am »
Quote
The setting can be changed in the setup but it has to be done for each mode, and even then will often revert back to white.
It would be great if someone figured out a way to make black background the default.

Warning: Changes in /flash are permanent! You can brick your device! Don't change anything there if you are not sure what you are doing. Before you do anything there, use tar to back up all files from /flash to the CF or PCMCIA card!

In my first post i mentioned that the power up settings are stored in /flash/egServer/registry/Powerup/ i think that you can't change the powerup configuration with the GUI, but you can configure the device, save the configuration to a profile an then use telnet to copy your profile to /flash/egServer/registry/Powerup/. All profiles are stored as supdirectories of /flash/egServer/registry/

Quote
Must be some of E7495B Linux setting ?

I'm sorry, i can't see anything wrong from here, it's not easy to debug stuff like this without a way to reproduce the issue. I think the Linux on the E7495B isn't the issue here, It could be a hardware issue with your E7495B or some problem with your Network or Computer(s).
 

Offline Wuerstchenhund

  • Super Contributor
  • ***
  • Posts: 3055
  • Country: gb
Re: Agilent E7495 linux root account
« Reply #51 on: February 25, 2015, 08:23:39 am »
i think that you can't change the powerup configuration with the GUI

Sure you can. Just save your preset as "powerup"  ;)

However this doesn't seem to help for the screen capture background setting, which still seems to revert to white.

I also couldn't find a parameter for it in the registry, but maybe I just didn't look hard enough or overlooked something.
 

Offline 9aplus

  • Regular Contributor
  • *
  • Posts: 124
Re: Agilent E7495 linux root account
« Reply #52 on: February 25, 2015, 09:04:01 am »
Yes, GPS does it automatically.
In that case that is not stored on hwclock or there is no clock backup battery... because my unit was on GPS couple days ago.

I'm sorry, i can't see anything wrong from here, it's not easy to debug stuff like this without a way to reproduce the issue. I think the Linux on the E7495B isn't the issue here, It could be a hardware issue with your E7495B or some problem with your Network or Computer(s).
Thank you for your kind efforts  :-+
No rush... after all, with all this I am refreshing my Unix know how :)
With CF use can pick up necessary data for now... and remote is in to do list.
E7495B must be capable on VXI or USBTMC commands, that may be also god solution for my future remote...

Considering from last night one other way to bring E7485B version of egclient.jar
to Ubuntu PC...  by simple copy on CF card, but
path ->
on /flash/mnt/cf/
>ls -al
.
..
empty folder! (some data like screns, xls and update files are on CF for sure....

Anyone, what is right path for my CF card?
Quote
enable_irq(114) unbalanced from c032558c
Trying to free nonexistent resource <ce8a6000-ce8a600f>
hda: SILICONSYSTEMS INC 128MB, ATA DISK drive
ide0 at 0xce8a6000-0xce8a6007,0xce8a600e on irq 114
hda: 254208 sectors (130 MB) w/0KiB Cache, CHS=993/8/32
Partition check:
 hda: hda1
ide_cs: hda: Vcc = 3.3, Vpp = 0.0
enable_irq(115) unbalanced from c032558c
Trying to free nonexistent resource <ce8b7000-ce8b700f>
hdc: TS8GCF133, ATA DISK drive
ide1 at 0xce8b7000-0xce8b7007,0xce8b700e on irq 115
hdc: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: task_no_data_intr: error=0x04 { DriveStatusError }
hdc: 15662304 sectors (8019 MB) w/1KiB Cache, CHS=974/255/63
 hdc: hdc1
ide_cs: hdc: Vcc = 3.3, Vpp = 0.0
 hda: hda1
 hda: hda1
VFS: Can't find ext2 filesystem on dev ide0(3,1).
 hda: hda1
 hda: hda1
cramfs: wrong magic
 hda: hda1
 hda: hda1
 hdc: hdc1
 hdc: hdc1
VFS: Can't find ext2 filesystem on dev ide1(22,1).
 hdc: hdc1
 hdc: hdc1
cramfs: wrong magic
 hdc: hdc1
 hdc: hdc1
 hda: hda1
 hda: hda1
VFS: Can't find ext2 filesystem on dev ide0(3,1).
 hda: hda1
 hda: hda1
cramfs: wrong magic
 hda: hda1
 hda: hda1
 hdc: hdc1
 hdc: hdc1
VFS: Can't find ext2 filesystem on dev ide1(22,1).
 hdc: hdc1
 hdc: hdc1
cramfs: wrong magic
 hdc: hdc1
 hdc: hdc1

Asking because >mount
report same devices with and without PCMCIA and CF card plugged on E7495B
no >lsblk to find out, any other way to do it?
Quote
[root@E749xx /root]$mount
rootfs on / type rootfs (rw)
/dev/root on / type ext2 (rw)
/proc on /proc type proc (rw)
none on /dev/pts type devpts (rw)
/dev/mtdb3 on /flash type jffs2 (rw)
« Last Edit: February 25, 2015, 03:21:37 pm by 9aplus »
 

Offline Wuerstchenhund

  • Super Contributor
  • ***
  • Posts: 3055
  • Country: gb
Re: Agilent E7495 linux root account
« Reply #53 on: February 25, 2015, 03:45:37 pm »
Yes, GPS does it automatically.
In that case that is not stored on hwclock or there is no clock backup battery... because my unit was on GPS couple days ago.

I didn't check but without a charged battery in the battery bays or PSU power it will probably forget the date/time as I doubt it has a separate backup battery.

Quote
Considering from last night one other way to bring E7485B version of egclient.jar
to Ubuntu PC...  by simple copy on CF card, but
path ->
on /flash/mnt/cf/
>ls -al
.
..
empty folder! (some data like screns, xls and update files are on CF for sure....

You *did* mount the card in the E7495 before you tried to access it, didn't you?

Quote
Anyone, what is right path for my CF card?

Now that's really easy. It says it right there (I highlighted the relevant part in bold):

Quote
enable_irq(114) unbalanced from c032558c
Trying to free nonexistent resource <ce8a6000-ce8a600f>
hda: SILICONSYSTEMS INC 128MB, ATA DISK drive
ide0 at 0xce8a6000-0xce8a6007,0xce8a600e on irq 114
hda: 254208 sectors (130 MB) w/0KiB Cache, CHS=993/8/32
Partition check:
 hda: hda1
ide_cs: hda: Vcc = 3.3, Vpp = 0.0
enable_irq(115) unbalanced from c032558c
Trying to free nonexistent resource <ce8b7000-ce8b700f>
hdc: TS8GCF133, ATA DISK drive
ide1 at 0xce8b7000-0xce8b7007,0xce8b700e on irq 115
hdc: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: task_no_data_intr: error=0x04 { DriveStatusError }
hdc: 15662304 sectors (8019 MB) w/1KiB Cache, CHS=974/255/63
 hdc: hdc1

ide_cs: hdc: Vcc = 3.3, Vpp = 0.0
hda: hda1
 hda: hda1
VFS: Can't find ext2 filesystem on dev ide0(3,1).
 hda: hda1
 hda: hda1
cramfs: wrong magic
 hda: hda1
 hda: hda1
 hdc: hdc1
 hdc: hdc1
VFS: Can't find ext2 filesystem on dev ide1(22,1).
 hdc: hdc1
 hdc: hdc1
cramfs: wrong magic
 hdc: hdc1
 hdc: hdc1
 hda: hda1
 hda: hda1
VFS: Can't find ext2 filesystem on dev ide0(3,1).
 hda: hda1
 hda: hda1
cramfs: wrong magic
 hda: hda1
 hda: hda1
 hdc: hdc1
 hdc: hdc1
VFS: Can't find ext2 filesystem on dev ide1(22,1).
 hdc: hdc1
 hdc: hdc1
cramfs: wrong magic
 hdc: hdc1
 hdc: hdc1

It seems you're using a Transcend 8GB 133x Compact Flash card. But the error messages shouldn't be there.

Is the card formatted properly (FAT32)?

Quote
Asking because >mount
report same devices with and without PCMCIA and CF card plugged on E7495B
no >lsblk to find out, any other way to do it?
Quote

Easy:

Code: [Select]
# mount /dev/hdc1 /mnt
If you want to access the PCMCIA flash card (or a CF card in a PCMCIA adapter) then it's /dec/hda1 instead.
« Last Edit: February 25, 2015, 03:52:28 pm by Wuerstchenhund »
 

Offline Urs42

  • Supporter
  • ****
  • Posts: 142
  • Country: ch
Re: Agilent E7495 linux root account
« Reply #54 on: February 25, 2015, 04:08:51 pm »
Quote
I didn't check but without a charged battery in the battery bays or PSU power it will probably forget the date/time as I doubt it has a separate backup battery.

Some init script stores date and time at shutdown to a file in /flash, this date will be restored at the next boot.

Quote
hdc: TS8GCF133, ATA DISK drive
ide1 at 0xce8b7000-0xce8b7007,0xce8b700e on irq 115
hdc: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: task_no_data_intr: error=0x04 { DriveStatusError }
hdc: 15662304 sectors (8019 MB) w/1KiB Cache, CHS=974/255/63
 hdc: hdc1

I'm not sure if this is a critical error, some CF/PCMCIA cards will produce errors like this one, because they don't understand all command that the kernel sends to them while initializing the card.



 

Offline 9aplus

  • Regular Contributor
  • *
  • Posts: 124
Re: Agilent E7495 linux root account
« Reply #55 on: February 25, 2015, 05:32:38 pm »
CF card is formated properly. That's the same one from which update to A.06.25 is performed

Well

I didn't check but without a charged battery in the battery bays or PSU power it will probably forget the date/time as I doubt it has a separate backup battery.

You *did* mount the card in the E7495 before you tried to access it, didn't you?

My date went crazy again, both accu was inside unit....
Quote
[root@E749xx /root]$date
Wed Feb 25 02:10:32 UTC 2015
[root@E749xx /root]$hwtime
bash: hwtime: command not found
[root@E749xx /root]$hwclock
Wed Feb 25 06:53:49 2015  -0.763275 seconds
[root@E749xx /root]$


Well my expectation was that the system already done that for me....

Thank you to both of you :)
Must try advices, than report later....
« Last Edit: February 25, 2015, 05:39:48 pm by 9aplus »
 

Offline 9aplus

  • Regular Contributor
  • *
  • Posts: 124
Re: Agilent E7495 linux root account
« Reply #56 on: February 25, 2015, 05:52:51 pm »
Done... on second attempt after reboot
 
Quote
[root@E749xx /root]$mount /dev/hdc1 /mnt
[root@E749xx /root]$mount
rootfs on / type rootfs (rw)
/dev/root on / type ext2 (rw)
/proc on /proc type proc (rw)
none on /dev/pts type devpts (rw)
/dev/mtdb3 on /flash type jffs2 (rw)
/dev/hdc1 on /mnt type vfat (rw)
[root@E749xx /root]$
 

Offline Wuerstchenhund

  • Super Contributor
  • ***
  • Posts: 3055
  • Country: gb
Re: Agilent E7495 linux root account
« Reply #57 on: February 25, 2015, 07:31:56 pm »
Some init script stores date and time at shutdown to a file in /flash, this date will be restored at the next boot.

Yes, but that is only to avoid that new files are written with older timestamps than existing files.

Quote
I'm not sure if this is a critical error, some CF/PCMCIA cards will produce errors like this one, because they don't understand all command that the kernel sends to them while initializing the card.

In my experience (I use CF cards a lot for embedded stuff) the Transcend cards are often more problematic than say Sandisk or Apacer. Especially when they are treated as a fixed disk (like in the E7495) and not like a removable device.

However, I have used similar cards (same model, just 1GB and 16GB instead of 8GB) and didn't see such errors.
 

Offline Wuerstchenhund

  • Super Contributor
  • ***
  • Posts: 3055
  • Country: gb
Re: Agilent E7495 linux root account
« Reply #58 on: February 25, 2015, 07:41:32 pm »
Well my expectation was that the system already done that for me....

Both CF and PCMCIA storage remain unmounted until you press the screen shot button or save some measurement data, where the card gets mounted, written to and unmounted. Ever wondered why saving a simple screen shot takes so long? That's why.

This way the cards can be removed while the E7495 is still running.
 

Offline 9aplus

  • Regular Contributor
  • *
  • Posts: 124
Re: Agilent E7495 linux root account
« Reply #59 on: February 25, 2015, 09:30:08 pm »
Last session ->
Quote
E749xx login: root
Password:
[root@E749xx /root]$mount /dev/hdc1 /mnt
[root@E749xx /root]$mount
rootfs on / type rootfs (rw)
/dev/root on / type ext2 (rw)
/proc on /proc type proc (rw)
none on /dev/pts type devpts (rw)
/dev/mtdb3 on /flash type jffs2 (rw)
/dev/hdc1 on /mnt type vfat (rw)
[root@E749xx /root]$cd ..
[root@E749xx /]$cd ..
[root@E749xx /]$ls
bin         flash       linuxrc     nfs         root        usr
dev         home        lost+found  proc        sbin        var
etc         lib         mnt         rd          tmp         xdrive
[root@E749xx /]$cd flash
[root@E749xx /flash]$cd egGui
[root@E749xx egGui]$ls
JimiProClasses.zip  rhino-1.5R4.jar     xerces.jar
egclient.jar        shellexec.log
libguiutil.so       swing.jar
[root@E749xx egGui]$cp egclient.jar /dev/hdc1
[root@E749xx egGui]$umount /dev/hdc1
[root@E749xx egGui]$mount
rootfs on / type rootfs (rw)
/dev/root on / type ext2 (rw)
/proc on /proc type proc (rw)
none on /dev/pts type devpts (rw)
/dev/mtdb3 on /flash type jffs2 (rw)
[root@E749xx egGui]$

This is 4th try and failure.... after >cp on CF card file system is gone, full format on Win PC help to restore... data and screen copy
on same CF goes well....
 

Offline CustomEngineerer

  • Frequent Contributor
  • **
  • Posts: 459
  • Country: us
Re: Agilent E7495 linux root account
« Reply #60 on: February 26, 2015, 02:53:27 am »
Last session ->
Quote
E749xx login: root
Password:
[root@E749xx /root]$mount /dev/hdc1 /mnt
[root@E749xx /root]$mount
rootfs on / type rootfs (rw)
/dev/root on / type ext2 (rw)
/proc on /proc type proc (rw)
none on /dev/pts type devpts (rw)
/dev/mtdb3 on /flash type jffs2 (rw)
/dev/hdc1 on /mnt type vfat (rw)
[root@E749xx /root]$cd ..
[root@E749xx /]$cd ..
[root@E749xx /]$ls
bin         flash       linuxrc     nfs         root        usr
dev         home        lost+found  proc        sbin        var
etc         lib         mnt         rd          tmp         xdrive
[root@E749xx /]$cd flash
[root@E749xx /flash]$cd egGui
[root@E749xx egGui]$ls
JimiProClasses.zip  rhino-1.5R4.jar     xerces.jar
egclient.jar        shellexec.log
libguiutil.so       swing.jar
[root@E749xx egGui]$cp egclient.jar /dev/hdc1
[root@E749xx egGui]$umount /dev/hdc1
[root@E749xx egGui]$mount
rootfs on / type rootfs (rw)
/dev/root on / type ext2 (rw)
/proc on /proc type proc (rw)
none on /dev/pts type devpts (rw)
/dev/mtdb3 on /flash type jffs2 (rw)
[root@E749xx egGui]$

This is 4th try and failure.... after >cp on CF card file system is gone, full format on Win PC help to restore... data and screen copy
on same CF goes well....

Your syntax is a little off. "cp egclient.jar /dev/hdc1" is copying egclient.jar over the hdc1 device, not into it. I didn't think unix/linux would actually let you do that. My guess is that it wrote egclient.jar starting at the beginning of the cf card and overwrote the partition table which is why the file system is gone. The correct syntax would be "cp egclient.jar /dev/hdc1/", notice the trailing front slash after hdc1. Though I still would not recommend doing it this way. I would reformat the the CF card, mount it and then copy it with this command. "cp egclient.jar /mnt/" Again, make sure you get the trailing front slash.
« Last Edit: February 26, 2015, 02:58:03 am by CustomEngineerer »
 

Offline ldhn1uec

  • Newbie
  • Posts: 3
Re: Agilent E7495 linux root account
« Reply #61 on: February 26, 2015, 12:35:57 pm »
New to the group, new to the unit. At the hamcation flea market i picked up 4 units, all "broken", seems they all work to some extent. one has a broken lcd, all took the firmware upgrade. all have slightly different opotions. dissasembled and reassembled cracked unit,  it still works and is useable with remote software. saw some talk of the download issues, check any/all firewall settings on the host pc as the file is pulled from the pc within the java parent. i had trouble until i used the early 1.4 java package. that worked well on xp and still works on w7. starting to look into modifying the options, i'll post results here. i will also mention that since this is an older unit, don't use cf larger than 2g due to changes in sector sizes.  find a 64 or 128 MEG cf card for transfers and you'll have much fewer problems.  hope that helps.

Lou... N1UEC


Sent from my iPad using Tapatalk
 

Offline 9aplus

  • Regular Contributor
  • *
  • Posts: 124
Re: Agilent E7495 linux root account
« Reply #62 on: February 26, 2015, 07:42:56 pm »
@CustomEngineerer thank you, that was useful tip, copy now in order  :-+

Concerning overall progress, something still missing.....  Correct path maybe?

RemoteGui.jar is not able to start egclient.jar, even not when all are within Home folder

When run alone egclient.jar makes this screen, and it is not possible to quit OpenJDK Java 6 Runtime.

 
 

Offline CustomEngineerer

  • Frequent Contributor
  • **
  • Posts: 459
  • Country: us
Re: Agilent E7495 linux root account
« Reply #63 on: February 27, 2015, 01:09:23 am »
@CustomEngineerer thank you, that was useful tip, copy now in order  :-+

Concerning overall progress, something still missing.....  Correct path maybe?

RemoteGui.jar is not able to start egclient.jar, even not when all are within Home folder

When run alone egclient.jar makes this screen, and it is not possible to quit OpenJDK Java 6 Runtime.
 

Glad you were able to get the copy done. For what's going wrong now all I can think of is to make sure that you are starting RemoteGui.jar like Urs42 suggested in Reply #35. Pasting it below. Also note that the command is a little different than when he first suggested it back in Reply #29. Good luck.

Quote
It loos like you are running the command in your home directory, that won't work. Run it in the directory where all the java files are.

I pasted the wrong command line, please replace egclient-patch.jar with egclient.jar

Code: [Select]
java -Dserver=192.168.1.209 -DlocalAddress=192.168.1.205 -classpath "egclient.jar:xerces.jar:JimiProClasses.zip:RemoteGui.jar" elgato.gui.MainWindow
 

Offline 9aplus

  • Regular Contributor
  • *
  • Posts: 124
Re: Agilent E7495 linux root account
« Reply #64 on: February 27, 2015, 12:35:43 pm »
Yes, you are right, just forgot on that advice...

Now all running well  :-+
(except ftp file transfer, but who cares)

Like to thank to all of you. for kind assistance and patience
on this small E7495B tutorial on Java & Linux
 

Offline 9aplus

  • Regular Contributor
  • *
  • Posts: 124
Re: Agilent E7495 linux root account
« Reply #65 on: February 27, 2015, 06:44:39 pm »
Java application running but something is still not good regarding communication ->
Quote
q@ubuntu:~/Desktop$ cd E7495xRemoteGui
q@ubuntu:~/Desktop/E7495xRemoteGui$ java -Dserver=192.168.1.209 -DlocalAddress=192.168.1.205 -classpath "egclient.jar:xerces.jar:JimiProClasses.zip:RemoteGui.jar" elgato.gui.MainWindow
1425060510121 INFO util.Resources Loaded resource file: /elgato/system.properties
1425060510182 INFO util.Resources Loaded resource file: /elgato/gui.properties
1425060510790 INFO util.LocaleManager No locale set, using default.
1425060512755 INFO util.Resources Loaded resource file: /elgato/infrastructure.properties
1425060518929 INFO util.DebugServer DebugServer started on port 5100
1425060519272 INFO gui.MainWindow Display area: java.awt.Dimension[width=472,height=414]
1425060519529 INFO commChannel.DefaultCommandProcessor STATUS: Startup in process...
1425060519725 INFO commChannel.DefaultCommandProcessor STATUS: Startup complete.
1425060521582 INFO commChannel.UDPMeasurementReader Binding to DatagramSocket
1425060521583 INFO commChannel.UDPMeasurementReader Bound to UDP port 37537
1425060522662 INFO mainScreens.ProductFactory Instantiating El Gato Product Factory (class ElgatoFactory)
1425060545849 INFO util.Resources Loaded resource file: /elgato/measurement.properties
1425060599560 WARN commChannel.DefaultCommandProcessor Suspected GUI hang received while waiting for a packet, re-sending readyToReceive
1425060647308 WARN commChannel.DefaultCommandProcessor Suspected GUI hang received while waiting for a packet, re-sending readyToReceive
1425060674497 INFO util.Resources Loaded resource file: /help/help.properties
1425061378924 WARN commChannel.DefaultCommandProcessor Suspected GUI hang received while waiting for a packet, re-sending readyToReceive
1425061738848 WARN commChannel.DefaultCommandProcessor Suspected GUI hang received while waiting for a packet, re-sending readyToReceive
1425062015101 ERROR:  util.FileSystemHelper saveImage(null, /tmpscreenTmp.png, image, true):
null
com.sun.jimi.core.JimiException
   at com.sun.jimi.core.JimiWriter.putImage(JimiWriter.java:242)
   at com.sun.jimi.core.Jimi.putImage(Jimi.java:601)
   at com.sun.jimi.core.Jimi.putImage(Jimi.java:587)
   at com.sun.jimi.core.Jimi.putImage(Jimi.java:575)
   at elgato.infrastructure.util.FileSystemHelper.saveImage(Unknown Source)
   at elgato.infrastructure.util.FileSystemHelper.saveImage(Unknown Source)
   at elgato.infrastructure.mainScreens.PrintScreenMessageScreen.decorateImage(Unknown Source)
   at elgato.infrastructure.mainScreens.PrintScreenMessageScreen.saveScreenImage(Unknown Source)
   at elgato.infrastructure.mainScreens.PrintScreenMessageScreen.printScreen(Unknown Source)
   at elgato.infrastructure.mainScreens.PrintScreenMessageScreen.commitAction(Unknown Source)
   at elgato.infrastructure.mainScreens.MediaMessageScreen.run(Unknown Source)
   at java.lang.Thread.run(Thread.java:701)

1425062015219 ERROR:  widgets.ImageIcon Timed out waiting for image to load
1425062015220 WARN mainScreens.PrintScreenMessageScreen decorateImage: No addition of filename to screen capture image...java.lang.IllegalArgumentException: Width (-1) and height (45) cannot be <= 0
1425062015220 ERROR:  util.FileSystemHelper saveImage(null, /tmp/printScreen_20150127_193334.png, image, true):
null
java.lang.NullPointerException
   at com.sun.jimi.core.Jimi.putImage(Jimi.java:575)
   at elgato.infrastructure.util.FileSystemHelper.saveImage(Unknown Source)
   at elgato.infrastructure.util.FileSystemHelper.saveImage(Unknown Source)
   at elgato.infrastructure.mainScreens.PrintScreenMessageScreen.saveScreenImage(Unknown Source)
   at elgato.infrastructure.mainScreens.PrintScreenMessageScreen.printScreen(Unknown Source)
   at elgato.infrastructure.mainScreens.PrintScreenMessageScreen.commitAction(Unknown Source)
   at elgato.infrastructure.mainScreens.MediaMessageScreen.run(Unknown Source)
   at java.lang.Thread.run(Thread.java:701)

1425062436250 WARN commChannel.UDPMeasurementReader Error reading measurement packet, ignoring: java.net.SocketException: Socket closed
1425062436273 WARN commChannel.UDPMeasurementReader -80 bytes remaining after reading packet
1425062436287 WARN commChannel.UDPMeasurementReader Error reading measurement packet, ignoring: java.net.SocketException: Socket closed
1425062436287 WARN commChannel.UDPMeasurementReader -80 bytes remaining after reading packet
1425062436288 WARN commChannel.UDPMeasurementReader Error reading measurement packet, ignoring: java.net.SocketException: Socket closed
1425062436288 WARN commChannel.UDPMeasurementReader -80 bytes remaining after reading packet
1425062436288 WARN commChannel.UDPMeasurementReader Error reading measurement packet, ignoring: java.net.SocketException: Socket closed
1425062436289 WARN commChannel.UDPMeasurementReader -80 bytes remaining after reading packet
1425062436290 WARN commChannel.UDPMeasurementReader Error reading measurement packet, ignoring: java.net.SocketException: Socket closed
1425062436292 WARN commChannel.UDPMeasurementReader -80 bytes remaining after reading packet
1425062436292 WARN commChannel.UDPMeasurementReader Error reading measurement packet, ignoring: java.net.SocketException: Socket closed
1425062436295 WARN commChannel.UDPMeasurementReader -80 bytes remaining after reading packet
1425062436296 WARN commChannel.UDPMeasurementReader Error reading measurement packet, ignoring: java.net.SocketException: Socket closed
1425062436296 WARN commChannel.UDPMeasurementReader -80 bytes remaining after reading packet
1425062436296 WARN commChannel.UDPMeasurementReader Error reading measurement packet, ignoring: java.net.SocketException: Socket closed
1425062436296 WARN commChannel.UDPMeasurementReader -80 bytes remaining after reading packet
1425062436297 WARN commChannel.UDPMeasurementReader Error reading measurement packet, ignoring: java.net.SocketException: Socket closed
1425062436297 WARN commChannel.UDPMeasurementReader -80 bytes remaining after reading packet
1425062436303 WARN commChannel.UDPMeasurementReader Error reading measurement packet, ignoring: java.net.SocketException: Socket closed
1425062436307 WARN commChannel.UDPMeasurementReader -80 bytes remaining after reading packet
1425062436307 WARN commChannel.UDPMeasurementReader Error reading measurement packet, ignoring: java.net.SocketException: Socket closed
1425062436315 WARN commChannel.UDPMeasurementReader -80 bytes remaining after reading packet
1425062436316 WARN commChannel.UDPMeasurementReader Error reading measurement packet, ignoring: java.net.SocketException: Socket closed
1425062436316 WARN commChannel.UDPMeasurementReader -80 bytes remaining after reading packet
1425062436316 WARN commChannel.UDPMeasurementReader Error reading measurement packet, ignoring: java.net.SocketException: Socket closed
1425062436317 WARN commChannel.UDPMeasurementReader -80 bytes remaining after reading packet
1425062436317 WARN commChannel.UDPMeasurementReader Error reading measurement packet, ignoring: java.net.SocketException: Socket closed
1425062436317 WARN commChannel.UDPMeasurementReader -80 bytes remaining after reading packet
1425062436318 WARN commChannel.UDPMeasurementReader Error reading measurement packet, ignoring: java.net.SocketException: Socket closed
1425062436318 WARN commChannel.UDPMeasurementReader -80 bytes remaining after reading packet
1425062436318 WARN commChannel.UDPMeasurementReader Error reading measurement packet, ignoring: java.net.SocketException: Socket closed
1425062436318 WARN commChannel.UDPMeasurementReader -80 bytes remaining after reading packet
1425062436319 WARN commChannel.UDPMeasurementReader Error reading measurement packet, ignoring: java.net.SocketException: Socket closed
1425062436319 WARN commChannel.UDPMeasurementReader -80 bytes remaining after reading packet
1425062436320 WARN commChannel.UDPMeasurementReader Error reading measurement packet, ignoring: java.net.SocketException: Socket closed
1425062436321 WARN commChannel.UDPMeasurementReader -80 bytes remaining after reading packet
1425062436327 WARN commChannel.UDPMeasurementReader Error reading measurement packet, ignoring: java.net.SocketException: Socket closed
1425062436328 WARN commChannel.UDPMeasurementReader -80 bytes remaining after reading packet
1425062436328 WARN commChannel.UDPMeasurementReader Error reading measurement packet, ignoring: java.net.SocketException: Socket closed
1425062436328 WARN commChannel.UDPMeasurementReader -80 bytes remaining after reading packet
1425062436329 WARN commChannel.UDPMeasurementReader Error reading measurement packet, ignoring: java.net.SocketException: Socket closed
1425062436329 WARN commChannel.UDPMeasurementReader -80 bytes remaining after reading packet
1425062436329 WARN commChannel.UDPMeasurementReader Error reading measurement packet, ignoring: java.net.SocketException: Socket closed
1425062436330 WARN commChannel.UDPMeasurementReader -80 bytes remaining after reading packet
1425062436331 WARN commChannel.UDPMeasurementReader Error reading measurement packet, ignoring: java.net.SocketException: Socket closed
1425062436331 WARN commChannel.UDPMeasurementReader -80 bytes remaining after reading packet
1425062436332 WARN commChannel.UDPMeasurementReader Error reading measurement packet, ignoring: java.net.SocketException: Socket closed
1425062436333 ERROR:  util.DebugServer Couldn't accept connection
Socket closed
java.net.SocketException: Socket closed
   at java.net.PlainSocketImpl.socketAccept(Native Method)
   at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:375)
   at java.net.ServerSocket.implAccept(ServerSocket.java:478)
   at java.net.ServerSocket.accept(ServerSocket.java:446)
   at elgato.infrastructure.util.DebugServer.run(Unknown Source)

1425062436335 INFO util.DebugServer DebugServer stopped
1425062436337 WARN commChannel.UDPMeasurementReader -80 bytes remaining after reading packet
1425062436338 WARN commChannel.UDPMeasurementReader Error reading measurement packet, ignoring: java.net.SocketException: Socket closed
1425062436338 WARN commChannel.UDPMeasurementReader -80 bytes remaining after reading packet
1425062436339 WARN commChannel.UDPMeasurementReader Error reading measurement packet, ignoring: java.net.SocketException: Socket closed
1425062436340 WARN commChannel.UDPMeasurementReader -80 bytes remaining after reading packet
1425062436341 WARN commChannel.UDPMeasurementReader Error reading measurement packet, ignoring: java.net.SocketException: Socket closedq@ubuntu:~/Desktop/E7495xRemoteGui$
 

Offline jwm_

  • Frequent Contributor
  • **
  • Posts: 318
  • Country: us
    • Not A Number
Re: Agilent E7495 linux root account
« Reply #66 on: February 27, 2015, 11:32:32 pm »
got my E7495A for repair but without any accesories or charger. can someone tell me the polarity/voltage of the external power port?

Offline Wuerstchenhund

  • Super Contributor
  • ***
  • Posts: 3055
  • Country: gb
Re: Agilent E7495 linux root account
« Reply #67 on: February 28, 2015, 08:36:15 am »
got my E7495A for repair but without any accesories or charger. can someone tell me the polarity/voltage of the external power port?

24Vdc, positive inside, negative outside
 

Offline Wuerstchenhund

  • Super Contributor
  • ***
  • Posts: 3055
  • Country: gb
Re: Agilent E7495 linux root account
« Reply #68 on: February 28, 2015, 08:51:06 am »
The E7495 firmware looks very much the same as for the N1996 CSA SA

It would be interesting to find out how similar the hardware is, and if some of the capabilities of the N1996A could be transferred to the E7495.
 

Online PA0PBZ

  • Super Contributor
  • ***
  • Posts: 4465
  • Country: nl
Re: Agilent E7495 linux root account
« Reply #69 on: February 28, 2015, 09:11:42 am »
The E7495 firmware looks very much the same as for the N1996 CSA SA

It would be interesting to find out how similar the hardware is, and if some of the capabilities of the N1996A could be transferred to the E7495.

It would be nice to have a service manual for either, but I only found the N1996A one at Agilent for about $400  :palm:
Keyboard error: Press F1 to continue.
 

Offline 9aplus

  • Regular Contributor
  • *
  • Posts: 124
Re: Agilent E7495 linux root account
« Reply #70 on: February 28, 2015, 10:00:55 am »
got my E7495A for repair but without any accesories or charger. can someone tell me the polarity/voltage of the external power port?

24Vdc, positive inside, negative outside
100W PS ->  4+ A current
 

Offline ldhn1uec

  • Newbie
  • Posts: 3
Re: Agilent E7495 linux root account
« Reply #71 on: February 28, 2015, 09:58:00 pm »
so, i have found the power supply can bve almost anything with a + center. the spec for the instrument is 10-24 volts at least 65 watts. 12v 5 amps works fine, as well as 19.8v and 4.14a.

my tinkering is going well. DO NOT ALTER the lower limit of the receivers as that will cause the system to fault. 375 is the actual \low limit. (was trying to squeeze vhf out of the swr bridge).

still comparing the dumps of the 4 units to decode the licensing arrangement. does seem that the only changes are the lic files as the other files are present anyway.

anyone have luck rebuilding or replacing the li-ion batteries?

as far as the remote gui, no joy on java 6, go back to java 1.4.2 and all was well. don't forget the loc/remote button to enable full control from the pc. even with a cracked lcd the remote software allows me to work with it.

so far so good 3/4 are working and 1 works but is -10db on spectrum

not bad for $50 each!



Sent from my iPad using Tapatalk
 

Offline 9aplus

  • Regular Contributor
  • *
  • Posts: 124
Re: Agilent E7495 linux root account
« Reply #72 on: March 01, 2015, 10:45:10 am »
Quote
as far as the remote gui, no joy on java 6, go back to java 1.4.2 and all was well.

You are running 1.4.2 on windows ?
Which one ? My try on Win 7 no luck....
How do you run remote gui on Win os?
 

Offline Urs42

  • Supporter
  • ****
  • Posts: 142
  • Country: ch
Re: Agilent E7495 linux root account
« Reply #73 on: March 01, 2015, 05:31:31 pm »
Quote
my tinkering is going well. DO NOT ALTER the lower limit of the receivers as that will cause the system to fault. 375 is the actual \low limit. (was trying to squeeze vhf out of the swr bridge).

Do you have the A or B model? The range of the E7495B goes from 10MHz to 2.7GHz, but the preamplifiers only go down to 375 MHz. 10MHz is written on the front panel, but i can enter frequencies down to 500KHz.
 

Offline ldhn1uec

  • Newbie
  • Posts: 3
Re: Agilent E7495 linux root account
« Reply #74 on: March 02, 2015, 03:00:39 am »
i have the 7495A. the spectrum analyzers go down fine, the swr bridge/return loss port will not go below 375m

as far as the gui, you need to uninstall java completely, go to the java site archives and get the 1.4.2 java package and install it. then the gui parts work fine. when i get round to it i may try 6.

attempted to swap lic&hostid files with no luck. seems to be more involved. may try the patch listed above.


Sent from my iPad using Tapatalk
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf