AB Panelview 600 Memory

My read of the manual indicates that the memory can be substantially expanded with flash memory and the division of memory between application and program is adjustable. I suggest you call AB for some technical assistance on this. It's a possibility the thing is broken or you've simply overlooked a step. You know, one of those steps everyone knows so they forgot to put it in the manual or they hide it in a cautionary note somewhere else or it was added by an addendum to your manual. One of those hair pulling, sleep losing little frustrations that you figure out after wasting alot of time.

Good luck.

A-B's PanelBuilder32 is the program used to create applications for all of the Panelview Classic models. I've probably created several hundred PV applications since they were available and have never seen a use for the memory card other than application storage (PC to PV exchange). It is not required to be installed for the PV to work, however its presence is required if the application you build uses external fonts as thats where the fonts are stored.

Sorry guys, this thing is just not that smart. The memory card does become more useful in the newer generation of Panelviews (the Pluses) but that system runs on a variation of Windows CE; the Classics have a simple bios for starting an application out of RAM or copied from the memory card into RAM and then started.

Now, back to the original problem. Have you taken advantage of global objects? If you are using the same button or indicator on multiple screens you can save memory by making it a global object on the first screen you use it, then referencing it on subsequent screens.

Note: if you change a global object's properties, all screens that use it will also see the change.

Also, with respect to text. Each text string you create is stored with a Text ID (integer). You can see it in the PB32's text editor. If you use the same string in many places, unless you take advantage of referencing the Text ID in a object and just simple type it in, PB32 will create a new test string with a new Text ID. So the text editor can be filled with the same exact text entries but each one has a unique text ID.

I hope these few pointers will help you with your application. I've yet to run out of memory on a Panelview in spite of small rather large applications.

Thanks for the input.

A couple of fellow systems intergrators just left the site after spending an hour or so trying everything under the sun to include calling AB for tech support but were not able to get the ATA flash memory to work as application memory. Not much of a surprise to me but given that I now have to deal with the projects division and have them fork over the funds for a PV 1000 I had to cover all my bases.