Hello,
I always thought the UDP address 230.0.0.230 is broadcast? When I try to access it with a second viewer, the playback in the first viewer stops. I can only access 230.0.0.230 with one viewer at the same time. I tried the different settings # anywhere, anyhub, and multihub. Stil the same result. Any idea ?
73 de Robert, DD4YR
Winterhill UDP broadcast
Re: Winterhill UDP broadcast
It should work in the way that you expect. Set BOOT = multihub in winterhill.ini to make it start in that mode.
Some routers do not work correctly with multicast. Sometimes multicast will not work over WiFi.
Are you opening the 2 viewers on the same PC? It should not make any difference.
Does the 4 line status display show the TS Destination as 230.0.0.230?
Brian
Some routers do not work correctly with multicast. Sometimes multicast will not work over WiFi.
Are you opening the 2 viewers on the same PC? It should not make any difference.
Does the 4 line status display show the TS Destination as 230.0.0.230?
Brian
Re: Winterhill UDP broadcast
Hello Brian, tnx for fast reply!
I´ve set BOOT = multihub in winterhill.ini
There is no router between Winterhill Raspi and the PC. Only a switch.
I´m openening the 2 viewers on the same PC.
One viewer is whpcviewer-3v20d2, the other VLC input of OBS.
VLC is adressed to 230.0.0.230:9941
The 4 lines in whpcviewer are showing the IP Adress from my PC ?!?
Viewing still only visible on one of these viewers.
I can switch back and forth, only one shows live the stream.
73 de Robert, DD4YR
I´ve set BOOT = multihub in winterhill.ini
There is no router between Winterhill Raspi and the PC. Only a switch.
I´m openening the 2 viewers on the same PC.
One viewer is whpcviewer-3v20d2, the other VLC input of OBS.
VLC is adressed to 230.0.0.230:9941
The 4 lines in whpcviewer are showing the IP Adress from my PC ?!?
Viewing still only visible on one of these viewers.
I can switch back and forth, only one shows live the stream.
73 de Robert, DD4YR
Re: Winterhill UDP broadcast
>>The 4 lines in whpcviewer are showing the IP Adress from my PC ?!?
If the TS Destination in the 4 line display is showing 192.168.xxx.xxx, but not 230.0.0.230, then WH is not in multicast mode. Can you post a screenshot please.
Also, the whpcviewer .bat file should be something like:
whpcviewer-3v20d2 230.0.0.230 9900 192.168.77.247 0 0 576 360 0 -240 1152 220
The 192.168 interface address is needed only if you have more than one network interface on your PC, otherwise it is 0.
Check the file ~/winterhill/whlog.txt and see if WH is starting with the correct IP address. This is from one of my test versions, but the command format is the same.
2023-05-02 11:06:10 <<<<<<<<<< Program started: winterhill-wxm330s ./wxm330s 0 9904 0 0 0 0 0
2023-05-02 11:06:13 +++ NIM_A FTS4334L initialised +++
2023-05-02 11:06:14 +++ NIM_B FTS4335 initialised +++
Brian
If the TS Destination in the 4 line display is showing 192.168.xxx.xxx, but not 230.0.0.230, then WH is not in multicast mode. Can you post a screenshot please.
Also, the whpcviewer .bat file should be something like:
whpcviewer-3v20d2 230.0.0.230 9900 192.168.77.247 0 0 576 360 0 -240 1152 220
The 192.168 interface address is needed only if you have more than one network interface on your PC, otherwise it is 0.
Check the file ~/winterhill/whlog.txt and see if WH is starting with the correct IP address. This is from one of my test versions, but the command format is the same.
2023-05-02 11:06:10 <<<<<<<<<< Program started: winterhill-wxm330s ./wxm330s 0 9904 0 0 0 0 0
2023-05-02 11:06:13 +++ NIM_A FTS4334L initialised +++
2023-05-02 11:06:14 +++ NIM_B FTS4335 initialised +++
Brian
Re: Winterhill UDP broadcast
Ok,
the 4-line looks like:
RX STATUS CALLSIGN MER D FREQUENCY SR MODULATION FPRO CODE ANT PACKETS %NUL NIMTYPE TS DESTINATION
----------------------------------------------------------------------------------------------------------------------------------------
1 DVB-S2 A71A 12.0 7.3 10491.500 1500 QPSK 4/5 LN20 H264-MPA TOP 441572 3.3 FTS4334L 192.168.20.109
2 DVB-S2 F5AJJ 8.2 7.2 10498.244 333 QPSK 1/2 LN25 H265-AAC TOP 44444 4.1 FTS4334L 192.168.20.109
3 lost "M0PIT" 10495.259 250 QPSK 3/4 LN35 -AAC BOT 52826 10.8 FTS4334L 192.168.20.109
4 lost F1FHK 10494.229 250 QPSK 3/5 SY35 H264-AAC BOT 9045 14.6 FTS4334L 192.168.20.109
192.168.20.109 is the IP of my PC
WHPC viewer bat script is
rem IPADDRESS BASE IPINTERFACE VLC1 VLC1 VLC VLC INFO INFO INFO INFO
rem Zero or PORT Usually LEFT TOP WIDTH HEIGHT LEFT TOP WIDTH HEIGHT
rem broadcast zero
whpcviewer-3v20d2 230.0.0.230 9900 0 0 0 476 300 0 0 952 130
whlog.txt
2023-08-05 11:38:15 <<<<<<<<<< Program started: winterhill-3v20a ./winterhill-3v20 0 9900 0 25165830 31457286 27262982 29360134 ^M
2023-08-05 11:38:16 +++ NIM_A FTS4334L initialised +++ ^M
2023-08-05 11:38:16 +++ NIM_B FTS4334L initialised +++ ^M
2023-08-05 11:38:16 PIC_A version is 3v20 ^M
2023-08-05 11:38:16 PIC_B version is 3v20 ^M
Robert
the 4-line looks like:
RX STATUS CALLSIGN MER D FREQUENCY SR MODULATION FPRO CODE ANT PACKETS %NUL NIMTYPE TS DESTINATION
----------------------------------------------------------------------------------------------------------------------------------------
1 DVB-S2 A71A 12.0 7.3 10491.500 1500 QPSK 4/5 LN20 H264-MPA TOP 441572 3.3 FTS4334L 192.168.20.109
2 DVB-S2 F5AJJ 8.2 7.2 10498.244 333 QPSK 1/2 LN25 H265-AAC TOP 44444 4.1 FTS4334L 192.168.20.109
3 lost "M0PIT" 10495.259 250 QPSK 3/4 LN35 -AAC BOT 52826 10.8 FTS4334L 192.168.20.109
4 lost F1FHK 10494.229 250 QPSK 3/5 SY35 H264-AAC BOT 9045 14.6 FTS4334L 192.168.20.109
192.168.20.109 is the IP of my PC
WHPC viewer bat script is
rem IPADDRESS BASE IPINTERFACE VLC1 VLC1 VLC VLC INFO INFO INFO INFO
rem Zero or PORT Usually LEFT TOP WIDTH HEIGHT LEFT TOP WIDTH HEIGHT
rem broadcast zero
whpcviewer-3v20d2 230.0.0.230 9900 0 0 0 476 300 0 0 952 130
whlog.txt
2023-08-05 11:38:15 <<<<<<<<<< Program started: winterhill-3v20a ./winterhill-3v20 0 9900 0 25165830 31457286 27262982 29360134 ^M
2023-08-05 11:38:16 +++ NIM_A FTS4334L initialised +++ ^M
2023-08-05 11:38:16 +++ NIM_B FTS4334L initialised +++ ^M
2023-08-05 11:38:16 PIC_A version is 3v20 ^M
2023-08-05 11:38:16 PIC_B version is 3v20 ^M
Robert
Re: Winterhill UDP broadcast
>> 1 DVB-S2 A71A 12.0 7.3 10491.500 1500 QPSK 4/5 LN20 H264-MPA TOP 441572 3.3 FTS4334L 192.168.20.109
>>2023-08-05 11:38:15 <<<<<<<<<< Program started: winterhill-3v20a ./winterhill-3v20 0 9900 0 25165830 31457286 27262982 29360134
These 2 lines show that WH is not in multihub mode.
Can you check the format of the BOOT line in winterhill.ini again. Have you changed the multihub launch file?
Do you have monitor and keyboard on the RPi? There should be no VLC windows on the RPi monitor in multihub mode.
Try stopping WH manually with the screen icon and start multihub mode manually with the screen icon.
Brian
>>2023-08-05 11:38:15 <<<<<<<<<< Program started: winterhill-3v20a ./winterhill-3v20 0 9900 0 25165830 31457286 27262982 29360134
These 2 lines show that WH is not in multihub mode.
Can you check the format of the BOOT line in winterhill.ini again. Have you changed the multihub launch file?
Do you have monitor and keyboard on the RPi? There should be no VLC windows on the RPi monitor in multihub mode.
Try stopping WH manually with the screen icon and start multihub mode manually with the screen icon.
Brian
Re: Winterhill UDP broadcast
the boot line looks ok.
on the Raspberry are no vlc windows.
the 4-line command window shows, the TS target is the IP of my PC
After manually stop and restart the TS target is 127.0.0.1, after click in Quick-Tune the TS target IP changes to my PC´s IP
I didn´t change the multihub launch file -
on the Raspberry are no vlc windows.
the 4-line command window shows, the TS target is the IP of my PC
After manually stop and restart the TS target is 127.0.0.1, after click in Quick-Tune the TS target IP changes to my PC´s IP
I didn´t change the multihub launch file -
Re: Winterhill UDP broadcast
Maybe running without a router is causing complications. You must be using fixed IP addresses? I can't try that easily here.
Try logging in directly on the RPi and shut down WH.
Open a terminal window
cd ~/winterhill/RPi-3v20
sudo ./winterhill-3v20 230.0.0.230 9900 0 0 0 0 0
and see if it gives any errors. I'm doing that from memory, so I think it's correct.
This should start WH in multihub mode.
Brian
Try logging in directly on the RPi and shut down WH.
Open a terminal window
cd ~/winterhill/RPi-3v20
sudo ./winterhill-3v20 230.0.0.230 9900 0 0 0 0 0
and see if it gives any errors. I'm doing that from memory, so I think it's correct.
This should start WH in multihub mode.
Brian
Re: Winterhill UDP broadcast
Hello Brian,
that's it !
With the manual start and allocation of the IP addresses, we are on the right way.
Now the UDP address of the Winterhill stays at 230.0.0.230 and I can access it from the PC with several programmes without collision.
Now I just have to integrate this into the autostart and test it out further.
Many thanks for your help!
73 de Robert, DD4YR
that's it !
With the manual start and allocation of the IP addresses, we are on the right way.
Now the UDP address of the Winterhill stays at 230.0.0.230 and I can access it from the PC with several programmes without collision.
Now I just have to integrate this into the autostart and test it out further.
Many thanks for your help!
73 de Robert, DD4YR
Re: Winterhill UDP broadcast
Good. I'm still not sure why the normal multihub startup does not work.
Brian
Brian