Home/Support/Support Forum/Problem with ConnectProg with the new firmware 82001116_h
Welcome to Digi Forum, where you can ask questions and receive answers from other members of the community.

Problem with ConnectProg with the new firmware 82001116_h

0 votes
Hello,

I am using the software "connectprog.exe" to make several operation on the DigiConnectME 2MB -S.

One of these operation is the download of a defaults.rci file and the factory settings restoration.

With old firmware (82000867_G), my commands are perfectly done, and my module is correctly configured with my own parameters :

connectprog /upload /destip=xxx.xxx.xxx.xxx /username=custom /password=custom /custom=defaults.rci

connectprog /defaults /destip=xxx.xxx.xxx.xxx /username=root /password=dbps

connectprog /reboot /destip=xxx.xxx.xxx.xxx /username=root /password=dbps

Now, with the firmware 82001116_h, when the command with /defaults is done, I receive this message :

Device found
Connect to device: SUCCESS
Restora factory defaults: FAILED
ERROR: Failed to restore factory defaults.

After that, the module's parameters are set to DIGI's one, and all my configuration is lost. The IP address is set to DHCP, and I don't have DHCP server so the IP address is randomized. If I made an hard reset (by unplug and re-plug the power line), my parameters are restored because the command with /upload is correctly done and my file was correctly uploaded.

This is a big problem for me because I have sent to my clients a batch file which uses the connectprog software and if they upgrade the ConnectME firmware this batch does not work anymore.

Is there a special command in connectprog to keep network configuration when doing a factory restoration ?

I have try to make a new "default.rci" file by the new firmware but the problem is always here.

When I try to make the factory restoration by the web page, it is working only if the button "keep network setting" is checked. Otherwise the webpage is never refreshed and I return to the same problem as with connectprog.exe (all is deconfigured).

Please help me !
asked Jun 20, 2007 in Plug N' Play by Thomas_Bernard New to the Community (9 points)
recategorized Dec 18, 2013 by tuxembb

Please log in or register to answer this question.

2 Answers

0 votes
Unfortunately the problem you're talking about is related to the new Treck stack. It re-acts on all network changes immediately unlike the old Fusion stack. The connect programmer is erroring out (or actually timing out) since it doesn't get an RCI response back from the Connect ME saying it has finished factory defaulting the module.
answered Jun 20, 2007 by charliek Veteran of the Digi Community (408 points)
0 votes
Ok, but my real problem is that It re-acts with the parameters defined by digi, and not with my parameters specified in the defaults.rci I sent before.
answered Jun 21, 2007 by Thomas_Bernard New to the Community (9 points)
...