Motor/Scanning Bug, All devices.

[RustySpoons]

Since the "Fix" for the motor bug, another bug is present, the time-out is broken if the first transponder it tries to scan is inactive.

When you do first do a manual scan of a Single Satellite, if the first transponder it tries to scan is inactive it will sit there forever.
I currently get around this by manually tuning a known "Active" transponder on the satellite I wish to scan, it will then lock, return to manual scan and select single satellite and it will then start scanning.

You are also unable to do a Automatic scan, as if the dish moves to a position where the first transponder it tries to scan is inactive it will stay there.

This is present on ALL OA-E Images not just ViX and present on all boxes that have had the latest commit.

[Emulated]

Yes I have that problem so used a much earlier image and I notice there were some posts in another forum about this.

[Emulated]

No one appears to bother about this problem. I contacted Gigablue and they inform me its a problem with the images and would be the same on all E2 receivers. If so is it worth bothering with an E2 receiver or better to go for Android.

[abu baniaz]

We have to guess which satellite and the dead transponder being referred to.

E2 developers do this in their own time, it is a hobby. "Read my mind" posts tend to get ignored. Is it really that difficult to be more descriptive and post debug logs?

[RustySpoons]

We have just had a family bereavement and I'm going to the funeral today, I'll try and put some logs up on here at some point.

[Emulated]

We have to guess which satellite and the dead transponder being referred to.

E2 developers do this in their own time, it is a hobby. "Read my mind" posts tend to get ignored. Is it really that difficult to be more descriptive and post debug logs?
Hey ho what an attitude and as such I will ignore WOS as they appear to have the same mindset as you. Remember, there are other forums with links to other sellers. There are other images besides Vix and you need us more than we need you.

[Sicilian]

Hey ho what an attitude and as such I will ignore WOS as they appear to have the same mindset as you. Remember, there are other forums with links to other sellers. There are other images besides Vix and you need us more than we need you.

Thats a bit harsh. Without a report of the actual satellite how are we supposed to look at this? Just the name of the actual satellite would be a start. I spent couple of hours manual single satellite scanning 13, 19 and 28.2 yesterday with no issues.

Please provide the satellite where you have this issue so at least we can try and replicate the issue.

[Tkr001]

Hey ho what an attitude and as such I will ignore WOS as they appear to have the same mindset as you. Remember, there are other forums with links to other sellers. There are other images besides Vix and you need us more than we need you.
Read Abu’s post again. He doesn't have an attitude apart from an attitude of helping many. All he is asking for is the info to be able to try and help you. As he says is it too hard to provide?

BTW i have no affiliation to the sponsor, heck he wont even sell to me due to my location!

[Emulated]

Maybe a bit harsh but I only referred to the general problem whereby on my Gigablue UHD UE 4K regardless of the image as a general enquiry and never expected an indifferent answer which came across as unfriendly. I load onto the box and set it to simple in tuner setup, choose the satellites, input my position and do an automatic scan. It sits there, nothing for hours. Do a manual scan and it may or may not work, depending on the satellite. It works on older Vix and other images from last December, therefore its something that has been altered in later images in general I will send a debug file later but it means I have to save my existing image and install a recent one to get a debug log.

[Sicilian]

Just a satellite name or degree will be a starting point.


Sent from my iPhone using Tapatalk

[Joe_90]

I've had this issue since the change in the code to handle the motor time-out problem, but worked around by using a different transponder to initiate the satellite search. I haven't had much time of late to do bug tracking, but if memory serves it happened on 15W and possibly on 30W when I did an initial scan using a clean build. If I get a chance I'll do some testing later today. It would appear that whatever transponder is first in the xml list for particular satellites is either dead or has changed tuning parameters such that the scan just waits indefinitely.

[Emulated]

Just a satellite name or degree will be a starting point.


Sent from my iPhone using Tapatalk
On the last Vix image from memory 15 west as I scan all the satellites in I can to see whats on them. I will reload the image later and try again by removing 15 west from the scan as there were other satellites.

[Joe_90]

