Kitz Forum

Broadband Related => Broadband Hardware => Topic started by: burakkucat on August 20, 2014, 07:20:12 PM

Title: HG612 Firmware [August 2014] -- A "Test Run"
Post by: burakkucat on August 20, 2014, 07:20:12 PM
As Wolfy (Howlingwolf (http://forum.kitz.co.uk/index.php?action=profile;u=6710)) has released unlocked variants of Beattie's latest firmware image for the Huawei HG612 [1], the time was ripe to take the webgui image for a "test run".

My testing HG612 was flashed with the bcm96368MVWG_fs_kernel_HG612V100R001C01B030SP08_Webgui firmware image. It was then connected via a 1.5 metre "local loop" to a Planet VC-230N, the latter device being configured to operate in CO mode.

The VC-230N was powered up and allowed to stabilise. After two minutes had elapsed, power was then applied to the HG612. A further two minutes were allowed to elapse, so that the latter could also stabilise.

A sequence of screenshots were then captured. Two, showing the device configurations, are attached below.



[1] https://mega.co.nz/#F!LdJFDIJL!e_E1twsIg2kTet8mPjrb4w
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: burakkucat on August 20, 2014, 07:23:16 PM
Two further screenshots, showing both devices' status, are attached below.
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: burakkucat on August 20, 2014, 07:31:04 PM
Finally, a telnet connection was established to the HG612 and the usual data was harvested. Bald_Eagle1 then took the harvested data and produced his usual collection of graphical data.

Both the raw harvested data (as a ZIP format file) and the portrait montage are attached below.
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: NewtronStar on August 20, 2014, 10:59:37 PM
and waiting for your conslusion   ;D

I think the new 2014 firmware has zero impact in performance unlike kernel_HG612V100R001C01B030SP06 which did improve FTTC somewhat

Until B*Cat can test his model in the real world on FTTC your 1.5 meter local loop test is  unrealistic  :-\
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: burakkucat on September 06, 2014, 01:33:16 AM
Eleven months ago I attempted to gather statistics for the then available HG612 firmware images. [1] All was good for the ultra-short local loop (1.5 m) but the results for a longer loop were seriously degraded by a spool of copper coated steel cable. I made a note to source some new all-copper cable but never got around to doing so.

Last month I collected and shared the data relating to the latest firmware image from Beattie, once it had been unlocked and given back its GUI by Howlingwolf. N*Star's comment (the previous post) was still in my mind when I saw an offer of two 100 m spools, 0.5 mm copper conductors, three pair, CW1308 specification cable on a well-known auction web-site. The price? £11-99

The two spools of cable were delivered on Thursday afternoon. The first test, with a magnet, was passed. Not copper coated steel. The second test, a good scrape of a conductor with a sharp blade, was passed. Not copper coated aluminium.

Batteries were fitted into the Tester 301C, the green pair of one cable was shorted at the far end and the near-end was connected to the LINE sockets of the 301C by 1.6 m test leads. The near-end of the blue pair was connected to the REF sockets of the 301C by an identical set of 1.6 m test leads. With the BAL control set off, a very satisfying trace for a short-circuit was seen. Look closely at the second image (attached below) and you can see that the indicated length is slightly more than 104 m. The next increment, to 105 m, positioned the cursor to the right of the deviation from horizontal by as much as it was to the left, when set at 104 m. So the measured length of that spool of cable is 104 m "plus a bit". Remembering to subtract the length of the test leads, 1.6 m (i.e. 1 m "plus a bit") from the measured length, gave me a result of 103 m.

Next the Ohmmeter 18C was used to check the insulation resistance and conductor resistance of that spool of cable. Each pair (green, blue and orange) showed a very healthy insulation resistance greater than 1000 MOhms. Each pair showed an identical 18.4 Ohms value when shorted at the far end (over 206 m of conductor). Each individual conductor (of each pair) showed 9.5 Ohms (over 103 m of conductor). It was very satisfying to obtain consistent results for all the tests, for they showed the first spool of cable to be in excellent condition. I can therefore say that each of the six conductors has a resistance of 0.09 Ohm/metre.

Obviously I still need to check the second spool of cable, to determine its electrical length and condition. Once that has been done I should then be able to perform six separate experiments, with local loop lengths of 103 m, 206 m, 309 m, (309 + L) m, (309 + 2L) m and (309 + 3L) m, where L is the electrical length of the second spool of cable. I am assuming, of course, that fellow kitizens will be interested to see the results?  :-\

[1] http://forum.kitz.co.uk/index.php?topic=13160.0
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: NewtronStar on September 06, 2014, 02:15:01 AM
I am assuming, of course, that fellow kitizens will be interested to see the results?  :-\

I am very interested to see the results  :)
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: Ronski on September 06, 2014, 07:00:40 AM
Wouldn't using the three pairs joined in the single cable and still coiled up cause interference?

What about trying 103 + L? Then it can be compared to 103 + 103 in the same reel. Hopefully reel 2 is also 103 meters.
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: roseway on September 06, 2014, 07:05:13 AM
I'm certainly interested in the results. Measurements under rigorously controlled conditions are very much needed, to balance the anecdotal evidence which we so often depend on.
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: Bald_Eagle1 on September 06, 2014, 09:08:07 AM
I too would be interested in seeing the results.



Just thinking aloud.......................................

Another 'interesting' experiment at some stage might be this:-

Run a generated VDSL2 signal down one pair & a live ADSL signal down another pair, sort of simulating differingent DSL modes carried within a D-side cable bundle.

Connecting & disconnecting the ADSL & VDSL2 signals in turn, logging the effects accordingly might/might not provide some indication of how severe crosstalk really can be?


Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: burakkucat on September 06, 2014, 06:29:42 PM
Thank you all for the comments and suggestions.  :)

