Can't Update Apex Firmware?

[drummereef]

Attempting to update the Apex firmware to 4.03 but the process keeps timing out. Here's what I've done so far to initiate the install.

1. I've checked the arp -a in DOS and there is only 1 interface and address listed. I don't have any other network adapters that I can think of but don't know exactly where to look to see.

2. I've tried to force install by unplugging the base unit and plugging it back in during installation but that also did not work.

The connection is established with proper login but the boot loader doesn't start.

Suggestions/Help? :confused:

[aquamanic]

disable your wireless adapter.

Are you running XP?

[drummereef]

Yes XP Home. It's a desktop. How do I disable the wireless adapter?

[aquamanic]

Go into the control panel, network properties. Select the wireless adapter, right click and select disable. I'm going a little from memory since I don't run XP.

[drummereef]

OK all I see in the Network Connections is Internet Connection (internet gateway), Local Area Connection and 1394 Connection. I'm assuming neither of these are wireless adapters?

[aquamanic]

Just saw you said it's a desktop. It probably doesn't have wireless.

Can you copy/paste the results of these two DOS commands:

arp -a
ipconfig /all

[drummereef]

Here's the arp -a. Still working on ipconfig/all.... give me a minute.

Interface: 192.168.1.2 --- 0x2
Internet Address Physical Address Type
192.168.1.1 00-13-10-96-b9-fb dynamic

[drummereef]

arp -a

Interface: 192.168.1.2 --- 0x2
Internet Address Physical Address Type
192.168.1.1 00-13-10-96-b9-fb dynamic


ipconfig/all

Windows IP Configuration

Host Name . . . . . . . . . . . . : desktop
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connecti
on
Physical Address. . . . . . . . . : 00-07-E9-D2-C3-9F
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.224
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 68.94.156.1
68.94.157.1
Lease Obtained. . . . . . . . . . : Tuesday, June 15, 2010 1:33:15 AM
Lease Expires . . . . . . . . . . : Wednesday, June 16, 2010 1:33:15 AM

[aquamanic]

Your controller is hard-wired to your router?

[drummereef]

Yes, with a Cat5e cable. And I'm able to connect to the Apex over the network and internet.

[drummereef]

Another question... How long after re-boot does it typically take for the display to show stats? Seems like it takes an awfully long time for my display. I can log into the Apex over the network and it seems to be connected and fine but the physical display is flashing like it's trying to load.

[aquamanic]

It could take up to a minute for the display to come back after a reboot. It has its own firmware that it gets from the base module.

On your other problem, you've got some sort of conflict on the network. The controller can only establish a link with the loader if they're both on the same subnet and there's no other subnets declared. The new firmware is much more tolerant but that doesn't help you now.

Here's what I would do:

- first, reboot your router, PC and Apex in that order. Make sure you give each one ample time to restart and load their software.
- then try the firmware load.

If that doesn't work, reboot the PC into 'Safe Mode with Networking'. To do this, you usually press F5 or F8 during reboot. That will interrupt the boot cycle and present you with a menu where you can pick that option. After that, try your firmware load.

If neither of those work, post back and somebody with more network experience than me can weigh in on what to look for.

[drummereef]

I appreciate all the help Alan but unfortunately no dice. :( I talked to Curt on the phone and he also suggested "safe mode w/networking" but that didn't work either. He's at lunch but supposed to be calling back. Somewhere along the way I've lost the display too. Probably an issue with the uploader not completing or the base unit still thinks it's in boot mode or something. Luckily I can still login to via my browser to view stats.

If anyone else has suggestions, I'm open.

[aquamanic]

Curt will get you going. Post back as to what the solution was. May help someone else.

[drummereef]

IT WORKS!!! :beer: I spoke with one of the techs at Neptune and he got the update to load and the display to work again. Hooray!

Basically I had to configure my IP and DNS settings manually in XP instead of having XP automatically obtain an address. These are under the Internet Protocol (TCP/IP) settings in the control panel. For some reason an extra display was loaded onto the system which was probably causing an issue with it loading properly. I updated the firmware of the display and deleted the old one, now it works. :)

[aquamanic]

That's good to hear. I'm curious as to what was going on with XP on your desktop but you're working now, that's the important part. Good luck!

[drummereef]

Apparently it had something to do with the subnet mask. Normally the subnet will be 255.255.255.0, but mine for some reason was set at 255.255.255.224. I believe it is because my DSL modem is set on "bridged" mode so it's compatible with my Linksys router (just a guess). When we assigned a specific IP address and changed the subnet mask to .0 it worked. Strange because the subnet mask was the same as what was in the Net settings on the Apex so I don't exactly know why it wouldn't translate but for whatever reason it likes .0 instead.

[RussM]

I understand why the firmware update would fail with that non-standard subnet masking. While common in enterprise networks, variable-length subnet masks are highly unusual for home networks, which almost always use "natural" or "whole boundary" masks, i.e. 255.255.255.0

Based on the equipment & usage you describe, I cannot conceive a good reason why it might be configured that way. You could probably reconfigure to use a standard Class C (255.255.255.0) mask and avoid the hassle with future firmware upgrades.

[aquamanic]

I should have seen the subnet mask in the ipconfig /all. I was looking for other adapters and went right by it.

You probably don't need a static address though. The mask was the problem.

[drummereef]

Do you think the mask is necessary for my router to function properly or is it a completely separate issue?

[aquamanic]

If your router is working correctly now, then obviously that other mask is not necessary.

That other mask (255.255.255.224) was creating a second subnet, something the Apex can't deal with. The mask you have now (255.255.255.0) provides for a single subnet with 1-255 nodes or devices. Plenty for the home.

[drummereef]

OK I went into my router and changed the mask to 255.255.255.0 and it looks like everything is functioning properly. Hopefully that will take care of future firmware upgrade issues. :) Don't ask me why it was set up that way, I have no idea. But at least it all works with a "normal" mask now.