I've tried 15W on my HD51 which is my motorised receiver. Snip from log below. I selected a whole satellite scan of 15W from the menu. As far as I can determine the first transponder is not receivable at my location as it's beamed at America. The log shows continual attempts at retuning without any timeout until I pressed the RED key to cancel. The behaviour (on my HD51) prior to the recent code changes was that it would stall on the transponder until the "rotor timeout" expired which could be from 70 seconds to several minutes depending on where the motor started from. Though this delay happened (on the old code) on a satellite change even if the transponder was live and receivable. With the current code I have no issues switching from one working transponder to another on the same or on different satellites. The problem only occurs when doing a full satellite scan which involves a motor move from another sat position. If I do a whole satellite scan of 15W while I'm tuned to a transponder on 15W, then the tuner times out on the unreceivable first transponder and moves to the next in the list.


< 104.667> [eDVBSatelliteEquipmentControl] Entry for 345,0? not in Rotor Table found... i try gotoXX?
< 104.667> [eDVBSatelliteEquipmentControl] siteLatitude = 53.xxxxx, siteLongitude = 354.xxxxx, 345.000000 degrees
< 104.667> [eDVBSatelliteEquipmentControl] PolarmountHourAngle=19x.xxxxx
< 104.667> [eDVBSatelliteEquipmentControl] RotorCmd = d0a3
< 104.667> [eDVBSatelliteEquipmentControl] RotorCmd d0a3, lastRotorCmd ffffffff
< 104.667> [eDVBSatelliteEquipmentControl] set rotor timeout to 360 seconds
< 104.667> [eDVBFrontend] prepare_sat System 1 Freq 10983000 Pol 0 SR 45000000 INV 2 FEC 8 orbpos 3450 system 1 modulation 1 pilot 2, rolloff 0, is_id -1, pls_mode 1, pls_code 0
< 104.667> [eDVBFrontend] tuning to 1233 mhz

The 10983H transponder is a Pan American beam according to Lyngsat, so is unreceivable in my location on the East cost of Ireland



