Upgrading Axcent 3 to Ni-3000
Kouya
Junior Member
in AMX Hardware
This is my first upgrading of an Axcent 3 to NI-3000. Looking at the program I see that I only need to change the device addresses to the D:P:S standard.
The code complies (Netlinx) without errors.
I figure it's just pulling the Axcent, installing the NI-3000, load the program and everything should be fine.
I know it can't be this easy.....what am I missing? What's the logical approach?
I don't want to bring a knife to a gunfight.
Thanks for any input
brian
The code complies (Netlinx) without errors.
I figure it's just pulling the Axcent, installing the NI-3000, load the program and everything should be fine.
I know it can't be this easy.....what am I missing? What's the logical approach?
I don't want to bring a knife to a gunfight.
Thanks for any input
brian
Comments
-
Actually, it very well could be that easy. It won't be taking advantage of the code features in NetLinx, like timelines, event handlers, and multi-threading (well, pseudo-multi-threading) though. But if ou are looking for a quick controller replacement, it should do.
The only thing I can think of off-hand is if you are using medium waits in your Axcess code. In Axcess, they timed out on their own, in NetLinx, they act like longs. -
If you're using DEFINE_COMBINE, you need to add a virtual device to your DEFINE_DEVICE section and make sure that that virtual device is the first item in the DEFINE_COMBINE statement.
I thought there were a couple other Axcess keyword caveats, but I'm neither remembering them right this instant nor finding them online.
Speaking of online, doing a search on "axcess netlix" on AMX's tech note database turns up a handful of documents, a few of which address things to look for and/or keep in mind when going from one platform to the other.
- Chip -
String constants
One thing that had me stumped for a few days were how string constants are declared. The example is for Hitachi projectors, ON command.
Axcess:
strProjOn = "$BE,$EF,$03,$06,$00,$BA,$D2,$01,$00,$00,$60,$01,$00"
NetLinx:
strProjOn[] = {$BE,$EF,$03,$06,$00,$BA,$D2,$01,$00,$00,$60,$01,$00}
It's just a syntax issue, but it had me thinking that my serial ports / cables were flakey. From what I can recall, the compiler didn't generate an error, leading me to believe that my code was okay.
It is probably documented somewhere, but I was too busy trying to get the swap done to hunt for such differences. I learnt my lesson.
Yours,
Roger McLean. -
PLease check the SET BAUD commands. In AXcent3, the 'SET BAUD' commands are done in DEFINE_START.
In NetLinx, these commands should be done in DATA_EVENTs ONLINE. -
Upgrading Axcent 3 to Ni-3000
Thanks to all for sharing some valuable info
brian
Leave a Comment
Categories
- All Categories
- 2.5K AMX General Discussion
- 922 AMX Technical Discussion
- 514 AMX Hardware
- 502 AMX Control Products
- 3 AMX Video Distribution Products
- 9 AMX Networked AV (SVSI) Products
- AMX Workspace & Collaboration Products
- 3.4K AMX Software
- 151 AMX Resource Management Suite Software
- 386 AMX Design Tools
- 2.4K NetLinx Studio
- 135 Duet/Cafe Duet
- 248 NetLinx Modules & Duet Modules
- 57 AMX RPM Forum
- 228 MODPEDIA - The Public Repository of Modules for Everyone
- 943 AMX Specialty Forums
- 2.6K AMXForums Archive
- 2.6K AMXForums Archive Threads
- 1.5K AMX Hardware
- 432 AMX Applications and Solutions
- 249 Residential Forum
- 182 Tips and Tricks
- 146 AMX Website/Forums