Ronski -- The self-interference by local coupling is something that Asbokid was uncertain about and he & I concluded that it could skew the results obtained but in a consistent fashion. I like your proposed experiment in using one pair from each spool in series and comparing the result with that of using two pairs from one spool in series.

Eric -- I share your view. Some results from a well-defined experimental set-up will be better than none at all. I can control the experimental environment quite carefully but I am limited with the equipment I have to paw.

BE1 -- A good proposal. Unfortunately that will be something I can not perform. The Planet VC230N only operates in VDSL2 mode and only has one "line port". To perform your suggested experiment would require usage of a DSLAM with two different line cards installed. Again, if I am remembering correctly, that was on Asbokid's ToDo list -- using his Huawei SmartAX MA5616 DSLAM.



I have now quantified the second spool of CW1308 cable. Just like the first spool, it is marked as 100 m of 0.5 mm diameter solid copper wire, 3 pair cable.

This time I connected one open-circuited pair to the LINE terminals and the short-circuited pair to the REF terminals of the Tester 301C. With the BAL control set off, a very satisfying trace for an open-circuited pair was seen. Look closely at the second image (attached below) and you can see that the indicated length is slightly less than 110 m. The previous increment, to 109 m, positioned the cursor to the left of the deviation from horizontal by as much as it was to the right, when set at 110 m. So the measured length of that spool of cable is 109 m "plus a bit". Remembering to subtract the length of the test leads, 1.6 m (i.e. 1 m "plus a bit") from the measured length, gave me a result of 108 m.

Once again the Ohmmeter 18C was used to check the insulation resistance and conductor resistance of that spool of cable. Each pair (green, blue and orange) showed a very healthy insulation resistance greater than 1000 MOhms. Each pair showed an identical 18.6 Ohms value when shorted at the far end (over 216 m of conductor). Each individual conductor (of each pair) showed 9.5 Ohms (over 108 m of conductor). As previously, I can therefore say that each of the six conductors has a resistance of 0.09 Ohm/metre.
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: Bald_Eagle1 on September 06, 2014, 06:52:43 PM

BE1 -- A good proposal. Unfortunately that will be something I can not perform. The Planet VC230N only operates in VDSL2 mode and only has one "line port". To perform your suggested experiment would require usage of a DSLAM with two different line cards installed. Again, if I am remembering correctly, that was on Asbokid's ToDo list -- using his Huawei SmartAX MA5616 DSLAM.



TBH, my thinking aloud included a somewhat veiled 'hint' that someone with maybe a Planet VC230N for the VDSL2 element & a real live ADSL connection (possibly even provided via TalkTalk) may be willing to use their ADSL connection as the temporary donor for the other element of any such experimentation  ;)


