Jump to content

ACM/VCM


EnoSat

Recommended Posts

Hi,

planned add support on ACM/VCM transponders ?

 

etc. hex string from NIT pid on ACM/VCM transponder Freq-11185.50 SR-21666 on 28.2 East

00 40 80 29 00 41 3C 00 00 00 09 4A 07 00 41 00 41 02 8B 07 00 11 00 41 00 41 00 0D 43 0B 01 11 85 50 02 82 94 02 16 66 03 45 CF 97 05 FF B7 B8 B9 BA BB BC BD BE BF C0 C1 C2 C3 C4 C5 C6 C7 C8 C9 CA CB CC CD CE CF D0 D1 D2 D3 D4 D5 D6 D7 D8 D9 DA DB DC DD DE DF E0 E1 E2 E3 E4 E5 E6 E7 E8 E9 EA EB EC ED EE EF F0 F1 F2 F3 F4 F5 F6 F7 F8 F9 FA FB FC FD FE FF 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F 20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F 30 31 32 33 34 35 36 37 38 39 3A 3B 3C 3D 3E 3F 40

vs.

hex string from NIT pid on CCM transponder

00 40 F0 33 02 9E C1 00 00 F0 13 40 11 43 45 54 20 54 65 6C 65 70 6F 72 74 20 47 6D 62 48 F0 13 EC 54 02 9E F0 0D 43 0B 01 26 88 10 02 85 81 02 20 00 01 A3 60 B4 64

 

post-20113-0-45141500-1324226522_thumb.png

Edited by EnoSat
  • Like 1
Link to comment

..not quite the right answer ;) It has nothing to do with 16APSK. Information about ACM/VCM can be found in the MATYPE which is located in the base band header (EN 302307).

 

Neither transedit nor any other normal BDA_based application has access to this information!

 

..concerning the NIT, it contains nothing related to the question ;)

 

40 -> table_id: network_information_section - actual_network
8029 -> length 41 -> Bytes
0041 -> network_id
3C -> reserved (2 Bits): 0 -> version_number (5 Bits): 1E -> current_next_indicator (1 Bit): 0
00 -> section_number
00 -> last_section_number
0009 -> network_descriptors_length 9 bytes
4A -> linkage_descriptor
07 -> 7 bytes
0041 -> transport_stream_id
0041 -> original_network_id
028B -> service_id
07 -> linkage_type: RCS Map
0011 -> transport_stream_loop_length 17 bytes
0041 -> transport_stream_id
0041 -> original_network_id
000D -> transport_descriptors_length 13 bytes
43 -> satellite_delivery_system_descriptor
0B -> 11 bytes
01118550 -> frequency: 011,18550 GHz
0282 -> orbital_position: 028,2 degrees
94 -> east -> polarization: linear - horizontal -> modulation: reserved for future use
0216660 -> symbol_rate: 021,6660 Msymbol/s
03 -> FEC: 3/4 conv. code rate

Link to comment

thanks to info , maybe need more detail for:

94 -> east -> polarization: linear - horizontal -> modulation: reserved for future use

 

PS: i known idea for use TransEdit/DvbEdit for Multistream transponders ?

, 12 West
Link to comment
maybe need more detail for:

94 -> east -> polarization: linear - horizontal -> modulation: reserved for future use

doesn't matter and won't be of any help. Said transponder locks without any problem with the TBS6925. In fact it's plain CCM (8PSK, 3/5) though the MATYPE says ACM/VCM. Any other DVB-S2 device should be able to lock as well, but I guess they are hardcoded in the firmware to reject any MATYPE other than defining CCM Broadcasting services with single TS.

 

Talking about multiple input streams (MIS). Again not possible, because the necessary MATYPE is not available. You have to use an additional tool like crazyscan or tbsrecorder to set the corresponding mux first. If you do, transedit or DVBViewer can handle the single TS.

 

Further, DVBViewer and other dvb_tv_applications are restricted to TS and can't handle packetized or continuous streams.

Link to comment
maybe need more detail for:

94 -> east -> polarization: linear - horizontal -> modulation: reserved for future use

again, because Transedit won't show anything which apparently gives room to speculations ;) ,I've looked it up using EN 300468 (before I used an old parsing tool ;) ). The satellite delivery system is partly wrong (it says horizontal polarisation) and vage but there is nothing to worry about. It's just DVB-S2 with auto_modulation :bye:

 

28E_11185V

0x94
10010100

1 -> east
00-> linear-horizontal
10-> a=0,20
1 -> dvb-s2
00-> auto

  • Like 1
Link to comment
  • 2 weeks later...
  • 1 year later...

Hello. I have finally found a forum discussing this new form of broadcast. I am of course currently 8unable to view such content, and wondered if anyone can help me.

 

This is my first post here and I hope it is not in the wrong place. I cannot currently find the welcome page but please forgive me.

 

My question relates to the ACM/VCM broadcasts at 28.2 East

 

My Technomate TM 5402 HD detects, but does not lock onto, the following frequncies, of which we know nothing about and have no idea what is on them. I hope someone can help and tell us the service names of anything found on the following frequencies at 28.2 East.

 

(all DVB-S2)

11.009 V, SR 22500 FEC unknown 16APSK

11.186 V SR 22500 FEC unknown 16APSK (but could be SR 21666 FEC 3/5 16APSK?

 

The above have been on air for a number of years.

 

Since last Friday morning, 4 October, the following muxes have been actived at 28.2 East

 

11.464 H SR 22500 FEC unknown (16APSK?)

11.479 V SR 22500 FEC unknown (16APSK?)

11.508 V SR 22500 FEC unknown (16APSK?)

 

The thrid one of these was off for a while earier in the week, but was back on earlier today.

 

My receiver stores it as SR 45000 but locks it at 22500 going on and off and never finding any channels - so I assume from reading elsewhere this is either VCM, ACM and/or 16APSK.

 

My box can cope with 8PSK as well as QPSK, but not 16APSK.

 

This may be an unusual first post, but I found the thread before registration and thought I would lose it if I had to search around first for a welcome thread.

 

If anyone is able to check all these frequencies mentioned, please can you let me know what you find on them and give their correct paramaters?

 

Thanks very much indeed for your help. It is most appreciated.

Edited by jimbo2013
Link to comment

..your observations are not quite correct. I guess you've obtained the data from the usual transponder sites ;)

 

e.g. 11479V is constantly switching between different modulations. The stream type is continuous which means that DVBViewer or transedit can't read this stream cos it's not a stream of transport packets each starting with sync byte 0x47.

 

You'll need an VCM/ACM capable card (e.g. TBS5925) and a tool like crayzyscan though you even then you won't know the content of these data streams ;)

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...