< 104.667> [eDVBChannel] OURSTATE: tuning
< 104.674> [eDVBFrontend] set static current limiting
< 104.674> [eDVBFrontend] set sequence pos 3
< 104.674> [eDVBFrontend] setVoltage 1
< 104.691> [eDVBFrontend] sleep 900ms
< 104.791> [eInputDeviceInit] 0 18f 1
< 104.792> [InfoBarGenerics] KEY: 399 GREEN
< 105.591> [eDVBFrontend] set sequence pos 9
< 105.591> [eDVBFrontend] invalidate current rotorparams
< 105.682> [eDVBFrontend] sendDiseqc: e0316ed0a3(?)
< 105.683> [eDVBFrontend] sleep 1000ms
< 106.592> [DVBCAHandler] no more services
< 106.683> [eDVBFrontend] sleep 2000ms
< 107.664> [eDVBFrontend] close frontend 1
< 107.664> [eDVBFrontend] sendTone allowed only in feSatellite (2)
< 108.683> [eDVBFrontend] setVoltage 2
< 108.683> [eDVBFrontend] set sequence pos 3
< 108.683> [eDVBFrontend] set timeout 1440
< 108.683> [eDVBFrontend] setFrontend 0
< 108.683> [eDVBFrontend] setting frontend 0
< 108.684> [eDVBFrontend] sleep 250ms
< 108.934> [eDVBFrontend] rotor locked step 0 failed (not locked)
< 108.934> [eDVBFrontend] set sequence pos -4
< 108.934> [eDVBFrontend] sleep 250ms
< 109.184> [eDVBFrontend] rotor locked step 0 failed (not locked)
< 109.184> [eDVBFrontend] set sequence pos -4
< 109.185> [eDVBFrontend] sleep 250ms
< 109.435> [eDVBFrontend] rotor locked step 0 failed (not locked)
< 109.435> [eDVBFrontend] IF_LOCK_TIMEOUT_GOTO: got FE_TIMEDOUT
< 109.435> [eDVBFrontend] set sequence pos -4
< 109.435> [eDVBFrontend] setFrontend 0
< 109.435> [eDVBFrontend] setting frontend 0
< 109.435> [eDVBFrontend] sleep 250ms
< 109.685> [eDVBFrontend] rotor locked step 0 failed (not locked)
< 109.685> [eDVBFrontend] set sequence pos -4
< 109.685> [eDVBFrontend] sleep 250ms
< 109.935> [eDVBFrontend] rotor locked step 0 failed (not locked)
< 109.936> [eDVBFrontend] set sequence pos -4
< 109.936> [eDVBFrontend] sleep 250ms
< 110.186> [eDVBFrontend] rotor locked step 0 failed (not locked)
< 110.186> [eDVBFrontend] IF_LOCK_TIMEOUT_GOTO: got FE_TIMEDOUT
< 110.186> [eDVBFrontend] set sequence pos -4
< 110.186> [eDVBFrontend] setFrontend 0
< 110.186> [eDVBFrontend] setting frontend 0
< 110.186> [eDVBFrontend] sleep 250ms
< 110.436> [eDVBFrontend] rotor locked step 0 failed (not locked)
< 110.436> [eDVBFrontend] set sequence pos -4
< 110.436> [eDVBFrontend] sleep 250ms
< 110.687> [eDVBFrontend] rotor locked step 0 failed (not locked)
< 110.687> [eDVBFrontend] set sequence pos -4
< 110.687> [eDVBFrontend] sleep 250ms
< 110.937> [eDVBFrontend] rotor locked step 0 failed (not locked)
< 110.937> [eDVBFrontend] IF_LOCK_TIMEOUT_GOTO: got FE_TIMEDOUT
< 110.937> [eDVBFrontend] set sequence pos -4
< 110.937> [eDVBFrontend] setFrontend 0
< 110.937> [eDVBFrontend] setting frontend 0
< 110.937> [eDVBFrontend] sleep 250ms
< 111.187> [eDVBFrontend] rotor locked step 0 failed (not locked)
< 111.187> [eDVBFrontend] set sequence pos -4
< 111.187> [eDVBFrontend] sleep 250ms
< 111.438> [eDVBFrontend] rotor locked step 0 failed (not locked)
< 111.438> [eDVBFrontend] set sequence pos -4
< 111.438> [eDVBFrontend] sleep 250ms
< 111.688> [eDVBFrontend] rotor locked step 0 failed (not locked)
< 111.688> [eDVBFrontend] IF_LOCK_TIMEOUT_GOTO: got FE_TIMEDOUT
< 111.688> [eDVBFrontend] set sequence pos -4
< 111.688> [eDVBFrontend] setFrontend 0
< 111.688> [eDVBFrontend] setting frontend 0
< 111.688> [eDVBFrontend] sleep 250ms
< 111.938> [eDVBFrontend] rotor locked step 0 failed (not locked)
< 111.938> [eDVBFrontend] set sequence pos -4
< 111.938> [eDVBFrontend] sleep 250ms
< 112.189> [eDVBFrontend] rotor locked step 0 failed (not locked)
< 112.189> [eDVBFrontend] set sequence pos -4
< 112.189> [eDVBFrontend] sleep 250ms
.........
............
............. and so on until I manually cancel using the RED key at this point -------------------------