BTW, the word "differingent" as used in my previous message was an accidental Eagleism - an example of multi-tasking at its worst  :-[

Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: burakkucat on September 07, 2014, 11:20:47 PM
I am gradually compiling a list of experiments to perform:
For each experiment I propose to attach the raw harvested ASCII text as a ZIP format file and, hopefully Mr Eagle will be able to provide the corresponding snap-shot graph montages.

I am hoping that the six different local loop lengths of experiment no. 6 will show a linear relationship and, perhaps, provide something that could then be extrapolated to "real" VDSL2 circuit parameters.

As I do not own a pair of crimping pliers and a tub of gel-crimps, I propose to make all the joints via "chocolate block" screw terminals. Each end of the loop will be fitted with an LJU2/3A (using IDCs) and a pair of RJ11 to 431A cables will connect the VC-230N & the HG612 devices to the circuit.
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: burakkucat on September 09, 2014, 08:53:54 PM
Adding some further information, before I begin the testing, so that those interested can comment, etc.

I have now defined three separate configurations for the VC-230N:
(Three screen-scrapes are attached, below.)

According to a specification sheet for CW1308 cable, each conductor should not exceed 97.8 Ohms/km. My tests show that the spool 1 cable conductors have a resistance of 90.8 Ohm/km and that the spool 2 cable conductors have a resistance of 87.1 Ohms/km.

My next consideration is how to serially connect the pairs for the experiments using the Openreach mimic configuration. I have thought about two different methods. For the following descriptions, I need to define the abbreviations used:

NE -- near end (the outer end of the cable on the spool).
FE -- far end (the inner end of the cable on the spool).
S1 -- spool one.
S2 -- spool two.
B -- blue pair (blue/white stripe & white/blue stripe).
O -- orange pair (orange/white stripe & white/orange stripe).
G -- green pair (green/white stripe & white/green stripe).
LJU2/3A -- Line jack unit with IDCs (secondary).

The first method of connection:

LJU2/3A to NE,S1,B
FE,S1,B to NE,S2,B
FE,S2,B to FE,S2,O
NE,S2,O to FE,S1,O
NE,S1,O to NE,S1,G
FE,S1,G to NE,S2,G
FE,S2,G to LJU2/3A

The second method of connection:

LJU2/3A to NE,S1,B
FE,S1,B TO FE,S1,O
NE,S1,O to NE,S1,G
FE,S1,G to NE,S2,G
FE,S2,G to FE,S2,O
NE,S2,O to NE,S2,B
FE,S2,B to LJU2/3A

For simplicity of connecting the pairs, I plan to use the first option. Any comments or observations, please?
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: konrado5 on September 09, 2014, 09:17:11 PM
I'm curious of SNR margin graph and errors on fast path. :)

Best regards
konrado5
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: burakkucat on September 09, 2014, 11:41:46 PM
I'm curious of SNR margin graph and errors on fast path. :)

I assumed that you would be interested to see how far I can "push" the test circuit. Hence I named the second configuration (fast path, zero target SNRM, no DS or US rate limit) in your honour!  ;D
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: NewtronStar on September 10, 2014, 12:40:45 AM
I would like to see your experiments converted to dslstats or HG612_Modem_stats graphs as thats the only reference we have as the JDSU 3000 is kind of expensive  :blush:
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: burakkucat on September 10, 2014, 01:47:19 PM
Assuming Bald_Eagle1 is agreeable and willing to assist, my intention is to provide a montage of the snapshot data and the full, raw harvested data as a ZIP format image of the ASCII text file.  :)
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: Bald_Eagle1 on September 10, 2014, 07:43:46 PM
Of course I'm agreeable.

Whenever you are ready, my furry fiend (not a typo)  :P

Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: burakkucat on September 11, 2014, 11:39:57 PM
I have been giving some further thought as to how I could connect together the three pairs on both spools of cable. Once again, I will define the abbreviations I shall use:

NE -- near end (the outer end of the cable on the spool).
FE -- far end (the inner end of the cable on the spool).
S1 -- spool one.
S2 -- spool two.
B -- blue pair (blue/white stripe & white/blue stripe).
O -- orange pair (orange/white stripe & white/orange stripe).
G -- green pair (green/white stripe & white/green stripe).
LJU2/3A -- Line jack unit with IDCs (secondary).

The third method of connection:

LJU2/3A to NE,S1,B
FE,S1,B to NE,S2,B
FE,S2,B to NE,S1,O
FE,S1,O to NE,S2,O
FE,S2,O to NE,S1,G
FE,S1,G to NE,S2,G
FE,S2,G to LJU2/3A

Of the three methods, I prefer the third because the "direction of travel" of the signal through the spools of cable is always in the same direction.
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: burakkucat on September 24, 2014, 12:58:37 AM
I present the results obtained when performing an experiment with the Planet VC-230N in the Konrado configuration. This just defines the absolute maximum limit to which the equipment can be "pushed".

The local loop length was 1.5 metres. The VC-230N was configured in fastpath mode, the target SNRM was set at 0 dB and no rate capping was applied.

