Home› AMX User Forum› AMX Technical Discussion

NI-3000 and mvp 8400

RoalgoRoalgo Posts: 3
in AMX Technical Discussion
Hey im trying to get my MVP 8400 to work on my NI - 3000, im able to get the MVP to send the signal to the NI but im unable to open any IR or RS232 ports, when i use the emulator to emulate the signal and i specify the port it works, im using Netlinx by the way any ideas what could be the problem?

Thanks

Comments

  • Jimweir192Jimweir192 Posts: 502
    Sounds like you've not got the device ID on the MVP set correctly.

    What Device ID are you using in Emulate a Device and what device is actually showing in the online tree?
  • RoalgoRoalgo Posts: 3
    Jimweir192 wrote: »
    Sounds like you've not got the device ID on the MVP set correctly.

    What Device ID are you using in Emulate a Device and what device is actually showing in the online tree?

    Here you go if you need any other info let me know, onething tho you see dvRS232_1 = 5001:1:0 i did change all 0 to 1 and try it like that too and still the same problem
    Amx.jpg 241.7K
  • CT-DallasCT-Dallas Posts: 157
    from your online tree, your NI is not device 5001 - it is 32002. Additionally your Touch Panel number should probably be something similar to device 10001 and not 32001, but I do not see that in your code definitions.

    you can probably find it in the forums, but there are suggested device numbering standards. Devices in the 30,000 range tend to be netlinx virtual devices. 41xxx tends to be a duet virtual device.
  • ericmedleyericmedley Posts: 4,177
    According to what I can see you're program is expecting to see the NIs ports at address 5001:xx:0 However, you're NI is address in the virtual channel range. (32002)

    I also notice the MVP-8400 is up there too. (31001) The default for MVPs it typically 10001.

    So, I'd readdress both the NIs ports and the MVP8400.
  • ericmedleyericmedley Posts: 4,177
    CT-Dallas wrote: »
    from your online tree, your NI is not device 5001 - it is 32002. Additionally your Touch Panel number should probably be something similar to device 10001 and not 32001, but I do not see that in your code definitions.

    you can probably find it in the forums, but there are suggested device numbering standards. Devices in the 30,000 range tend to be netlinx virtual devices. 41xxx tends to be a duet virtual device.

    Sorry, you beat my post by 2 mintues. (sigh)
  • Jimweir192Jimweir192 Posts: 502
    This occurs because panels are now shipped with a default address of 0 - meaning a Dynamic Address is assigned by the master.

    Why the Master has been changed from the default 5001 to 32002 is a strange one - this should be changed back to 5001.

    For reference, the 0 in 5001:1:0 means "this system", if your system number is 1 then 5001:1:1 and 5001:1:0 are the same thing. Look up Device:Port:System in the documentation as this is a key concept in all Netlinx operations.
  • DHawthorneDHawthorne Posts: 4,584
    Jimweir192 wrote: »
    Why the Master has been changed from the default 5001 to 32002 is a strange one - this should be changed back to 5001.

    Not to be too picky, but 5001 would be the controller, not the master. There is a difference. But in answer to that, I have seen them lose their addresses before under odd conditions, so I always check now if they appear in the dynamic range.
  • Jimweir192Jimweir192 Posts: 502
    DHawthorne wrote: »
    Not to be too picky, but 5001 would be the controller, not the master. There is a difference.

    Very true - and very different - my error for typing without thinking...
  • ericmedleyericmedley Posts: 4,177
    Jimweir192 wrote: »
    Very true - and very different - my error for typing without thinking...
    You can think while you're typing? I wish I could do that! :D
Sign In or Register to comment.