Transfer Aborted - Insufficient memory to complete transfer
I was able to upload files to my controller just fine last week, with 7 rooms connected to it. Today, I connected 6 more SDX's, 7 more touchpanels, and 2 more DX-RX units. When I tried to upload to my controller - exact same code just changed a couple flags for room status - I now get this "Insufficient Memory" problem when trying to transfer. Tomorrow I will disconnect all the other devices again, and try to upload again, but it looks like the RMS modules trying to handle so many devices in one controller is eating up all the controller memory. Reference the "only one thing" discussion point.
So, at this point, the RMS SDK has completely failed me. Time to get going on an Eric Medley I guess. Not what I wanted to have to do. Dang.
So, at this point, the RMS SDK has completely failed me. Time to get going on an Eric Medley I guess. Not what I wanted to have to do. Dang.
0
Comments
Rebooting the controller seems to have no effect on anything.
Disconnecting all extra / new devices and rebooting the controller does not clear the insufficient memory problem. Still only uploads PROG.tkn and fails everything else as insufficient memory.
Um... uploading without the duet files? Sorry this may not be an intelligent question, but my brain is dead meat here; how do I do that? I've actually been kinda perplexed about this issue, I've got 2 systems with nearly identical RMS module and include files. One of them (this one) uploads all the duet stuff; the other one does not. What am I missing in terms of system configuration that allows me to control that?
No worries!
In the File Transfer window... Right-click over the file(s) you're sending to your master and select the "Options" menu item. when there check the "Don't send Duet Files" option. That way it won't needlessly resend all the .jar files and all that. You do have to remember to re-send if you do make any changes to the duet side.
Also, it's only worth doing if you know that the Jar's and Duet files that are compiled are the same as what is already in the system. There is no version check at all when doing this type of transfer.
Working to re-configure the devices to the new controller now.
Thanks,
So, looks like two bad NX-3200's in a row for me. Talk about shattering my faith in the reliability of AMX/Harmon hardware...
To be clear, I didn't call them for help at the time, and I don't think calling them would have sped up resolution in any significant manner. I had more controllers, and throwing controllers at the problems first is a very effective strategy. I can't imagine a tech call wouldn't have eventually ended in trying another controller anyway. If the 3rd controller hadn't worked, I would have called. The way it played out turned out to be, "OK guys I'm up and running again now, but let me tell you what just happened to me..."
But back to the story, AMX/Harman peeps response seems pretty genuine, aggressive, and greatly appreciated from this end of the spectrum.