iSchedule Died!!

TurnipTruck

Greetings,

I have an NI-700-based system on which I am running I schedule.

Yesterday all functionality of iSchedule stopped working, although all other parts of the rather large system are OK. I have tried reloading code, still nothing.

I am relatively sure that iSchedule resides in flash memory. Having only remote access through port 1319, is there any way to remove the file written by iSchedule so that a new one could be built?

Thanks.

DHawthorne

If you FTP into the master, you will find a folder called SCHEDULE, and a file inside called SCHEDULE.bin. Delete it and reboot the master to rebuild it. You may want to check drive space on the master first though, that might be the issue.

TurnipTruck

Thanks Dave. Is there any way to wipe the flash remotely? I do not have FTP access off-site.

Thanks.

DHawthorne

TurnipTruck wrote: »

Thanks Dave. Is there any way to wipe the flash remotely? I do not have FTP access off-site.

Thanks.

I don't know of a way to wipe a single file ... though maybe someone else does and can share; if you have Telnet access you can issue a "clean disk" command that will wipe everything, assuming you have the capacity to reload it all. I'm not sure I would want to go that route myself, it's kind of like using a shotgun to kill a fly. It will probably work, but the collateral damage is a tad high ...

PhreaK

You could use the FILE_DELETE command in netlinx. Set up a virtual device for aux use and some command passing so that you could pass it something along the lines of "'DEL-',sFilename'" using control a device or from a telnet session.

If I get a chance today I might put together a quick module and post it.

TurnipTruck

So I ftp'ed into the master and deleted the schedule.bin file. The system did not rebuild it after a reboot. I then deleted the directory called schedule, still no luck. I reloaded the code and still no go.

I'm thinking that maybe the CF is corrupted???

Any ideas?

DHawthorne

If you reboot the master and Telnet into it as soon as you can, then turn messages on, you should see the chatter i!-Schedule makes as it attempts to create the file. I saw it fail just yesterday that way on a system, claiming there was not enough drive space to create the file. There was tons of drive space, so I have to assume it needs a lot of elbow room. I deleted a few old logs, and it was fine. Even if it's not a space issue, perhaps it will provide a clue.