Altx's Pages

This is an application used to remotely access a DVB device over TCP/IP. To install it extract the archive content into your AltDVB’s directory. The server is using one of the available interface libraries from .\Devices\ directory to access the DVB hardware. On network side, two TCP ports are used: one for commands (37000) and one for data (37001). You can change it by editing AltDVB_DevServer.cfg.

Warning: Be sure to stop the server if you want to use the same device directly in AltDVB !

To connect AltDVB to a remote server you have to manually edit Dev_Network.cfg. Please note that there is no autoreconnect feature: if the TCP/IP connection to the server is lost you have to restart the AltDVB.

AltDVB_DevServer_v2.3.0.340.zip (336.2 KiB)

MD5: a3fd76312984ad8eeaffafa7117ab0f1

Here are some interface libraries to a non-BDA DVB devices. Use them only if the BDA version of the driver for that device is not available. Please note that I cannot test them from various reasons: missing PCI interface from new motherboard or I don’t own the device anymore.

• Dev_DvbWorld.int – v2.3.0.198
  – access the hardware using vendor’s DwUsbApi.dll which must be present in AltDVB directory
• Dev_Pinnacle.int – v2.3.0.200
  – for older Pinnacle PCTV Sat/ PCTV 400i / etc.
• Dev_SkyStar2.int – v2.3.0.770
  – fixed DiSEqC command when using driver >= 4.4.0
  – config dialog built without VCL
• Dev_TTBudget.int – v2.3.0.294
  – need WDM drv. 2.19h (28.11.2006)
  – you have to copy “ttlcdacc.dll” (ver. >= 2.19.8.1) into ..\AltDvb\Devices\
  – tested with S2-3200

AltDVB_v2.3_NonBDA_Interfaces.zip (174.4 KiB)

MD5: bc61afd24cd67c53ebf00a472c6455f4

Comments in the forum

Changelog:

• added DiSEqC, PLS & MIS support for TBS PCI-E devices
• fixed DiSEqC for TBS USB devices

I think there is a driver issue with some TBS devices. After sending a DiSEqC command, the 22KHz tone is automaticaly set to ON causing the LNB to switch into HI band and loosing then transponder signal, if previously was in LO band. Of course, this only happens if the DiSEqC command is sent after the tuner is locked on the transponder, and is not noticeable if the DiSEqC commands are sent before setting the tuner.

I have tested on TBS-5520SE (USB) with driver v1.0.0.7 and TBS-6522 (PCI-E) with driver v1.0.1.2.
(many thanks to Mr. satelescu/satesco for borrowing the TBS-6522 device)

The setting TbsFix22KHz=1 from Dev_BdaDriver.cfg fixes the issue by sending TBSACCESS_22K with TBSBURST_OFF after the DiSEqC command, if the current TP is on LO band.

I already notified Mr.Steven from TBS Technology and he will verify the issue.

Dev_BdaDriver_v2.3.0.435.zip (48.4 KiB)

MD5: cc47783221de15f90157720330a11ea6

Comments and feedbacks in the forum.