< 233.615> [eDVBFrontend] rotor locked step 0 failed (not locked)
< 233.615> [eDVBFrontend] set sequence pos -4
< 233.615> [eDVBFrontend] sleep 250ms
< 233.865> [eDVBFrontend] rotor locked step 0 failed (not locked)
< 233.865> [eDVBFrontend] set sequence pos -4
< 233.865> [eDVBFrontend] sleep 250ms
< 234.115> [eDVBFrontend] rotor locked step 0 failed (not locked)
< 234.115> [eDVBFrontend] IF_LOCK_TIMEOUT_GOTO: got FE_TIMEDOUT
< 234.115> [eDVBFrontend] set sequence pos -4
< 234.115> [eDVBFrontend] setFrontend 0
< 234.115> [eDVBFrontend] setting frontend 0
< 234.115> [eDVBFrontend] sleep 250ms
< 234.366> [eDVBFrontend] rotor locked step 0 failed (not locked)
< 234.366> [eDVBFrontend] set sequence pos -4
< 234.366> [eDVBFrontend] sleep 250ms
< 234.616> [eDVBFrontend] rotor locked step 0 failed (not locked)
< 234.616> [eDVBFrontend] set sequence pos -4
< 234.616> [eDVBFrontend] sleep 250ms
< 234.749> [eDVBFrontend] close frontend 0
< 243.255> [eInputDeviceInit] 1 18e 1
< 243.256> [InfoBarGenerics] KEY: 398 RED
< 243.256> [ActionMap] SetupActions cancel
< 243.256> [Navigation] playing 1:0:16:451:3E9:2174:EEEE0000:0:0:0:
< 243.267> [eDVBServicePlay] timeshift
< 243.267> [eDVBServicePlay] timeshift
< 243.268> [eDVBServicePlay] timeshift
< 243.269> [Notifications] RemovePopup, id = ZapError
< 243.269> [eDVBResourceManager] allocate channel.. 03e9:2174
< 243.269> [eDVBFrontend] opening frontend 1
< 243.277> [eDVBFrontend] (1)tune
< 243.277> [eDVBFrontend] tune setting type to 2 from 0
< 243.277> [eDVBChannel] OURSTATE: tuning
< 243.277> [eDVBServicePMTHandler] allocate Channel: res 0
< 243.277> [eDVBCIInterfaces] addPMTHandler 1:0:16:451:3E9:2174:EEEE0000:0:0:0:
< 243.277> [eDVBChannel] getDemux cap=00
< 243.277> [eDVBResourceManager] allocate demux cap=00
< 243.277> [eDVBResourceManager] allocating demux adapter=0, demux=0, source=0 fesource=1
< 243.277> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
< 243.279> [eDVBFrontend] startTuneTimeout 5000
< 243.285> [eDVBFrontend] setVoltage 0
< 243.285> [eDVBFrontend] setFrontend 1
< 243.285> [eDVBFrontend] setting frontend 1
< 243.285> [eDVBFrontend] (1)fe event: status 0, inversion off, m_tuning 1
< 243.463> [eInputDeviceInit] 0 18e 1
< 243.464> [InfoBarGenerics] KEY: 398 RED
< 243.663> [eDVBFrontend] (1)fe event: status 1f, inversion off, m_tuning 2
< 243.663> [eDVBChannel] OURSTATE: ok
< 243.663> [eDVBLocalTimerHandler] channel 0x10f9ff8 running
< 243.663> [eEPGCache] channel 0x10f9ff8 running
< 243.663> [eDVBChannel] getDemux cap=00
< 243.663> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
< 243.663> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
< 243.663> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
< 243.663> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
< 243.663> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
< 243.663> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
< 243.663> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
< 243.663> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
< 243.663> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
< 243.663> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
< 243.663> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
< 243.663> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
< 243.663> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
< 243.663> [eDVBResourceManager] stop release channel timer
< 243.663> [eDVBChannel] getDemux cap=01
< 243.663> [eDVBResourceManager] allocate demux cap=01
< 243.663> [eDVBResourceManager] allocating shared demux adapter=0, demux=0, source=1
< 243.663> [eDVBServicePMTHandler] ok ... now we start!!

[Joe_90]

I again tried to scan 15W from an adjacent satellite (30W). I tried this because the "Rotor Timeout" parameter is shorter (33 seconds) coming from here rather than in my first test where the Rotor Timeout parameter is set to 360 seconds as I was starting from 28E and I was aware that I hadn't let the six minutes run out before I cancelled the tune.

On this log you can see the rotor timeout timer expire and no further tuning attempts seem to happen although the menu GUI is still on-screen and appears to be "stuck" on the first transponder.


