Loading ...
Sorry, an error occurred while loading the content.

1812JST-135 doesn't works with Omnirig. Need help !!!

Expand Messages
  • Mario
    Mar 4, 2010
    • 0 Attachment
      Hello all,

      I would like to support a JST-135 TRX with Omnirig. And with this project I have a probleme. Commands from the PC to the TRX are working. Changing the frequency or the modes ar no probleme and they are taking the right effect on the TRX, but the JST-135 doesn't response, he doesn't send correct data to the PC. I don't find a way to clear up the probleme. Did anybody have an idea? Can anybody help?

      I put the ini-file and a part of the Omnirig-logging-file in this mail to make it clearer.

      For your help,

      mny tnx es vy 73 de Mario, DB7MA



      Here comes the JST-135 ini-File. The source was the NRD-535DG ini-file included in Omnirig.

      ;-------------------------------------------------------------------------------
      ; initialize
      ;-------------------------------------------------------------------------------
      [INIT1]
      ;H1<cr>
      Command=48310D
      ReplyLength=0

      [INIT2]
      ;I1<cr>
      Command=49310D
      ReplyEnd=0D

      [INIT3]
      ;H0<cr> (this command turns off the "Lock"-Modus)
      Command=48300D
      ReplyLength=0
      ReplyEnd=0D

      ;-------------------------------------------------------------------------------
      ; set frequency
      ;-------------------------------------------------------------------------------

      [pmFreq]
      ;F........<cr>
      Command=47.00.00.00.00.00.00.00.0D
      ReplyEnd=0D
      Value=1|8|vfText|1|0

      [pmFreqA]
      ;F........<cr>
      Command=47.00.00.00.00.00.00.00.0D
      ReplyEnd=0D
      Value=1|8|vfText|1|0

      [pmFreqB]
      ;F........<cr>
      Command=47.00.00.00.00.00.00.00.0D
      ReplyEnd=0D
      Value=1|8|vfText|1|0


      ;-------------------------------------------------------------------------------
      ; set mode
      ;-------------------------------------------------------------------------------

      [pmDIG_U]
      ; D0<CR>
      Command=44.30.0D
      ReplyEnd=0D

      [pmCW_U]
      ; D1<CR>
      Command=44.31.0D
      ReplyEnd=0D

      [pmSSB_U]
      ; D2<CR>
      Command=44.32.0D
      ReplyEnd=0D

      [pmSSB_L]
      ; D3<CR>
      Command=44.33.0D
      ReplyEnd=0D

      [pmAM]
      ; D4<CR>
      Command=44.34.0D
      ReplyEnd=0D

      [pmFM]
      ; D5<CR>
      Command=44.35.0D
      ReplyEnd=0D

      [pmDIG_L]
      ; D0<CR>
      Command=44.36.0D
      ReplyEnd=0D

      ;-------------------------------------------------------------------------------
      ; read status
      ;-------------------------------------------------------------------------------
      [STATUS1]
      ; I1<cr>
      Command=49310D
      ReplyLength=14
      ReplyEnd=0D
      Validate=49.00.00.00.00.00.00.00.00.00.00.00.00.0D

      Value1=4|8|vfText|1|0|pmFreq
      Value2=4|8|vfText|1|0|pmFreqA
      Value3=4|8|vfText|1|0|pmFreqB

      Flag1=(...0..........)|pmDIG_U
      Flag2=(...1..........)|pmCW_U
      Flag3=(...2..........)|pmSSB_U
      Flag4=(...3..........)|pmSSB_L
      Flag5=(...4..........)|pmAM
      Flag6=(...5..........)|pmFM
      Flag7=(...6..........)|pmDIG_L



      Here comes a part of OmniRig's log-file:

      20:46:02.630 RIG 1 settings: Rig=JST-135|Port=COM1|Baud=1200|Data=8|Parity=None|Stop=1|RTS=High|Dtr=High|Poll=500|Timeout=100
      20:46:02.640 RIG 2 settings: Rig=NONE|Port=COM1|Baud=9600|Data=8|Parity=None|Stop=1|RTS=High|Dtr=High|Poll=500|Timeout=4000
      20:46:02.640 Starting RIG1
      20:46:02.660 RIG1 sending init command: 48310D
      20:46:02.660 RIG1 data sent
      20:46:02.660 RIG1 sending init command: 49310D
      20:46:02.670 RIG1 Status commands already in queue
      20:46:02.680 RIG1 data sent
      20:46:02.790 RIG1 {!}recv timeout. Rx Buffer: ""
      20:46:02.790 RIG1 sending init command: 48300D
      20:46:02.790 RIG1 data sent
      20:46:02.790 RIG1 data sent
      20:46:03.011 RIG1 {!}recv timeout. Rx Buffer: ""
      20:46:03.011 RIG1 sending status command: 49310D
      20:46:03.011 RIG1 data sent
      20:46:03.011 RIG1 data sent
      20:46:03.131 RIG1 reply received: 42310D44320D4730
      20:46:03.131 {!}RIG1 reply validation failed
      20:46:03.201 RIG1 Adding status commands to queue
      20:46:03.201 RIG1 sending status command: 49310D
      20:46:03.201 RIG1 data sent
      20:46:03.201 RIG1 data sent
      20:46:03.201 RIG1 reply received: 0D41300D43303033
      20:46:03.201 {!}RIG1 reply validation failed
      20:46:03.291 {!}RIG1 unexpected data received: 0D46303134313130
      20:46:03.361 {!}RIG1 unexpected data received: 30300D42310D4432
      20:46:03.431 {!}RIG1 unexpected data received: 0D47300D41300D43
      20:46:03.511 {!}RIG1 unexpected data received: 3030330D46303134
      20:46:03.591 {!}RIG1 unexpected data received: 31313030300D
      20:46:03.792 RIG1 Adding status commands to queue
      20:46:03.792 RIG1 sending status command: 49310D
      20:46:03.792 RIG1 data sent
      20:46:03.792 RIG1 data sent
      20:46:03.912 RIG1 reply received: 42310D44320D4730
      20:46:03.912 {!}RIG1 reply validation failed
      20:46:03.982 {!}RIG1 unexpected data received: 0D41300D43303033
      20:46:04.062 {!}RIG1 unexpected data received: 0D46303134313130
      20:46:04.112 {!}RIG1 unexpected data received: 30300D
      20:46:04.292 RIG1 Adding status commands to queue
      20:46:04.292 RIG1 sending status command: 49310D
      20:46:04.292 RIG1 data sent
      20:46:04.292 RIG1 data sent
    • Show all 16 messages in this topic