Home AMX User Forum NetLinx Studio

Lexicon serial problems

Hi guys

I am working with MC-8 ver 2 .
The AMX module is working only with MC-8 ver 1...

The program that came with the module sent properly only few command.

I am trying to work with the serial command with no success..I am sending command like this:

Set Volume - SEND_STRING dvLexMC8, "'$F1,$04,$40,$01,$01,$F2'"

its not working...

I am also trying to understand how to change input and the document is not clear to me. every company has it logic, and this one is so not clear I don't understand what they want...

http://www.lexicon.com/downloads/mc8/MC8SerialDefRev1.pdf


thanks of any help

Ady.

Comments

  • adysadys Posts: 395
    Ok, we found a solution - to use the "Ir Codes" commads via serial commands. nice solution.


    We have a strange problem:

    DATA_EVENT[dvLexMC8]
    {

    ONLINE:
    {
    SEND_COMMAND DATA.DEVICE,'SET BAUD 19200,O,8,1'
    }
    STRING:
    {

    local_var char cLCD_DATA[64];
    cLCD_DATA= DATA.TEXT

    SEND_STRING dvDebug, "'lexicon string'"
    SEND_STRING dvDebug, DATA.TEXT

    } // END OF - string event
    } // END OF - data event



    The device is not sending strings to the data event...

    but If we connecting it with a serial cable to the terminal program - we can see that its sending string on the serial port.

    the code is the same for a lot of other serial devices.

    Any idea how to start solving this?

    thanks

    Ady
  • SEND_STRING dvDebug, "'lexicon string'"
    SEND_STRING dvDebug, DATA.TEXT

    SEND_STRING dvDebug, "DATA.TEXT"

    Did you remember the quotes in your actual code?
  • adysadys Posts: 395
    yes..

    The code don't reach there at all, not even with the a debugger.

    Netlinx studio notifications window also don't work.

    Only when connecting with a cable via terminal its sending some strange characters...

    I can understand that maybe there is some porblems in the code, but why the notifications window don't show the coming strings?
  • adysadys Posts: 395
    Problems Solved

    I changed the line

    SEND_COMMAND dvLexMC8, 'SET BAUD 19200,O,8,1'

    to be

    SEND_COMMAND dvLexMC8, 'SET BAUD 19200,O,8,1 485 Disable'

    and now it working like it should...

    Why is that?

    I messed with it 2 days just to find out this 485 disable .. this is not written anywhere :(
  • adys wrote:
    I changed the line

    SEND_COMMAND dvLexMC8, 'SET BAUD 19200,O,8,1'

    to be

    SEND_COMMAND dvLexMC8, 'SET BAUD 19200,O,8,1 485 Disable'

    and now it working like it should...

    Why is that?

    I messed with it 2 days just to find out this 485 disable .. this is not written anywhere :(

    Should both work, the '485 DISABLE' or *ENABLE*is optional (but must be written uppercase). For RS232 control (pins 2,3,5), it also doesn't matter if 485 mode is enabled or disabled (it's just a different handling of the data sent and received on pins 1,4,6,9). Maybe it's some kind of side effect if a full patched com cable is used and 485 mode was ON.
Sign In or Register to comment.