< 3578.729> [Skin] Parsing embedded skin <embedded-in-'ServiceScanSummary'>
< 3578.729> [Skin] processing screen <embedded-in-'ServiceScanSummary'>:
< 3578.731> [eDVBLocalTimerHandler] remove channel 0x10ac4c0
< 3578.731> [eEPGCache] remove channel 0x10ac4c0
< 3578.733> [eDVBChannel] getDemux cap=00
< 3578.733> [eDVBResourceManager] allocate demux cap=00
< 3578.733> [eDVBResourceManager] allocating demux adapter=0, demux=0, source=0 fesource=0
< 3578.733> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
< 3578.735> [eDVBFrontend] (0)tune
< 3578.735> [eDVBSatelliteEquipmentControl] Entry for 345,0? not in Rotor Table found... i try gotoXX?
< 3578.735> [eDVBSatelliteEquipmentControl] siteLatitude = 53.xxxxxx, siteLongitude = 354.xxxxxx, 345.000000 degrees
< 3578.735> [eDVBSatelliteEquipmentControl] PolarmountHourAngle=19x.xxxxxx
< 3578.735> [eDVBSatelliteEquipmentControl] RotorCmd = d0a3
< 3578.735> [eDVBSatelliteEquipmentControl] RotorCmd d0a3, lastRotorCmd d1aa
< 3578.735> [eDVBSatelliteEquipmentControl] set rotor timeout to 33 seconds <-----------------------------------------------------------------------------------------------------------------------
< 3578.735> [eDVBFrontend] prepare_sat System 1 Freq 10983000 Pol 0 SR 45000000 INV 2 FEC 8 orbpos 3450 system 1 modulation 1 pilot 2, rolloff 0, is_id -1, pls_mode 1, pls_code 0
< 3578.735> [eDVBFrontend] tuning to 1233 mhz
< 3578.735> [eDVBChannel] OURSTATE: tuning
< 3578.743> [eDVBFrontend] set static current limiting
< 3578.743> [eDVBFrontend] setTone 0
< 3578.744> [eDVBFrontend] sleep 25ms
< 3578.769> [eDVBFrontend] set sequence pos 4
< 3578.769> [eDVBFrontend] set sequence pos 5
< 3578.769> [eDVBFrontend] set sequence pos 3
< 3578.769> [eDVBFrontend] invalidate current rotorparams
< 3578.861> [eDVBFrontend] sendDiseqc: e0316ed0a3(?)
< 3578.862> [eDVBFrontend] sleep 1000ms
< 3578.871> [eInputDeviceInit] 0 18f 1
< 3578.872> [InfoBarGenerics] KEY: 399 GREEN
< 3579.862> [eDVBFrontend] sleep 2000ms
< 3580.667> [DVBCAHandler] no more services
< 3581.862> [eDVBFrontend] setVoltage 2
< 3581.862> [eDVBFrontend] set sequence pos 3
< 3581.862> [eDVBFrontend] set timeout 132
< 3581.862> [eDVBFrontend] setFrontend 0
< 3581.862> [eDVBFrontend] setting frontend 0
< 3581.862> [eDVBFrontend] sleep 250ms
< 3582.112> [eDVBFrontend] rotor locked step 0 failed (not locked)
< 3582.113> [eDVBFrontend] set sequence pos -4
< 3582.113> [eDVBFrontend] sleep 250ms
< 3582.363> [eDVBFrontend] rotor locked step 0 failed (not locked)
< 3582.363> [eDVBFrontend] set sequence pos -4
< 3582.363> [eDVBFrontend] sleep 250ms
< 3582.613> [eDVBFrontend] rotor locked step 0 failed (not locked)
< 3582.613> [eDVBFrontend] IF_LOCK_TIMEOUT_GOTO: got FE_TIMEDOUT
< 3582.613> [eDVBFrontend] set sequence pos -4
< 3582.613> [eDVBFrontend] setFrontend 0
< 3582.613> [eDVBFrontend] setting frontend 0
< 3582.613> [eDVBFrontend] sleep 250ms
< 3582.864> [eDVBFrontend] rotor locked step 0 failed (not locked)
< 3582.864> [eDVBFrontend] set sequence pos -4
< 3582.864> [eDVBFrontend] sleep 250ms
< 3583.114> [eDVBFrontend] rotor locked step 0 failed (not locked)
< 3583.114> [eDVBFrontend] set sequence pos -4
< 3583.114> [eDVBFrontend] sleep 250ms
< 3583.364> [eDVBFrontend] rotor locked step 0 failed (not locked)
< 3583.364> [eDVBFrontend] IF_LOCK_TIMEOUT_GOTO: got FE_TIMEDOUT
< 3583.364> [eDVBFrontend] set sequence pos -4
< 3583.364> [eDVBFrontend] setFrontend 0
< 3583.364> [eDVBFrontend] setting frontend 0
< 3583.364> [eDVBFrontend] sleep 250ms


