How do I download custom audio files from a Netbotz appliance?

[DCIM_Support]

I'm preparing to re-flash my Netbotz 450 and need to save the custom audio file we uploaded to it.

Thanks.

(CID:97485929)

[DCIM_Support]

Hi Dominic,

There is no option to download custom audio from a NetBotz appliance, only upload. I even tried uploading a test file and named it test.wav. File uploaded and is shown in AV fine. I then started a telnet session and did a search through every directory on root for "test.*" .  In every case, I got the following response:

find: test.*: No such file or directory

You'll have to look through the system that had previously uploaded the files if you want the actual files themselves. Without knowing why you're re-flashing the bot (some corruption?), A backup should contain these files.  A restore using a backup from this bot should replace the files on the bot. I've checked and you can not pull the files from the backup either. Restoring a bot that has an issue however will likely bring that issue back.

Steve

(CID:97485966)

[DCIM_Support]

Thanks Steve. We're having an issue where our camera pod keeps "disconnecting", in that it won't show any video or record any clips until we unplug it and plug it back in again. Rebooting the appliance hasn't helped. Tech support suggested re-flashing the appliance, which will wipe the configuration, hence this question. I need to be able to add the custom audio file back if I end up having to redo the config.

Do you know whether doing an update of the firmware will remove all the current setup? If not I'll try an update first before attempting a re-flash.

(CID:97485981)

[DCIM_Support]

Hi Dominic, If the reflash is to fix an issue, I would at least start out with a fresh config to rule out any issue with the system. a re-flash does not necessarily wipe out everything (depends on how it's done) but for this kind of issue, you might want to. I would run a backup first just in case. I'm assuming this is a USB connected camera as you mentioned unplugging it an plugging it back in. If this is the case, I would try a different USB cable. If you have another camera, I would also try swapping cameras. Also, if this is connected to a USB hub, maybe check the hub. Without knowing your exact configuration, I can't say if it's a firmware issue, hardware issue, connection issue, or configuration issue. If the issue doesn't take too long to occur, I'd suggest connecting the camera directly to the bot with no hubs and no other sensors to see if the issue continues. If that fails, reflash. If that fails, try swapping cables then cameras. Maybe even take it out of the current environment to rule out noise, induction, or something else environmental. Still happens? Probably a bad bot. Steve

(CID:97485982)

[DCIM_Support]

Thanks Steve. Unfortunately most of those options aren't available to me. The camera's been working fine for years without any significant changes to the configuration but recently started having this disconnection issue. The issue takes several days to manifest. Can you tell me whether doing a firmware update from DCE will affect the current configuration? Will I need to go back and set everything up again?

(CID:97485983)

[DCIM_Support]

Hi Dominic, As I eluded to previously, it depends on how it is done. If you're doing a TFTP flash, K-base FA176133 notes 2 different ways: I) rootupg (this final upgrade option will wipe out all Bot configuration) II) rootupg keep (this option will upgrade but save any configuration on the Bot) Using the "keep" option will just update or re-flash the firmware. If this issue you're seeing has anything to do with corruption of the existing code, using the "keep" option will retain the issue. This is why I suggested a backup before doing the flash. The backup too may have the issue but restoring the system to defaults with the tftp flash and leaving it to verify it is fixed will show if it was a corruption issue. After that, re-importing the backup should bring it back to it's previous state and running in that configuration for a while will tell you if it was a code issue if it doesn't come back or if it was a configuration corruption issue if it does come back. Steve

(CID:97485984)

[DCIM_Support]

Steve, My understanding is that doing a firmware update from DCE is not the same as re-flashing the appliance. If that's the case, then will doing an update clear the config? Thanks.

(CID:97485987)

[DCIM_Support]

Dominic, No, Doing a firmware update, through DCE or through the Advanced View interface, will simply update your firmware. It will not delete any settings. It will also not correct corruption in the config should that be the cause of the issue. Corruption is usually why we recommend e "re-flash" of the firmware. This is why the rep suggested in the troubleshooting that you use k-base FA176133 and re-flash the firmware. Steve

(CID:97485988)

[DCIM_Support]

Thanks Steve.

(CID:97485993)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.