NEC V651 RS232 AMXB SDK Response

JohnB

I'm trying to establish control of an NEC V651 via RS232 from an NI700. I have the protocol tested and functioning via an emulator and have verified null cable status. I can communicate directly to the unit but when I plug into the NI700 I get the following response when sending a power on or power off command:

AMXB<-SDKClass=Monitor><-Make=NEC><Device-GUID=NEC_LCD><-Model=V651>

Is this some sort of device discovery? I can't seem to get around it or find any information to disable it. Has anyone run into this?

Any help would be greatly appreciated.

ericmedley

Post your send string code and we'll see if we can help

JohnB

Thanks for the reply Eric. Here's what I'm sending:

CHAR CMDHEADER[7] = '0A0A0C'
CHAR GETHEADER[7] = '0A0A06'
CHAR STX = ''
CHAR ETX = ''
CHAR POWERON[10] = 'C203D60001'
CHAR POWEROFF[10] = 'C203D60004'

SEND_STRING dvLCD[1], "CMDHEADER,STX,POWERON,ETX,'I',$0D"
SEND_STRING dvLCD[2], "CMDHEADER,STX,POWERON,ETX,'I',$0D"

SEND_STRING dvLCD[1], "CMDHEADER,STX,POWEROFF,ETX,'L',$0D"
SEND_STRING dvLCD[2], "CMDHEADER,STX,POWEROFF,ETX,'L',$0D"

I've also used the hex equivalent for each as follows. I get the same response from either. Again, only from the NI700. Using a comm emulator from my laptop this works perfectly.

"$01,$30,$41,$30,$41,$30,$43,$02,$43,$32,$30,$33,$44,$36,$30,$30,$30,$31,$03,$73,$0D" - Power On
"$01,$30,$41,$30,$41,$30,$43,$02,$43,$32,$30,$33,$44,$36,$30,$30,$30,$34,$03,$76,$0D" - Power Off

Hope this helps.

JB

jjames

John - yes, that is a Device Discovery string. Just basically telling the master, "Hello - I'm an NEC V651, do you want to interface with me through a Duet module?"

Should be of no concern.

JohnB

Thanks, jjames. I just got off the phone with AMX and they confirmed that as well.

You wouldn't happen to know which module to use for this model, would you? None of the modules shown in their repository reference this model or series. I've downloaded 2 different ones to try out, but it sure would be nicer not to have to experiment. It would be even nicer if I could disable this so I can send direct strings.

Thanks for the help.

jjames

The string coming from the device is cooked into its software, I doubt you'd be able to disable it. It's just a beacon, hence AMXB. You should still be able to interface with it just fine.

What do you mean send direct strings? If you have the emulation working, I'd continue development where you left off rather than doing a complete 180 and interface with a virtual device.

Does the device turn on and off with your commands?

JohnB

No, that's the trouble. The only response I get, when connected to the NI700, is the AMX beacon when sending direct strings, as listed above, and no status change on the LCD. I've also tried alternate command strings such as a Get command for power status with the same result. <grrrr>

jjames

Check the baud rate?

JohnB

Yeah, baud is good. Loading modules now to test.

Andrew G Welker

JohnB wrote: »

Thanks for the reply Eric. Here's what I'm sending:

CHAR CMDHEADER[7] = '0A0A0C'
CHAR GETHEADER[7] = '0A0A06'
CHAR STX = ''
CHAR ETX = ''
CHAR POWERON[10] = 'C203D60001'
CHAR POWEROFF[10] = 'C203D60004'

SEND_STRING dvLCD[1], "CMDHEADER,STX,POWERON,ETX,'I',$0D"
SEND_STRING dvLCD[2], "CMDHEADER,STX,POWERON,ETX,'I',$0D"

SEND_STRING dvLCD[1], "CMDHEADER,STX,POWEROFF,ETX,'L',$0D"
SEND_STRING dvLCD[2], "CMDHEADER,STX,POWEROFF,ETX,'L',$0D"

I've also used the hex equivalent for each as follows. I get the same response from either. Again, only from the NI700. Using a comm emulator from my laptop this works perfectly.

"$01,$30,$41,$30,$41,$30,$43,$02,$43,$32,$30,$33,$44,$36,$30,$30,$30,$31,$03,$73,$0D" - Power On
"$01,$30,$41,$30,$41,$30,$43,$02,$43,$32,$30,$33,$44,$36,$30,$30,$30,$34,$03,$76,$0D" - Power Off

Hope this helps.

JB

For the record, the STX & ETX commands you are sending with the send_string dvLCD[1] line are empty, when they should be $02 & $03 accordingly. Also, I believe your command header variable is missing a $01, which is the start of header byte. You have these correct in the comm emulator, but they are not there in the code you are actually sending out.

JohnB

Yeah, it seems like that because the characters did not copy/paste correctly in the post. What your seeing is the ASCII representation of those hex codes as printed by the forum. In the code they actually appear as SOH for $01, STX for $02 and ETX for $03. I've confirmed them though by sending all hex codes as well, but I get the same result.

If you want to try it out, use the Function number pad on your laptop and press Fn-Alt-001 you'll see the ASCII character for $01. Likewise, if you type Fn-Alt-002 and Fn-Alt-003 for $02 and $03, respectively, you'll see the ASCII characters for STX and ETX. It's a cool little trick to maintain all ASCII codes versus going back and forth between hex and ASCII, at least for simple non-printable codes like these.

jeff.gardiner

Have you tried sending those hex strings directly to the device through the NI-700 using the Control a Device dialog?

I assume your checksum is correct for device address A. Is your display set to the same device address? If you're not daisy-chaining your displays, you could use a wildcard for the address and see if that works. The code for power on that I've tested it below.

"$01,$30,$2A,$30,$41,$30,$43,$02,$43,$32,$30,$33,$44,$36,$30,$30,$30,$31,$03"

JohnB

Thanks for the reply, Jeff. Yeah, I did do that. Ultimately, after further discussion with AMX tech support a device module is the final solution. The Device Discovery function can not be disabled. Fortunately, the first one I grabbed worked right away.

If anyone needs a recommendation for simple power on/off control for this display I can recommend the module for the NEC LCD6520AVT. The only bummer is that it doesn't seem to have a polling command for power status so I'll have to poll for input or something.

Thanks for all the feedback. Hope this helps.

Cheers.