Request for supporting Ceton devices on Linux

[mvallevand]

Sorry I don't know anything about OpenDCT and I don't understand the comment. I do see that the channel scan was still going on and the registry said 9 not 10 devices. Did you make the properies change the OpenDCT author mentioned? This is the foundation for Ceton and HDHR use in SageTV so I suspect it will work when configured. Support for OpenDCT is here https://forums.sagetv.com/forums/showthread.php?t=62774

Also I again don't see any connect from opendct.bat there.

Martin

[run088]

Maybe you can notice something in the properties file. I installed sage and in gets as far. If opendct is running the tuners show up. But I cant get playback.I attached the file.

And as far as my last comment it was just in regards of something I noticed in the log and copied and pasted in my above post. And it would only affect one card. Its not associating the right ip with the right card.

The card with a static ip of 192.168.2.250 for its web interface answers request on 192.168.2.251. This is the network of the card. these cards dont exactly have virtual Ethernet in the traditional sense. You dont exactly bridge the connection more like merge 2 networks. Your just assigning both networks in the same range so everything can be seen everywhere.

For this reason on the linux side my bridge runs a little unstable. The OS is aware of this and sometimes tries to set the network gateway to the card and not the actual network.. The card itself is running its own little linux OS on top of whatever OS the host PC is running on.

Now with 2 cards I have 3 OS and networks running.

The card with a static ip of 192.168.2.250 for its web interface answers request on 192.168.2.251.
The card with a static ip of 192.168.2.240 for its web interface answers request on 192.168.2.241.
The host PC on windows running 2 nics on my real network in the same subnet

That makes this code a problem because its sending tuner request for this tuner to the other tuners network. I pulled this from the log


InfiniTVCaptureDevice - Encoder Manufacturer: 'Ceton', Number: 2, Remote IP: '192.168.2.250', Local IP: '192.168.2.241', CableCARD: true, Lineup: 'dct_infinitv', Offline Scan Enabled: false, RTP Port: 8426

09:19:02.189 [cling-17] INFO  SageTVManager - The capture device 'DCT-Ceton InfiniTV PCIe (00-80-84-b9) Tuner 2' is ready.

[mvallevand]

You either missed the two steps for attaching or the zip or 7z requriement for uploads. I won't know much about the file but I can compare some things I know.

The bridged network does seem like the problem we might be having but discovery is working (I think) and you can connect to opendct to create the INSTALL xmls files. Even if opendct can't open a Ceton device I would expect an error messge on the start similar to what I see if I send your command line

Code:

12:54:48.607 [SageTVRequestHandler-1383:Unknown] DEBUG SageTVRequestHandler - SageTV sent: 'START DCT-Ceton InfiniTV PCIe (00-80-0d-5a) Tuner 3|7824|2|12345678|stdout|Great'
12:54:48.608 [SageTVRequestHandler-1383:Unknown] DEBUG SageTVManager - The capture device 'DCT-Ceton InfiniTV PCIe (00-80-0d-5a) Tuner 3' is not yet available.
12:54:48.609 [SageTVRequestHandler-1383:Unknown] DEBUG SageTVManager - The requested capture device 'DCT-Ceton InfiniTV PCIe (00-80-0d-5a) Tuner 3' did not exist. Triggering re-discovery.
12:54:48.609 [SageTVRequestHandler-1383:Unknown] ERROR SageTVRequestHandler - SageTV sent: 'START DCT-Ceton InfiniTV PCIe (00-80-0d-5a) Tuner 3|7824|2|12345678|stdout|Great', Replied: 'ERROR Invalid Input'
12:54:48.610 [SageTVRequestHandler-1383:Unknown] ERROR SageTVRequestHandler - Encoder device does not exist.
12:54:48.700 [SageTVRequestHandler-1383:Unknown] DEBUG SageTVRequestHandler - SageTV sent: 'GET_SIZE DCT-Ceton InfiniTV PCIe (00-80-0d-5a) Tuner 3'
12:54:48.700 [SageTVRequestHandler-1383:Unknown] DEBUG SageTVManager - The capture device 'DCT-Ceton InfiniTV PCIe (00-80-0d-5a) Tuner 3' is not yet available.
12:54:48.700 [SageTVRequestHandler-1383:Unknown] DEBUG SageTVManager - The requested capture device 'DCT-Ceton InfiniTV PCIe (00-80-0d-5a) Tuner 3' did not exist. Triggering re-discovery.

That does assume the network is stable you can test opendct connectivity at anytime with

python(3) scripts/opendct.py VERSION

Martin

[sub]

Maybe remove one of those two device for now, while you're trying to get it going, and only add it back in when you get past the first device working.

[mvallevand]

I am not sure the issue is two devices as much as it is the two merged unstable routes. I do agree removing one network and using basic networking would confirm that the extras device is valid and the OP can focus on connectivity.

Martin

[run088]

zip and upload your sh and py files and I will try them here

Maybe run

sha256sum /opt/opendct/lib/opendct-0.5.29.jar

To see which version you have.

Martin

root@livetv:~# sha256sum /opt/opendct/lib/opendct-0.5.29.jar

96d5b55d17f427319e848edccae181329aa7b064d67c711c548ae280de142e2c  /opt/opendct/lib/opendct-0.5.29.jar

[run088]

I had no luck with one card. I noticed I had some java errors on opendct on my windows 10 build and fixed those but still got nowhere.

Switched back over to linux. Here are the latest logs

[mvallevand]

There is no connect from opendct.py showing

Does

python3 opendct.py VERSION

even work?

Mrtin

[run088]

I cant get the v5 to work with the ceton setup on either windows 7, windows 10, or ubuntu 18.0.4

I did get the setup to work in v4 on windows 7. it wouldnt work in 10 for me so far and there is no option in v4 for linux.

It is a little buggy on 7 but could be the way it is configured. It loads kinda slow and always shows a black screen but you can see the file load and buffer and it says play. If I go into setting and i dont have to change anything but push apply it starts to display the picture and play normally.

I ran into this post which made me try v4

https://forums.nextpvr.com/showthread.php?tid=60283


If I can get the bugs worked out on 7 I have no problem staying there as long as I have to.

[sub]

I ran into this post which made me try v4

Yeah, there was built in support for Ceton devices in v4. Unfortunately I probably wont add Ceton support in v5 because:
- I have no environment I can use for testing Ceton stuff any more,
- these devices were always a pain to work with
- these devices haven't been sold for a few years,
- there isn't many people still using them. (so hard to justify the massive effort to support them directly)