and so on until the rotor timeout occurs after 33 seconds in this instance - the satellite scan menu dialogue remains on screen without moving to the next transponder, though!




< 3614.408> [eDVBFrontend] rotor locked step 0 failed (not locked)
< 3614.408> [eDVBFrontend] set sequence pos -4
< 3614.409> [eDVBFrontend] sleep 250ms
< 3614.659> [eDVBFrontend] rotor locked step 0 failed (not locked)
< 3614.659> [eDVBFrontend] set sequence pos -4
< 3614.659> [eDVBFrontend] sleep 250ms
< 3614.909> [eDVBFrontend] rotor locked step 0 failed (not locked)
< 3614.909> [eDVBFrontend] rotor timout <-------------------------------------------------------------------------------------------
< 3614.909> [eDVBFrontend] set sequence pos 5
< 3614.909> [eDVBFrontend] set sequence pos 4
< 3614.909> [eDVBFrontend] update current switch params
< 3614.909> [eDVBFrontend] sleep 500ms
< 3615.410> [eDVBFrontend] set dynamic current limiting
< 3629.476> [LogManager] Trim Poll Started
< 3629.479> [Task] job Components.Task.Job name=LogManager #tasks=1 completed with [] in None
< 3656.750> [NetworkTime] Updating
< 3656.750> [Console] command: /usr/bin/ntpdate-sync
< 3656.750> [eConsoleAppContainer] Starting /bin/sh
< 3662.884> [Console] finished: /usr/bin/ntpdate-sync
< 3662.884> [NetworkTime] setting E2 time: 1524579706.42
< 3986.075> [AutoTimer] current auto poll 2018-04-24 15:27:09
< 3986.076> [AutoTimer] Auto Poll Started
< 3986.076> [AutoTimer] No changes in configuration, won't parse
< 3986.078> [Task] job Components.Task.Job name=AutoTimer #tasks=0 completed with [] in None
< 3986.078> [AutoTimer] next auto poll at 2018-04-24 15:57:09

[abu baniaz]

Hey ho what an attitude and as such I will ignore WOS as they appear to have the same mindset as you. Remember, there are other forums with links to other sellers. There are other images besides Vix and you need us more than we need you.

What we need is people to be thorough and descriptive in their reports.

Nobody is a mind reader. Everyone uses their receiver with differences. Expecting people to know what the problem is without you actually stipulating it is not very conducive. It is actually counter productive because people waste time looking for a needle in a haystack. Actually, we don't even know we are searching for a needle. It could be anything.

If you want things fixed/improved, post details to work with.

My receiver crashed:- Post the crash log
This does not work:- Post the exact steps/options and hardware used. If possible, attach the debug log

I think you will find all "the mugs" who spend their time improving/fixing things require sufficient information to work with.

[RustySpoons]

On a fresh install using the Satellites.xml that comes with the image that last 2 that spring to mind are 19.2E and 4.8E if you go straight there and do a scan if the first transponder is dead it will sit there.
Basically any satellite that has a dead transponder first in the list. Unless you scan a known working transponder first.

[Joe_90]

@RustySpoons - I've posted a log of the issue on 15W. If you had identified the satellites at issue on your first post it would have saved trawling through the sats.

[Emulated]

I have tried every image going for the Gigablue UHD Quad 4K and the only one that works with no problems is the Openvix 5 1 002 19th Nov 2017. Maybe later ones but something is different and I will have to avoid updating.

[RustySpoons]

@RustySpoons - I've posted a log of the issue on 15W. If you had identified the satellites at issue on your first post it would have saved trawling through the sats.

As I mentioned there has been a family bereavement so my mind is all over the place at the moment, also the satellite will vary depending on setup and location.
I can't get all transponders on my dishes 1m/1.2m/2x Zone 1's so there will be a few that have a dead transponders for me.

I just bought a Mutant HD51 (And an Edision Primo IP S2) from the Sponsor, the Mutant arrived earlier and just setting it up now.
I'll log any issues...

[abu baniaz]

Sorry for your loss