Skip to content
HearingTracker
Log in

Connexx 9 software, where to get

711 replies37k viewsLast reply

Jump
Link to this topic
Reply

Welcome to the forum, great your giving a go, it’s all pretty easy enough to do, plus Connexx software is very easy to navigate, you’ll need the Noahlink wireless programming device for any DIY projects tho.

Hello all,

I’m new to the diy hearing aid idea but have ordered a Noahlink to give it a go. I have a copy of ReSound Smartfit for my every day units but would like the Connexx software for my Signia Silks. Can any one help me out please.

Steve

Welcome to the forum, great your giving a go, which Silk models, as you’ll need different programmer, connexxAir wireless or a HiPro and cables.

Welcome to the forum, great your giving a go, do read the user guides as it’s very helpful for setting up the first time, and don’t forget you’ll need the Noahlink wireless programming device for your DIY projects.

For the general users:

After spending a bunch of time trying to work around the error, I finally arrived at an answer…it’s not an answer that I’m necessarily happy with, but it’s an answer.

The short story is I have too beefy of a computer for the software to handle.

The long answer is error code 0x80070643 is thrown by the first MSI file to be installed (Programmer) when it calls a custom function in the MSI handler. The specific exception thrown is System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> System.OverflowException: Value was either too large or too small for a UInt16.
at System.Convert.ToUInt16(Int32 value)
at SHS..Fitting.Inst.CustomActions.BusinessLogic.FrameworkBL.GetTotalMemoryInGigaBytes()
at SHS.SAT.Fitting.Inst.CustomActions.BusinessLogic.FrameworkBL.CheckSystemRam()
at SHS.SAT.Fitting.Inst.CustomActions.BusinessLogic.FrameworkBL.CheckRequirements()
at SHS.SAT.Fitting.Inst.CustomActions.CustomActions.FrameworkCA.CheckRequirements(Session session)
— End of inner exception stack trace —
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object parameters, Object arguments)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object parameters, CultureInfo culture)
at Microsoft.Deployment.WindowsInstaller.CustomActionProxy.InvokeCustomAction(Int32 sessionHandle, String entryPoint, IntPtr remotingDelegatePtr)
CustomAction CheckRequirements returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

Although this system is my older (by about 5 years) Windows Desktop, I did upgrade the RAM to around 96GB. Free space on drives is fine (68GB on the main drive, compressed). And I tried running the installer on my newer system (128GB machine with zero space issues). Bottom line if I understand it correctly is that the code developer for the Signia Connexx software is not anticipating that the software will be installed on a beast like I own.

Looks like I (literally) need to dust off my 9 year old machine that I can’t upgrade to Windows 11 and see if it will install there…

Edited

Confirmed. The method the programmer is trying to use (System.Convert.ToUInt16) can only take an unsigned integer value under 65535. My system currently would attempt to express a value of 81838, thus throwing the error.

Bottom line, if you have a system with greater than 64GB of RAM, the connexx software will fail to install.

In reply to @tenkan

I thank you very much for the help! I was just able to purchase the Noahlink to program the hearing aids. I am now getting familiar with the software and have watched many videos of how it is used. The doubt I have is that the hearing aids she has are Pure Primax 7PX but in the software several items appear with this model, for example. Pure 7px S (108/45), another Pure 7px M (119/60). I don’t realize what the model is and what the other letter and what is in parentheses mean.
Thank you very much again for your help!

signia

Edited

it depends what receiver type is connected to the hearing aid.
check on the receiver , if you can find the imprinted power level
S = Smal , M = Medium , P = Power , HP = High Power

S → S receiver with Peak OSPL () 108 / 45 Peak Gain ()
M → M receiver with Peak OSPL (db ) 119 / 60 Peak Gain (dB)
P → P receiver with Peak OSPL (db SPL) 124 / 70 Peak Gain (dB)
HP → HP receiver with Peak OSPL (db SPL) 130 / 75 Peak Gain (dB)

Output Sound Pressure Level (OSPL)

Output Sound Pressure Level 90 (OSPL90) is the output saturation sound level (SSPL) to a 90dB sound input and is measured over a frequency range. This is also called SSPL90. 90dB sound is very loud, equivalent to sound generated by a lawnmower or screaming child.

Signia Primax PX platform is generation 2016 , see list of Signia hearing aid platforms3

In reply to @MartinQ

Yeah as has already been stated, just one other thing is once connected to the software it automatically generates which models are connected, so you won’t have to choose, just be sure to make your client up and then connect, the Noahlink wireless won’t be any good for Primax platform as its only the NX platform onwards, should be connexxAir for the older models.

Hi there, yeah that’s unfortunate it won’t, but no problem I’m sure you’ll be up and programming in no time.

Welcome to the forum, great your giving a go, it’s all pretty easy enough and Connexx is pretty easy to navigate, yes you’ll need any version Noahlink wireless will be fine.

Welcome to the forum, great your trying , as it’s for someone else be sure to read the user guides before starting, it’s all pretty easy enough tho, and you’ll also need the Noahlink wireless programming device.

Welcome to the forum, great your giving a go, it’s all pretty easy enough but do read the user guides as it’s very helpful for setting up the first time, don’t forget the Noahlink wireless programming device.

Related discussions