Page 1 of 2 12 LastLast
Results 1 to 15 of 26

Thread: set up to make viewsat work

  1. #1
    Join Date
    Oct 2012
    Posts
    76
    Satfix Buxs
    50,285
    Thanks
    10
    Thanked 3x in 3 Posts

    Default set up to make viewsat work

    Hello all,
    My hard drive recently broke on me, and all my info to make my viewsat to work was on it. I was using teknical's wfemu, but there is no longer a website for the instruction for set up. Essentially I have to start over setting up rqssp etc. Does anyone know what I should do or what are my options or where i should look for info on this? I have already subscribed with an iks server. Please help!!

  2. #2
    Join Date
    Oct 2012
    Posts
    224
    Satfix Buxs
    1,856
    Thanks
    118
    Thanked 140x in 89 Posts

    Red face

    Use this as it easier and simpler to use

    http://www.satfix.net/showthread.php...t-Captiveworks

    Cheers

    Shark1959

  3. #3
    Join Date
    Oct 2012
    Posts
    76
    Satfix Buxs
    50,285
    Thanks
    10
    Thanked 3x in 3 Posts

    Default

    So I looked around and found windows sssp setup for dummies.rar. I am stuck on step 4. I don't know what I need to edit. Any help?

  4. #4
    Join Date
    Oct 2012
    Posts
    224
    Satfix Buxs
    1,856
    Thanks
    118
    Thanked 140x in 89 Posts

    Default

    Do you have the link to dummies so i can read step 4

    Cheers

    Shark1959

  5. #5
    Join Date
    Oct 2012
    Posts
    76
    Satfix Buxs
    50,285
    Thanks
    10
    Thanked 3x in 3 Posts

  6. #6
    Join Date
    Oct 2012
    Posts
    76
    Satfix Buxs
    50,285
    Thanks
    10
    Thanked 3x in 3 Posts

    Default

    I'm still stuck on step 4 but I continued, and rq is saying ;failed to open serial device com1; error failed to initialize properly.... suggestions?

  7. #7
    Join Date
    Oct 2012
    Posts
    224
    Satfix Buxs
    1,856
    Thanks
    118
    Thanked 140x in 89 Posts

    Red face Maybe this will help

    I got this from another site C&P. Hopefully I got it all correct.

    Cheers

    Shark1959

    Default The RQ-SSSP Config file simplified

    The first time you look at the Rq-ssp config file it may be a little intimidating. At first glimpse there appears to be a lot of information and you might be thinking that you don’t know where to begin editing.

    First of all, out of the whole page the Rq sssp client binery only reads 11 lines. All the other information on the page is for reference and general info. Any Line that does not have # at the beginning is read by the application.

    So out of this whole page....

    ################################################## ######################
    # rq-sssp-client configuration file #
    # All configuration options in this file observe the same format: #
    # <configuration_name>=<configuration_value> #
    ################################################## ######################

    ############################General Configuration###############################
    # Serial port where the client receiver is connected.
    # Examples:
    # Linux PC: /dev/ttyS0, /dev/ttyS1, ... /dev/ttyS<n>
    # Dreambox/TD/DGS: /dev/tts/0, /dev/tts/1, ... /dev/tts/<n>
    # Windows: COM1, COM2, ... COM<n>
    serial_port=/dev/ttyS0

    # Serial port communication settings.
    # Example: 115200|8|N|1 = 115200bps, 8 data bis, no parity, 1 stop bit.
    serial_port_settings=115200|8|N|1

    # Sets the byte write delay. The default value of this parameter is 200us
    # which should work for most receivers. You can tweak this value in case
    # you're having communication problems. Sensible values for this parameter
    # go from 0 to 500 (microseconds).
    #
    # NOTE: This parameter *has no effect* in the Dreambox versions (PPC and MIPS).
    byte_write_delay=200

    # SSSP protocol variant
    # 0 - Captiveworks SSSP Protocol (Captiveworks receivers)
    # 1 - Coolsat SSSP Protocol (Coolsat, Viewsat receivers)
    # 2 - Gbox SSSP Protocol (Digiwave, Technomate and many other EU receivers)
    receiver_protocol=1

    # CaID mappings. This is used to solve CaID mismatch errors when a
    # receiver reports the wrong CaID (this can happen when the provider uses
    # multiple CaIDs). If you're sure the card server you're using supports the
    # provider, you can override the CaID mismatch check this way.
    #
    # Format:
    # caid_mappings=<original_caid>:<mapped_caid>|<origi nal_caid>:<mapped_caid>| ...
    #
    # Example: Your receiver may report CaID 1802, the card server
    # reports CaID 1816. Add this mapping:
    #
    # caid_mappings=1802:1816
    #
    # You can also add several mappings like this:
    #
    # caid_mappings=1802:1816|1803:1816| ...
    caid_mappings=

    # If enabled either the even or odd control word is returned for each
    # ECM. The single control word is duplicated. This is intended as a fix
    # for freezing on some receivers when using NDS providers.
    # 0 - Disabled
    # 1 - Return Even on 0x80 ECM table id, Odd on 0x81 ECM table id
    # 2 - Return Odd on 0x80 ECM table id, Even on 0x81 ECM table id
    # 3 - Always return Even
    # 4 - Always return Odd
    return_single_cw=0

    # Enable or disable background execution
    # 0 - Disable
    # 1 - Enable
    #
    # NOTE: Ignored in the WIN32 version.
    background_execution=1

    # This sets the level of console output for debugging:
    # 0 - Silent, 1 - Basic debug info, 2 - Extended debug info,
    # 3 - Show all debug info
    debug_level=1

    # This option enables or disables the writing of debug information to the
    # console.
    log_to_console=1

    # This option enables or disables the writing of console output to a log file
    log_to_file=0

    # When log_to_file is set to 1, this is the path and filename to write console
    # ouput to.
    #
    # NOTE: In the WIN32 version, if enabled, this should be set to a valid
    # Windows/DOS path.
    logfile_name=/var/bin/rq-sssp-client.log

    # URL of card-server to use, formats are as follows:
    #
    # newcamd://<username>:<password>@<hostname>:<port>/<des_key>/[EMM]
    #
    # Example:
    # newcamd://foo:[email protected]:12345/0CE3476FF2E1C9D9A0A109B371E3/EMM
    #
    # NOTE: The "EMM" suffix is optional and tells rq-sssp-client whether
    # to send EMM's to the card-server or not. Enabling or disabling this only
    # has effect if the card-server is configured to accept emms from this client.
    #
    # Multiple card-server url's can be specified for server fail-over.
    # If the client fails to connect or fails to get valid CW's, it will try to
    # connect to other servers in a round-robin fashion.
    #
    # Up to 65 servers can be added from index 0 to 63, plus a non-indexed parameter
    # named "card_server_url"
    card_server_url=newcamd://dummy:[email protected]:11000/0102030405060708091011121314/EMM
    #card_server_url_0=newcamd://dummy_2:[email protected]:10000/0102030405060708091011121314/EMM
    #card_server_url_1=newcamd://dummy_3:[email protected]:10000/0102030405060708091011121314/EMM

    The only thing that is relevant to the application are these lines:

    serial_port=/dev/ttyS0
    serial_port_settings=115200|8|N|1
    byte_write_delay=200
    receiver_protocol=0
    caid_mappings=
    return_single_cw=0
    background_execution=1
    debug_level=1
    log_to_console=1
    log_to_file=0
    logfile_name=/var/bin/rq-sssp-client.log
    card_server_url=newcamd://dummy:[email protected]:11000/0102030405060708091011121314/EMM

    To further simplify this page you will notice that I have painted three lines green and the rest red. The three green lines lines are the only ones you really need to edit for most setups. The red lines are necessary for the application to run, but the default settings are fine.

    The first line is your serial port. You will have to know which serial port your computer is using and set this line accordingly. If you are using a windows OS you will need to use serial port: com 1 or com 2 etc…..
    If your’re using a Linux OS you will need to use serial_port=/dev/ttyS0. ttyS0 is the equivalent of com1 and ttyS1 would be equal to com2 etc.

    The second line you may need to edit will be your receiver protocol. Most units use the default protocol 0 which is Captive works. If you are using the wfemu , cnxemu or a captive works receiver you just have to make sure the line reads receiver_protocol=0 If you are using Coolsat you would use receiver_protocol=1 or if you had Gbox you would use receiver_protocol=3.

    The last line to be concerned with is the server setting line. The information must be put in the proper order in order for the application to run properly. You can input 65 different server settings at a time if you wanted to.
    The default line will look like this.

    card_server_url=newcamd://dummy:[email protected]:11000/0102030405060708091011121314/EMM

    The order you should input your information should be:
    card_server_url=newcamd://username:Password@domain name or server IP:Port number/des key/and you can just delete the EMM from the end.

    card_server_url_0 =newcamd://username: password@domain name or server IP:Port number/des key/

    card_server_url_1=newcamd://username: password@domain name or server IP:Port number/des key/

    Please note the numbering of each card server in red.
    If you have a server with two ports, you can just copy the original line and change the port of the second line
    If you want to change the priorities of the servers you have listed, can just change the numbering of each server
    To turn a server off just add a number sign # to the beginging of the line
    Last edited by Shark1959; 09-15-2014 at 09:10 PM.

  8. The Following User Says Thank You to Shark1959 For This Useful Post:


  9. #8
    Join Date
    Oct 2012
    Posts
    76
    Satfix Buxs
    50,285
    Thanks
    10
    Thanked 3x in 3 Posts

    Default

    I just bought a windows 8 computer since my laptop with xp stopped working. I don't know if that matters. Anyway, in device manager i see com0com. How do I create com 1? I don't know how to set this line accordingly. Does viewsat use default protocol 0?

  10. #9
    Join Date
    Oct 2012
    Posts
    224
    Satfix Buxs
    1,856
    Thanks
    118
    Thanked 140x in 89 Posts

    Red face More info

    Quote Originally Posted by viewertrex View Post
    I just bought a windows 8 computer since my laptop with xp stopped working. I don't know if that matters. Anyway, in device manager i see com0com. How do I create com 1? I don't know how to set this line accordingly. Does viewsat use default protocol 0?
    It should be fine with window 8. With the windows version I listed of sssp, com0com is NOT required. The VS protpcol your asking about should be set to 1.

    I don't believe you have a serial port connection with the newer PC so you'll need a USB to serial adapter to connect your NULL modem crossover cable to the VS receiver.

    You might find this thread useful, where I helped someone with a VS2000, I have two Ultra's and they both work fine http://www.satfix.net/showthread.php...h-Viewsat-2000 Its rather lengthy but good info. A lot of people get mixed up with the different versions of sssp. The one I refer to in my first post is the best one for Windows IMHO, XX-Client Release v2.4.180.926 Windows Zip, again you'll find the download at the bottom of the page, in the link I referred to.

    Cheers

    Shark1959
    Last edited by Shark1959; 02-12-2014 at 03:58 PM. Reason: More info

  11. #10
    Join Date
    Oct 2012
    Posts
    76
    Satfix Buxs
    50,285
    Thanks
    10
    Thanked 3x in 3 Posts

    Default

    I have the usb serial adapter connected to my null modem like before. I changed a com3 port to com1, but rq still says it failed to open serial device com1; Where do I put this information for viewsat ultra (receiver_protocol=3, serial_speed=115200)?

  12. #11
    Join Date
    Oct 2012
    Posts
    224
    Satfix Buxs
    1,856
    Thanks
    118
    Thanked 140x in 89 Posts

    Default

    Quote Originally Posted by viewertrex View Post
    I have the usb serial adapter connected to my null modem like before. I changed a com3 port to com1, but rq still says it failed to open serial device com1; Where do I put this information for viewsat ultra (receiver_protocol=3, serial_speed=115200)?
    Are you using the RQ-SSSP I mentioned in my first post to you?

    If so you open the CONFIG file with NOTEPAD and you will then see what you are asking.

    Cheers

    Shark1959

  13. #12
    Join Date
    Oct 2012
    Posts
    76
    Satfix Buxs
    50,285
    Thanks
    10
    Thanked 3x in 3 Posts

    Default

    When I connect my usb serial adapter, it shows com4 so I entered serial_port=com4. When I go to device manager to check device status, it says device cannot start (code 10)
    {not enough quota}
    Not enough virtual memory or paging file quota is available to complete the specified operation.
    I updated the driver, but it says it is fine how it is.
    How do I resolve this?


    I really appreciate help from you guys at this site!!
    Last edited by viewertrex; 02-13-2014 at 12:51 AM.

  14. #13
    Join Date
    Oct 2012
    Posts
    224
    Satfix Buxs
    1,856
    Thanks
    118
    Thanked 140x in 89 Posts

    Default

    Can you please answer my question in post 11 instead of asking another question. One step at a time Thanks

    Cheers

    Shark1959

  15. #14
    Join Date
    Oct 2012
    Posts
    76
    Satfix Buxs
    50,285
    Thanks
    10
    Thanked 3x in 3 Posts

    Default

    Yes. I guess I am trying and looking at so many different things I get ahead of myself.

  16. #15
    Join Date
    Sep 2012
    Posts
    44
    Satfix Buxs
    431
    Thanks
    7
    Thanked 13x in 10 Posts

    Default

    if your having prbs with the comm port allocation. it is most likely because you have them allocated to com o com as when you configured it you assigned the comm ports 1, 2, 3, 4, 5, 6 or some combination of them. as Shark1959 stated, com o com is not needed if u use the rqssp file in the link he gave you. Turn off com-o-com or remove it and set your usb to serial to reflect com 4 in device manager as the usb to serial uses a different port than comm 1. give it a try.

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •