ModeSDeco2 and ModeSMixer2 - console programs for RTLSDR and transcoding

[spotter.ssol]

modesmixer2 --inConnect xxx.xxx.xxx.xxx:8080 --outServer beast:30005 --inConnect localhost:30004

How it flows:
-MM2 connects to my remote station feeding BEAST on port 8080 (--inConnect xxx.xxx.xxx.xxx:8080);
-MM2 serves BEAST on port 30005, in which Piaware connects (--outServer beast:30005);
-Piaware's MLAT feed is serving on port 30004, in which MM2 connects (--inConnect localhost:30004).

[IanH]

Piaware's MLAT feed is no longer on port 30004. The information is not so easy to find.

There are two versions of dump1090 used by Flightaware. I'm using the "mutability" version where Beast MLAT output is available on port 30105.

For the Flightaware version of dump1090, the MLAT output might be on port 30104 (which was deliberately changed from port 30004).

Try whichever applies to you and let us know which works.

[Anmer]

Piaware's MLAT feed is no longer on port 30004. The information is not so easy to find.

Can I access a streaming ADS-B data feed from FlightFeeder or PiAware?

Yes, FlightFeeders and PiAware supports TCP connections to the following ports for data access:

30002 for raw/unparsed messages in AVR format

30003 for parsed messages in BaseStation format

30005 for raw/unparsed messages in Beast binary format

30105 for multilateration results (only) in Beast binary format (for FlightFeeders, the device must be running 7.x or newer software)

30106 for multilateration results (only) in extended BaseStation format (for FlightFeeders, the device must be running 7.x or newer software)

https://flightaware.com/adsb/faq#datafeed

[IanH]

Ah should have found that instead of looking in obscure places. 

Anyway also found my source for default ports as set up on dump1090 according to "obj":

The default configuration is to return results in three ways:

* Connecting to localhost:30104 and sending results there; this is used to feed the dump1090 map.
* Listening on port 30105 and providing Beast-format results
* Listening on port 30106 and providing "extended basestation" format results

VRS can be configured to connect to either 30105 or 30106 to receive mlat results. This is in addition to port 30005; you need to configure two feeds, one to receive the off-the-air data, one to receive the mlat results. You can combine them within VRS if you like

http://discussions.flightaware.com/ads-b-flight-tracking-f21/vrs-show-both-dump1090-adsb-and-fa-mlat-positions-t36086-75.html

Hence in my setup I am taking the ADSB data from the RPi on port 30005 and combining it with MLAT results sent back from Flightaware on port 30105 to serve on another port of my choosing (since I don't use the alternative VRS to combine the two data streams).

[spotter.ssol]

Hi all!

I don't think that the problem in my case is related to port values. There's a very common misunderstanding that those values cannot be changed. They're just the default settings, and you can overwrite to other values in config. You just have to make sure that services that need to be connected are pointed to the correct ports. This capability is necessary, otherwise many users like me, with remote stations, may have trouble with firewalls from ISP's.
For more info about advanced configuration in V3, see https://flightaware.com/adsb/piaware/advanced_configuration.
Right now I'm proceeeding tests with piaware v3 with default port values, but still no go. 

[spotter.ssol]

Just to remember, the same setup with V2 works 100%.

[sergsero]

Hello,

From myself I can add that was conducted experiment to verify that modesmixer2 can process non-transponder-based (Downlink Format 18 (DF=18)) 1090 MHz Extended Squitter (1090ES) messages in compliance with published standards, as Federal Aviation Administration (FAA) DO-260B Minimum Operational Performance Specifications (MOPS) were issued on December 13, 2011.

The non-transponder-based 1090ES target messages (DF=18) were properly formatted, processed at the required rate, and essentially indistinguishable from the similar transponder-based (DF=17) target messages. The transmission descriptor decoded in accordance with RTCA Document DO-181C.

As is well known, the DF=18 format used as for the generation of ADS-B Out messages in aircraft that are not equipped with Mode S transponders, as for much of general aviation. The MOPS specifically allows for the generation of ADS-B Out messages in these aircraft that may only have Mode A/C - Air Traffic Control Radar Beacon System (ATCRBS) transponders.

For these aircraft, the DF field shall be set to DF=18 (binary 10010) for all ADS-B message transmissions from transmission devices that are not Mode S transponder based systems.

At the same time these DF=18 messages can be used for Traffic Information Services-Broadcast (TIS-B). The three-bit Code Format (CF) field serves to differentiate DF=18 ADS-B messages and DF=18 TIS-B messages.

DF=18, CF=0 indicates that the Aircraft Address (AA) field holds the aircraft's permanent 24-bit International Civil Aviation Organization (ICAO) address.
DF=18, CF=1 is used for all other non-transponder-based ADS-B message generation where the AA field holds another kind of address for the transmitting ADS-B client, which can be a self-assigned "anonymous" airborne target address, a surface vehicle address, or a fixed obstruction address.

The ADS-B messages from ADS-B transmitting sub-systems that are not based on Mode S transponders shall use CF=0 or 1, according to the type of address conveyed in the AA field.

As Oliver reported: "mlat-client now returns results as DF 18 TIS-B positions." Unfortunately, I am unable to test the real MLAT data feed from FlightAware server. But if it conform to standard requirements, it shall be processed by modesmixer2.

However, I will investigate the problem further.

Best regards,
sergsero

[IanH]

I agree that any ports can be set up - I just suggested to try with the default values.

Curious it doesn't work - you obviously know what you are doing.

[spotter.ssol]

IanH,

which version of mm2 are you running? On which OS and platform?

Good news - looks like modesmixer2 is mostly compatible with Piaware 3 

I had been testing the output of modesmixer2 in PlanePlotter and was combining the data to sbs30006 format - that seems to be the problem.

If I combine the Piaware outputs from port 30005 and 30105 and serve it in Beast format, both ADSB and MLAT data are plotted.

Code Select Expand

modesmixer2.exe --inConnect 192.168.0.179:30005 --inConnect 192.168.0.179:30105 --outServer beast:31005

Serving as sbs10001 to BaseStation also works.

Just the sbsb30006 conversion seems to cause problems.


So returning to the question from spotter.ssol, what is your modesmixer command line?

We should be abler to get it to work with Piaware 3

[IanH]

Running MM2 on Windows XP, MM2 version 20150825

(Win XP because it needs less resource than Win7  )

But I can try other OS if it helps


Edit: Beast output from MM2 seems to work ok on Debian 8.6 x64 showing combined ADSB and MLAT  from both Piaware 2 and Piaware 3. Two USAF C130 targets seen but not much MLAT at this time of night

Might be worthwhile trying VRS to see how that works - can be useful for diagnosing problems

[spotter.ssol]

Hi sergsero,

first, thanks for your continuous support. If it could help, here's some data for you.
I've setted up 2 stations, one with piaware v2.1-5 (working mlat) and other with v3.1 (non working mlat). Both with same behavior:
-MM2 connecting to a remote station on port 8080 (--inConnect xxx.xxx.xxx.xxx:8080);
-MM2 serving BEAST on port 30005, in which Piaware connects (--outServer beast:30005);
-Piaware's MLAT feed is serving on port 30105, in which MM2 connects (--inConnect localhost:30105).

All logs saying ok an connected. I've captured traffic using tcpdump on both machines, filtering the mlat data feed on port 30105. If anybody see some error in this setup, please contribute to the discussion.

Here's some raw data flowing from V2 (working):

Code Select Expand

ff004d4c4154008de4838790af85c45014e1a74d4d1a33ff004d4c4154008de48387990487aff8040065eb87
1a33ff004d4c4154008de4838790af81862fd2ddfe37c41a33ff004d4c4154008de4838790af85c3f214d9c13ef61a33ff004d4c4154008de48387990486b058040005bcce
1a33ff004d4c4154008de482bc906511eb265796be95c41a33ff004d4c4154008de482bc906516273a972841ab601a33ff004d4c4154008de482bc9901048a380400c4b60a
1a33ff004d4c4154008de482b3908d0084a9e0c67046111a33ff004d4c4154008de482b3908d04c6b8228161ef1b1a33ff004d4c4154008de482b39905968e188c004ed281
1a33ff004d4c4154008de482b3908bf0848be0aafb85ee1a33ff004d4c4154008de482b3908bf4c6982265f6f2ca1a33ff004d4c4154008de482b39905928e188c0042f9b9
1a33ff004d4c4154008de482bc906511eafe57c84545891a33ff004d4c4154008de482bc90651627149759bbdac61a33ff004d4c4154008de482bc9901038a58040002061b
1a33ff004d4c4154008de48617909b90c54ffd8d0109521a33ff004d4c4154008de48617909b95064a3ec2ddba5a1a33ff004d4c4154008de486179900c42d905c0057ddf4
1a33ff004d4c4154008de482bc906511ead657f86fbac01a33ff004d4c4154008de482bc90651626ec9788fdd02a1a33ff004d4c4154008de482bc9901028a7804004470fc1a33ff004d4c4154008de48d4290914154bc0d6262cc111a33ff004d4c4154008de48d4290914593524e4db48c721a33ff004d4c4154008de48d429900f02a106000d4c1f1
1a33ff004d4c4154008de4838790af918547d2b71194051a33ff004d4c4154008de4838790af95c30e14b4ad5b5f1a33ff004d4c4154008de48387990485b05004006e0194
1a33ff004d4c4154008de482b3908bb08445e03e1c4f311a33ff004d4c4154008de482b3908bb4c65421fb18ea601a33ff004d4c4154008de482b399058d8e3888001e7d6a
1a33ff004d4c4154008de48617909bc0c68bfddddbdf841a33ff004d4c4154008de48617909bc5077e3f115eb1be1a33ff004d4c4154008de486179900c52df05c009b5341
1a33ff004d4c4154008de4838790af9183b9d275579d1c1a33ff004d4c4154008de4838790af95c18614738552d81a33ff004d4c4154008de48387990485b07004002b7dbd
1a33ff004d4c4154008de482bc906511ea9e5846d7dff31a33ff004d4c4154008de482bc90651626b497d538118b1a33ff004d4c4154008de482bc9901028a98040061f02a
1a33ff004d4c4154008de482b3908b6083eddfa1fa7db41a33ff004d4c4154008de482b3908b64c5fe2162ce718f1a33ff004d4c4154008de482b399058c8e188800580b8d
1a33ff004d4c4154008de4838790af918313d25b8c7ae31a33ff004d4c4154008de4838790af95c0e414597b2eb51a33ff004d4c4154008de48387990485b0b004004b8142
1a33ff004d4c4154008de48617909d10c84dfe596ca7ee1a33ff004d4c4154008de48617909d15093a3f8b0ac7e21a33ff004d4c4154008de486179900c72e305c0081bdd7
1a33ff004d4c4154008de48d429091c156d20e1a1ad2beaf1a33ff004d4c4154008de48d429091c595604f0247ae821a33ff004d4c4154008de48d429900ed29b060002065e6
1a33ff004d4c4154008de482bc906511ea6458925e4cf11a33ff004d4c4154008de482bc906516267c981f68ea2b1a33ff004d4c4154008de482bc9901028a98040061f02a
1a33ff004d4c4154008de482b39089f08385dedd083bd11a33ff004d4c4154008de482b39089f4c59820a187eb841a33ff004d4c4154008de482b399058a8df8840043e80a
1a33ff004d4c4154008de4838790af91821fd231fc5a1b1a33ff004d4c4154008de4838790af95bff21430c42e7d1a33ff004d4c4154008de48387990486b0d00400811a1a6b
1a33ff004d4c4154008de48d429091b156d20e1a1a41f80f1a33ff004d4c4154008de48d429091b595604f02d4e8221a33ff004d4c4154008de48d429900ed29b05c00b6a3ef
1a33ff004d4c4154008de482bc906511ea3a58c448eca81a33ff004d4c4154008de482bc906516265298516c1a1aad1a33ff004d4c4154008de482bc9901018ad80400ee172a
1a33ff004d4c4154008de48d429091f1581e0e8ce597321a33ff004d4c4154008de48d429091f596a64f7224fb261a33ff004d4c4154008de48d429900eb29905800c1d762
1a33ff004d4c4154008de482bc906511e9ea59288252781a33ff004d4c4154008de482bc906516260498b31207621a33ff004d4c4154008de482bc9901018af80400ab6b03
1a33ff004d4c4154008de4838790af818133d209ad2f2f1a33ff004d4c4154008de4838790af85bf0a14099c415e1a33ff004d4c4154008de48387990486b0d80400efb863
1a33ff004d4c4154008de48d4290930158aa0ebe5daa551a33ff004d4c4154008de48d4290930597304fa4ec939f1a33ff004d4c4154008de48d429900ed29d058004111941a33ff004d4c4154008de482b390898082fdddf3df61301a33ff004d4c4154008de482b3908984c5121fbb0fff251a33ff004d4c4154008de482b39905898df8840046f758
1a33ff004d4c4154008de482bc906511e9be595ee0391b1a33ff004d4c4154008de482bc90651625da98e86d18301a33ff004d4c4154008de482bc9901018b180400a51686
1a33ff004d4c4154008de4838790af818035d1d5bc10581a33ff004d4c4154008de4838790af85be1213d6d5bfa51a33ff004d4c4154008de4838799048ab1380400f5b8ae
1a33ff004d4c4154008de48d42909311593e0ef0453d7e1a33ff004d4c4154008de48d4290931597c24fd5c2053a1a33ff004d4c4154008de48d429900ef2a1058005bff02
1a33ff004d4c4154008de482bc906511e98259aa246ed01a33ff004d4c4154008de482bc906516259e99332541e01a33ff004d4c4154008de482bc9901018b180400a51686
1a33ff004d4c4154008de482b390896082e7ddcdaf23ca1a33ff004d4c4154008de482b3908964c4fc1f9664dd841a33ff004d4c4154008de482b39905898e1884001f707b
1a33ff004d4c4154008de482b39087f0827bdd0de702f11a33ff004d4c4154008de482b39087f4c4921ed9393bf31a33ff004d4c4154008de482b39905878df88400549f8c
1a33ff004d4c4154008de482b39087b0827bdcbcd26f501a33ff004d4c4154008de482b39087b4c4921e8a0703d91a33ff004d4c4154008de482b39905888d3888006d5b69
1a33ff004d4c4154008de482b3908790825bdc72f29b581a33ff004d4c4154008de482b3908794c4741e426bd6851a33ff004d4c4154008de482b39905868cf88800343211
1a33ff004d4c4154008de482b39087208217db9e25dae51a33ff004d4c4154008de482b3908724c42e1d718ed99e1a33ff004d4c4154008de482b399058c8c588800850979

And here's some raw data from V3 (non working):

Code Select Expand

1a33ff004d4c41540092e482bc9065120e05d22816efa41a33ff004d4c41540092e482bc906516498212fa7cc6ad1a33ff004d4c41540092e482bc99010b84b00400c48dcb
1a33ff004d4c41540092e47e759099510d1dbe558767491a33ff004d4c41540092e47e759099554ce400b04d7e181a33ff004d4c41540092e47e759904f1adb8800075f87e
1a33ff004d4c41540092e482bc9065120defd2783901b51a33ff004d4c41540092e482bc906516496e13480883441a33ff004d4c41540092e482bc99010b84b00400c48dcb
1a33ff004d4c41540092e4838790af922d0bc59de0c6e21a33ff004d4c41540092e4838790af96680606a8aa99de1a33ff004d4c41540092e483879905808ab00800fc79e0
1a33ff004d4c41540092e482b3909b80bdda50a73ef8e81a33ff004d4c41540092e482b3909b84fef4905ac94b981a33ff004d4c41540092e482b39905b68d90040093b830
1a33ff004d4c41540092e4838790af922cedc54dc627991a33ff004d4c41540092e4838790af9667e8065abb167d1a33ff004d4c41540092e483879905818ab00800ff732e
1a33ff004d4c41540092e482bc9065120dddd2ad4138491a33ff004d4c41540092e482bc906516495c137c8a0aa11a33ff004d4c41540092e482bc99010b84b00400c48dcb1a33ff004d4c41540092e482b3909b80bd9c50499de96d1a33ff004d4c41540092e482b3909b84feb88ffd59c3121a33ff004d4c41540092e482b39905b98dd80400668070
1a33ff004d4c41540092e47e759097b10b8bbdc5c0708a1a33ff004d4c41540092e47e759097b54b580023fc1cb91a33ff004d4c41540092e47e759904f2acd88800e4f2041a33ff004d4c41540092e4838790af922c99c48e16d6c41a33ff004d4c41540092e4838790af966796059d02ce9c1a33ff004d4c41540092e483879905808ab00800fc79e0
1a33ff004d4c41540092e482bc9065120dc3d2e22204ff1a33ff004d4c41540092e482bc906516494213b011d8c51a33ff004d4c41540092e482bc99010a84f004004d7f57
1a33ff004d4c41540092e4838790af922c91c46982e0f81a33ff004d4c41540092e4838790af96678e0579b454a21a33ff004d4c41540092e4838799057f8a7008006432ac
1a33ff004d4c41540092e482bc9065120db1d34e23eebc1a33ff004d4c41540092e482bc9065164932141a1a2f93291a33ff004d4c41540092e482bc99010b84b00400c48dcb
1a33ff004d4c41540092e4838790af922c73c41bbe76bf1a33ff004d4c41540092e4838790af966770052d0d90641a33ff004d4c41540092e483879905808a7008009c851f
1a33ff004d4c41540092e482b3909b70bd084f1dcde2731a33ff004d4c41540092e482b3909b74fe268ed63559c61a33ff004d4c41540092e482b39905b68db80400b866111a33ff004d4c41540092e482bc9065120d9fd381dfecf31a33ff004d4c41540092e482bc9065164920144cea382e1a33ff004d4c41540092e482bc99010a84b00400c78705
1a33ff004d4c41540092e482b3909b80bcee4ec70cb7561a33ff004d4c41540092e482b3909b84fe0c8e82efa1421a33ff004d4c41540092e482b39905b58d700400b327b4
1a33ff004d4c41540092e47e759097010949bcca3615b01a33ff004d4c41540092e47e759097054923ff2deb82681a33ff004d4c41540092e47e759904fcab3880007084bf
1a33ff004d4c41540092e4838790af922c0dc331c5601d1a33ff004d4c41540092e4838790af96670c04474a80241a33ff004d4c41540092e483879905818a7008009f8fd1
1a33ff004d4c41540092e482b3909b70bc8e4e18d123b41a33ff004d4c41540092e482b3909b74fdae8dd7201a1a1f1a33ff004d4c41540092e482b39905b58db80400bd7943
1a33ff004d4c41540092e4838790af822bd9c29e5bbd171a33ff004d4c41540092e4838790af8666d803b7f4bc341a33ff004d4c41540092e4838799057e8a300800edc030

[spotter.ssol]

Thanks again, IanH. Followed your suggestion and installed VRS, pointed to the same machine where piaware V3 is installed. MLAT feed from V3 is working on VRS.
I'm concluding that the problem may be two things:
-the way I set up to connect things in V3 is not right, even if it's working for V2 OR;
-MM2 is having trouble to understand the mlat format.
Let's wait and see if we discover anything new about this. I'm done for today. 

Running MM2 on Windows XP, MM2 version 20150825

(Win XP because it needs less resource than Win7  )

But I can try other OS if it helps


Edit: Beast output from MM2 seems to work ok on Debian 8.6 x64 showing combined ADSB and MLAT  from both Piaware 2 and Piaware 3. Two USAF C130 targets seen but not much MLAT at this time of night

Might be worthwhile trying VRS to see how that works - can be useful for diagnosing problems

[sergsero]

Hi spotter.ssol,

Thank you for the information. I'll try to fix the issue using the above sample messages.
It is possible that I will need your help with getting more data, preferably as file in binary data format beast, which I can somewhere download.

Best regards,
sergsero

[spotter.ssol]

Hi sergsero,

I've sent you by PM a live link to my MLAT return feed (v3.1). Please report if you have success connecting.

[Conexia]

PROBLEM FIXED. THE flightroute.sqb DATABASE WAS CORRUPT. I HAVE DOWNLOADED AGAIN AND WORKED. Thanks.

Hello to everyone
I have installed and run ModeSDeco2 and a very happy with it. Added BaseStation.sqb and it is updating the database and adding new aircraft.
My problem is with flightroute.sqb database. It is placed in the same flder than  BaseStation.sqb and the route in my .bat file is the same.
When I run the bat I get errors:

2016-11-16 19:02:46.018  INFO     Magnetic declination value was calculated
2016-11-16 19:02:46.102  INFO     Device: 0 mnf: Realtek prod: RTL2838UHIDIR serial: 00000001
2016-11-16 19:02:46.646  INFO     Supported Gains (dB):  0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 15.7 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 40.2 42.1 43.4 43.9 44.5 48.0 49.6
2016-11-16 19:02:46.650  INFO     Freq Correction: 0 ppm
2016-11-16 19:02:46.703  INFO     Gain: 49.6 dB
2016-11-16 19:02:46.710  INFO     AGC: Off
2016-11-16 19:02:46.711  INFO     Start Beast Server on port 30005
2016-11-16 19:02:46.712  INFO     Start MSG Server on port 30003
2016-11-16 19:02:46.716  INFO     Open DB session
2016-11-16 19:02:54.316  ERROR    sqlite3_prepare_v2() SELECT route FROM FlightRoute WHERE flight = ? ORDER BY updatetime DESC LIMIT 1; no such table: FlightRoute
2016-11-16 19:02:54.319  ERROR    sqlite3_step() no such table: FlightRoute 1
2016-11-16 19:03:33.619  ERROR    sqlite3_prepare_v2() SELECT route FROM FlightRoute WHERE flight = ? ORDER BY updatetime DESC LIMIT 1; no such table: FlightRoute
2016-11-16 19:03:36.918  ERROR    sqlite3_step() no such table: FlightRoute 1
2016-11-16 19:04:06.438  ERROR    sqlite3_prepare_v2() SELECT route FROM FlightRoute WHERE flight = ? ORDER BY updatetime DESC LIMIT 1; no such table: FlightRoute
2016-11-16 19:04:06.472  ERROR    sqlite3_step() no such table: FlightRoute 1
2016-11-16 19:04:09.873  ERROR    sqlite3_prepare_v2() SELECT route FROM FlightRoute WHERE flight = ? ORDER BY updatetime DESC LIMIT 1; no such table: FlightRoute
2016-11-16 19:04:09.879  ERROR    sqlite3_step() no such table: FlightRoute 1
2016-11-16 19:04:53.934  ERROR    sqlite3_prepare_v2() SELECT route FROM FlightRoute WHERE flight = ? ORDER BY updatetime DESC LIMIT 1; no such table: FlightRoute
2016-11-16 19:04:53.934  ERROR    sqlite3_step() no such table: FlightRoute 1
2016-11-16 19:07:57.727  ERROR    sqlite3_prepare_v2() SELECT route FROM FlightRoute WHERE flight = ? ORDER BY updatetime DESC LIMIT 1; no such table: FlightRoute
2016-11-16 19:07:57.732  ERROR    sqlite3_step() no such table: FlightRoute 1
2016-11-16 19:13:37.299  ERROR    sqlite3_prepare_v2() SELECT route FROM FlightRoute WHERE flight = ? ORDER BY updatetime DESC LIMIT 1; no such table: FlightRoute
2016-11-16 19:13:37.299  ERROR    sqlite3_step() no such table: FlightRoute 1
2016-11-16 19:20:38.343  ERROR    sqlite3_prepare_v2() SELECT route FROM FlightRoute WHERE flight = ? ORDER BY updatetime DESC LIMIT 1; no such table: FlightRoute
2016-11-16 19:20:38.343  ERROR    sqlite3_step() no such table: FlightRoute 1
2016-11-16 19:23:27.510  ERROR    sqlite3_prepare_v2() SELECT route FROM FlightRoute WHERE flight = ? ORDER BY updatetime DESC LIMIT 1; no such table: FlightRoute
2016-11-16 19:23:27.510  ERROR    sqlite3_step() no such table: FlightRoute 1
2016-11-16 19:24:45.924  ERROR    sqlite3_prepare_v2() SELECT route FROM FlightRoute WHERE flight = ? ORDER BY updatetime DESC LIMIT 1; no such table: FlightRoute
2016-11-16 19:24:45.924  ERROR    sqlite3_step() no such table: FlightRoute 1
2016-11-16 19:30:38.829  ERROR    sqlite3_prepare_v2() SELECT route FROM FlightRoute WHERE flight = ? ORDER BY updatetime DESC LIMIT 1; no such table: FlightRoute
2016-11-16 19:30:39.122  ERROR    sqlite3_step() no such table: FlightRoute 1

If I delete --frdb D:\_MODESDECO\dbase\flightroute.sqb from the .bat file all works fine (without routes, of course)

Can anyone help?

Thanks in advance

Antonio