No, we are getting a Device not found, that is the issue. Netosprog appears to be ignoring the /ip= parameter on the /firmware command and searches for the device locally and then and only if it finds *any* device on the network it will go ahead and use the /ip specified to program the correct device. When the /ip is specified it should skip the auto search and just use the ip we want to upload to. The auto search only returns devices on our network so when we want to program a remote device we have to have a local device on the network to just trick it out so it will program ours. This I think is the bug Netosprog has and should be fixed.
The first example is my trying to program a bogus ip address and it auto finds one on another ip then because of that it tries to connect via ftp to the one specified on the /ip= (which will fail because I don't want to program it).
The second example is what happens with the same command but with the local test device unplugged. It does not even attempt to program the one specified by the ip parameter.
C:\netos75\bin>netosprog /upload /ip=10.100.1.99 /firmware=image.bin /username=r
oot /password=password
NET+OS Programmer
Version 1.3.15.0
Copyright 2004-2009 Digi International Inc
Searching for devices. Please wait...
Locate device (auto): SUCCESS
Uploading firmware...
Failed to open FTP session with error 12002
C:\netos75\bin>netosprog /upload /ip=10.100.1.99 /firmware=image.bin /username=r
oot /password=password
With the local device disconnected, does not attempt to program the device specified:
NET+OS Programmer
Version 1.3.15.0
Copyright 2004-2009 Digi International Inc
Searching for devices. Please wait...
Locate device (auto): Searching for devices. Please wait...
Locate device (auto): FAILED
ERROR: Device not found.
According to the Netosprog help when specifying /firmware you can specify the device to program using /ip=