Attached below is an image of the VC-230N configuration screen, the portrait montage (with thanks to Bald_Eagle1 for plotting the data) and the raw data harvested from the HG612.
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: burakkucat on September 24, 2014, 01:19:11 AM
I present the results obtained when performing the Ronski series of experiments with the Planet VC-230N in (what I term) the basic configuration. The aim of these experiments is to see if there is any degree of "self interference" when using all three pairs of each spool, serially.

Experiment 1

The local loop length was 211 metres, which consisted of the blue pair of spool 1 (103 metres) and the blue pair of spool 2 (108 metres) in series.

The VC-230N was configured in interleaved mode, the target SNRM was set at 6 dB and no rate capping was applied.

Attached below is an image of the VC-230N configuration screen, the portrait montage and the raw data harvested from the HG612.
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: burakkucat on September 24, 2014, 01:23:53 AM
Experiment 2

The local loop length was 206 metres, which consisted of the blue pair of spool 1 (103 metres) and the orange pair of spool 1 (103 metres) in series.

The VC-230N was configured in interleaved mode, the target SNRM was set at 6 dB and no rate capping was applied.

Attached below is an image of the VC-230N configuration screen, the portrait montage and the raw data harvested from the HG612.
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: burakkucat on September 24, 2014, 01:27:28 AM
Experiment 3

The local loop length was 216 metres, which consisted of the blue pair of spool 2 (108 metres) and the orange pair of spool 2 (108 metres) in series.

The VC-230N was configured in interleaved mode, the target SNRM was set at 6 dB and no rate capping was applied.

Attached below is an image of the VC-230N configuration screen, the portrait montage and the raw data harvested from the HG612.
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: burakkucat on September 24, 2014, 01:41:56 AM
The Ronski series of experiments clearly show that there is a significant degree of coupling at the higher frequencies and, thus, self-interference between the pairs.  :o

As of yet, I have not performed any further tests.

Unless someone can convince me otherwise, I intend to use the third method of connection of the pairs (see my post of September 11, 2014, 23:39:57, above) when testing with the Planet VC-230N in (what I term) the Openreach mimic configuration.  :-\
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: burakkucat on October 18, 2014, 11:36:37 PM
I performed the experiments, collected the data, passed that same data to the expert Eagle, received graphical plots in return and promptly forgot to post the results to this thread!  :paperbag: 

To recap I have presented results, above, obtained by performing an experiment using the Konrado configuration ("pushing" the circuit as far as is possible) and three tests using the Basic Configuration, suggested by Ronski, which shows that there is significant self-interfering cross-talk (for which a new abbreviation, SIXT, has just been created) when the same signal is sent through two (or more pairs) within the same cable binder.

This last sequence of seven experiments were performed using an Openreach Mimic Configuration, as shown in the first image below.

In each of the seven experiments both the Planet VC-230N and the Huawei HG612 were connected by identical leads with RJ11 & 431A plugs at each end. When I mention the length of the local loop, it does not include the lengths of those two leads, only the the length of the circuit between the two 431A plugs.

The local loop was gradually built up from a length of 0 metres to a length of 633 metres, using connections as detailed in my my post of September 11, 2014, 23:39:57, above.



Experiment 1.

Local loop length: 0 metres.

Attached is the raw data (as a ZIP format file) and the portrait montage.
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: burakkucat on October 18, 2014, 11:38:44 PM
Experiment 2.

Local loop length: 103 metres.
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: burakkucat on October 18, 2014, 11:40:01 PM
Experiment 3.

Local loop length: 211 metres.
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: burakkucat on October 18, 2014, 11:41:25 PM
Experiment 4.

Local loop length: 314 metres.
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: burakkucat on October 18, 2014, 11:48:09 PM
Experiment 5.

Local loop length: 422 metres.
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: burakkucat on October 18, 2014, 11:49:52 PM
Experiment 6.

Local loop length: 525 metres.
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: burakkucat on October 18, 2014, 11:51:13 PM
Experiment 7.

Local loop length: 633 metres.
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: Chrysalis on October 19, 2014, 06:03:01 AM
interesting that my attenuation and pre crosstalk stats were similar to your 300m tests.

can you test adding QLN to emulate crosstalk?
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: burakkucat on October 19, 2014, 03:52:03 PM
Sorry Chrys but I'm not sure I understand exactly what it is that you are asking.  :-\

My test with a (103 + 108 + 103) metres (314 metres) local loop was the first to show SIXT as the circuit pathway consisted of --
The SIXT was occurring between the blue and orange pair within spool 1.

If I had three spools (of nominally 100 metres) I could then mimic the attenuation of your circuit. I would then require a second pair of devices (CO & CPE) connected via a second pair through that (nominally) 300 metres local loop cable which would then provide the required cross-talk. (NEXT and/or FEXT.) Such testing would really require usage of a DSLAM/MSAN -- something that Asbokid could do with his Huawei SmartAX MA5616
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: burakkucat on October 19, 2014, 04:16:55 PM
There is one further experiment that I could perform with the equipment that I have available.  :)

That is to set up a (103 + 108) metres (211 metres) local loop and connect a Rheostat No 1A in series with one leg of the loop. The rheostat has a range of 0 - 9999 Ohms (10000 Ohms range) and by gradually increasing the resistance, mimic the appearance of a resistive fault within the circuit.

To harvest results at every one Ohm would be an impossible task (10000 experiments); likewise harvesting results at every 10 Ohms (1000 experiments) or 100 Ohms (100 experiments).

However harvesting results at every 1000 Ohms (10 experiments) would be a feasible task . . . Perhaps I should perform a few preliminary experiments to see how the circuit behaves. Hmm . . . Use inserted resistances of 0, 1, 10, 100, 1000, 9999 Ohms to get a "feel" for the circuit's response and then plan a more extensive experimental sequence based on the preliminary results.

Input and suggestions from interested kitizens will be appreciated.
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: les-70 on October 19, 2014, 04:49:43 PM
  From a quick glance I think each of the Hlogs other than from the test with the shortest length cable shows significant reflections from one end of the cable to the other.  The frequency difference between the dips in Hlog looks to correspond to a wavelength close to each of the respective cable lengths.  This may be a mismatch between the devices or bad joint.  This probably makes the results a bit pessimistic.  I think Asbo used baluns avoid something like this.
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: burakkucat on November 13, 2014, 12:40:12 AM
The set of six experiments as detailed in my reply #33, above, has now been performed.

Experiment 1.

Inserted resistance: 0 Ohms
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: burakkucat on November 13, 2014, 12:42:33 AM
Experiment 2.

Inserted resistance: 1 Ohms
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: burakkucat on November 13, 2014, 12:44:02 AM
Experiment 3.

Inserted resistance: 10 Ohms
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: burakkucat on November 13, 2014, 12:45:48 AM
Experiment 4.

Inserted resistance: 100 Ohms
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: burakkucat on November 13, 2014, 12:46:58 AM
Experiment 5.

Inserted resistance: 1000 Ohms
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: burakkucat on November 13, 2014, 12:48:42 AM
Experiment 6.

Inserted resistance: 9999 Ohms (We could really consider this as 10000 Ohms, for simplicity.)
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: burakkucat on November 13, 2014, 01:00:42 AM
Once again I would like to acknowledge the assistance of Bald_Eagle1 in producing the relevant graphs from the raw data harvests. If anyone noticed a sudden heavy flurry of electrons flowing between The Cattery & The Eagle's Nest and then in the return direction, the graphs displayed above are the end result.  :)

I cannot think of any other experiments that I could perform with the facilities that I have available. So I hope all of the above results will provide the data for other Kitizens to analyse and then share.  ;)
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: tickmike on November 16, 2014, 02:17:20 PM
Interesting  :).
Can you do any diagrams of your tests ? when you are not Cat napping   :blush:
If I can find it, I have /had a HR crimp joint of my line from some years ago, I can not remember how much wires are coming out of it, if there is enough to get my meter on it I will measure what the resistance is  ;).
Title: Re: HG612 Firmware [August 2014] -- A "Test Run"
Post by: burakkucat on November 16, 2014, 04:54:56 PM
Michael -- The circuit for the last six experiments was quite straightforward.

It consisted of the two spools of CW1308 cable (103 metres and 108 metres), an LJU2/3A at each end of the 211 metres length, one wire of the selected pair from each cable firmly connected via a "chocolate block" screw connector and the other wire of the selected pair attached to the terminals of the Rheostat No. 1A.

The Planet VC-230N (acting as a one port DSLAM) was connected to one of the LJU2/3As via a standard RJ11 plug to 431A plug lead and the Huawei 612 (the CPE) was connected to the other LJU2/3A via a similar RJ11 plug to 431A plug lead.

Thank you for offering to attempt to measure the resistance across that defective crimped joint. If measurement is possible, it would then give us an idea of the typical sort of resistance that such a failed joint could add to a circuit.  :)