Unitiqute Software Update!

You could try not powering Qute oft then on during the update; leave it on as it already has an established IP address. This power cycle step ensures device is in a known state, but may be delays in establishing the IP address are showing up as a time-out error. Wired Ethernet is best here for sure btw. 

Regards alan

Thankyou Alan, yes everything is hard wired for this update. The qute is in my office for this update. With it installed in the living room I use Homeplugs but for this their out of the equation.

I tried the procedure as you suggested and no communication at all happens, the Product Model is not even picked up. I get the message to 'Check Connections'!. But worse still when I go back and try again the software hangs and I have to Force quit and restart the Mac, oh dear. Doesn't inspire confidence does it.

I wish the qute would tell me that the serial connection was good, or I had some way of testing that. The drivers download and install but I have no equipment now to check an RS232.

Thanks again for the suggestion.

Malcolm

It's very difficult to know where the problem may be. I'm not familiar with using a Mac for this but if it were a PC then I know you sometimes have to leave time for the drivers to get loaded in the PC, which only happens when they are needed.

So I wonder about doing it in this order. Start the Mac but not yet the updater. With the UQ off,  connect the USB lead. Wait a couple of minutes, then start the UQ and once it has fully started, start the updater programme. Don't go thro the on off power cycle of the UQ (as you know it's in a freshly started state).

best

David

Have you installed a correct driver? If you are using a USB to Mini-USB B cable then the driver will be listed as CP2101 USB to UART Bridge controller (and in the Streamer Updater it will be listed as SLAB_USBtoUART).

Adam

Adam - have a look at the initial post. A 232 port is being used, and the dropdown says 'usbserial'. I don't know if that's right. With my USB port on the 272 the dropdown says 'COM3', but what should it say with a 232 socket on the streamer?

Hungryhalibut posted:

Adam - have a look at the initial post. A 232 port is being used, and the dropdown says 'usbserial'. I don't know if that's right. With my USB port on the 272 the dropdown says 'COM3', but what should it say with a 232 socket on the streamer?

And the OP is using a Mac not a PC.....

That's true..... do we know if the mac saying 'usbserial' means that the driver is ok? If so we can forget about that. The fact that Naim said it's a network issue suggests that the driver is correctly installed. Maybe?

I don't know.

But if the UQ is getting an IP address then this isn't being reported to the updater via the USB lead so I wonder whether a factory reset of the UQ might help.

Also when the OP tried connecting just the UQ to the home hub, I hope he did have the Mac still connected to the router because it does need to be to be able to deliver all of the firmware update. (Some of it goes over the USB and some via the Ethernet.)

Best

David

The OS will identify the driver as /dev/etc/*, but what the Mac UI reinterprets this as, or displays is anybody's guess.  It sounds as though it's displaying the "friendly name" not the driver name, so it could vary from one driver to another (e.g. from different suppliers).

M Hendra posted:

 

After some seconds the device UnitiQute is picked up. But it fails to find an IP address and asks me to manually enter, which I do, its: 192.168.1.86 but I get no further.

 

What fails to find an IP address, and an IP address for what?

The Updater software?
The UQ?
The serial converter (it shouldn't need one)

How do you know 192.168.1.86 is correct?  It's very unusual to have 84 devices on a home network.

I had a similar problem with an HDX update, using a Mac.

I had downloaded the correct usb driver per Naim's instructions, but, with the Mac hooked up with the USB to RS232 cable, the driver did not appear for selection on the drop down list of drivers installed.

I gave up eventually, and visited my local dealer, who carried out the update............using a Windoze machine, so I can only guess that the problem lies within Naim's update procedure for Mac.

Thankyou for your comments everyone.

Just to be clear, I am on a Mac and I have a UQ with an RS232 port.

My serial cable from Ugreen has the Prolific PL2303 chipset. When I installed the driver on the cd that came with the lead I got nothing in the drop down list provided by the Naim Updater. I then went onto the prolific website, downloaded the drivers for my OS (Yosemite) and loaded. I then got 'usbserial' as a port option.

I spoke to a naim rep regarding this and he set up a remote session with my computer. He proceeded to do all that I had done. He was happy with the 'usbserial' port option.

It would appear that the recycle of the UQ is required because it is only during the power up stage of the UQ that it attempts comms with the serial port. I'm guessing, I may be wrong but when I do that the next page tells me that the Product Model is a Uniti Qute, if I dont recycle I get nothing, it times out and tells me to check connections. The naim rep implied that because a product model was found the serial comms was ok.

So, when I recycle, get onto the next page, the Product Model is shown but it times out on the IP address. I can see the IP address on the UQ. I have been using the streamer for years. But naim say there is a problem with my network but cant tell me what.

I feel a trip to Doug Brady is imminent!

Thanks again everyone

Malcolm

The updater needs to find the IP address of the streamer or it cannot proceed. 

The OP could try installing the Fing app on an iPad. It will search the network and identify all the IP addresses if there is any doubt about the 86. 

I've done loads of updates as part of the beta group and always use the laptop wirelessly, with the Naim wired. It's never gone wrong yet. So if the Qute is connected with a wire to the router (and it can access the Internet, which can be checked using iradio) and the mac is also connected, wired or wirelessly, there should not be scope for any network issues. 

HH, he could be using static IPs without setting a static range in the DHCP server config, or he could have a LOT of dynamic IPs on the network, so the power cycle changes the IP address of the UQ (a power cycle can sometimes terminate the lease).  Without more info about his network we're blundering around blindly in the dark.

Just to chip in - I use my Macbook. During updates all 4 of my streamers were connected via USB-miniUSB to a laptop. All 4 streamers are hard-wired to the switch.

Following Naim manual on updates I never had any problems loading new firmware. 

So the question is: are there any non-standard network settings on OP's home network which cause this rather automatic process to fail?

Adam, wrt your last point, there must be a non-standard configuration to get an IP address of 192.168.1.86 !

My network:

Im connected to a BT Home Hub 3. I know nothing about static or dynamic addresses. The only thing I had to do to get it all working (from what I can remember) was to put my time capsule in bridge mode (DHCP off). I can get into the BT home hub and look at the addresses and options and so on. A DHCP range has been set up from 192.168.1.64 to 192.168.1.253. it tells me this is the default. You can configure this manually.

I can look at the DHCP table and look at details for each equipment connected. Within the detail there is an option 'Always Use this IP address' this is set to 'Yes'. Does that mean my IP addresses are static, is this a problem.

Like I said before this has been working for years

Id agree with Adam, this should be a fairly automatic process but unlike him I have an RS232 port on my UQ

So HH I can see all my addresses and all looks well (I tried to post a snapshot of the DHCP list but will have to investigate how to post an image). I can confirm the UQ is connected to the internet and I can receive iRadio.

Yes Dave Ive almost given up, Doug Brady beckons

HUGE, I'm inclined to agree with you regarding the 'friendly' serial. Dont know how to verify that??. I may uninstall th driver and connect the cable and see what happens.

Thanks everyone, this is getting complicated. Ive connected cameras and Sat Navs before and it just works!!

Malcolm

Huge, are you suggesting I change the default in my home hub. ....64 to ....253.

Huge posted:

How do you know 192.168.1.86 is correct?  It's very unusual to have 84 devices on a home network.

BT hubs assign IP addresses between  192.168.1.64 to 192.168.1.253,  so 80 something is not that far out, plus my old HH5 Type-B didn't assign sequencially & it frequently went in the 100's.    My latest Type-A does assign sequentially   

Whatever the hub & all the audio needs to be reset to DHCP,  then do a full power cycle on everything,  all off, hub back on first & let it finish its process,   then the Naim & the control point & it should be OK.  

If the Qute has an IP address and is working (you say iRadio works?) then I think there's no issue there. I can see no reason to use a fixed IP address for the Qute, and would be tempted to uncheck that option on the router and use DHCP for everything, but I can't see how that affects the current problem. 

I don't know much about homeplugs, but I wonder if moving the Qute from a home plug location to a regular wired Ethernet connection is causing confusion? Does the Qute work OK in either location?

Mike-B posted:

Huge posted:

How do you know 192.168.1.86 is correct?  It's very unusual to have 84 devices on a home network.

BT hubs assign IP addresses between  192.168.1.64 to 192.168.1.253,  so 80 something is not that far out, plus my old HH5 Type-B didn't assign sequencially & it frequently went in the 100's.    My latest Type-A does assign sequentially   

Whatever the hub & all the audio needs to be reset to DHCP,  then do a full power cycle on everything,  all off, hub back on first & let it finish its process,   then the Naim & the control point & it should be OK.  

 

'it should be ok'. Ha ha, this is computer stuff we are talking about. But yes, it should. The IP 86 is perfectly fine. I'd go to Doug Brady if it were me. 

Hi -

The usbserial driver is likely fine, as you downloaded the new "signed" one for your OS and since the updated reports a UnitiQute. 

The IP address is likely a "reserved" DHCP address, issued by the router but not a static IO. This is also fine (and convenient). 

Can you try running the updater but quitting after it has found the USB port, then without turning power off or disconnecting either the USB or the serial cable, check that you have an IP address assigned (use the IR handset and scroll in settings or set the input to an internet radio station or look in your router at the connected devices page). 

Then you can re-start the update knowing both the USB and Ethernet connections are alive. Skip the power cycle step this time and see what happens. 

Ive not updated my Qute v1 for some time, and last time it was during an unfortunate era when there were no signed drivers for the USB to serial cable converters so it was a lot of gagging about in the OS. You don't seem to be experiencing that, so perhaps it is just "slow" to get all the connections up and running, causing the time out when you cycle power during the update. That is the step I'm suggesting that you try to skip. 

Regards alan

M Hendra posted:

 

My network:

Im connected to a BT Home Hub 3. I know nothing about static or dynamic addresses. The only thing I had to do to get it all working (from what I can remember) was to put my time capsule in bridge mode (DHCP off). I can get into the BT home hub and look at the addresses and options and so on. A DHCP range has been set up from 192.168.1.64 to 192.168.1.253. it tells me this is the default. You can configure this manually.

I can look at the DHCP table and look at details for each equipment connected. Within the detail there is an option 'Always Use this IP address' this is set to 'Yes'. Does that mean my IP addresses are static, is this a problem.

Like I said before this has been working for years

Id agree with Adam, this should be a fairly automatic process but unlike him I have an RS232 port on my UQ

So HH I can see all my addresses and all looks well (I tried to post a snapshot of the DHCP list but will have to investigate how to post an image). I can confirm the UQ is connected to the internet and I can receive iRadio.

Yes Dave Ive almost given up, Doug Brady beckons

HUGE, I'm inclined to agree with you regarding the 'friendly' serial. Dont know how to verify that??. I may uninstall th driver and connect the cable and see what happens.

Thanks everyone, this is getting complicated. Ive connected cameras and Sat Navs before and it just works!!

Malcolm

I don't think the RS232 vs mini-USB matters that much here.

However I did spot an improvement opportunity: you mention you already have TimeCapsule (so in essence Apple Airport Extreme). This is a very user friendly and reliable way to build a home network.

My suggestion would be to rebuild your entire network in the following manner:

BT Home Hub > Lan cable to TimeCapsule.
TimeCapsule not in a bridge mode, but in a full network mode. If possible switch the WiFi on your BTHome Hub and use it only as a modem.

If you have a switch, connect the LAN output from your TimeCapsule to your switch, and the rest of the wired devices to the switch.

This way TimeCapsule will define your new WiFi network. Managing it will be much simpler too. I do realise there will be some initial work, reconfiguring the other devices to run on the new network. But the end game is worth it. I've been running Apple network at home for many years now. The only challenge came this year, when my old TimeCapsule died (hard drive failure). 

If you need a network extender, just get a cheap Airprot Express.

Huge posted:

Adam, wrt your last point, there must be a non-standard configuration to get an IP address of 192.168.1.86 !

Huge -why so? This sounds totally proper and potentially completely standard as long as its within the network address subnet i.e. 192.16.8.1.0 /24  and the DHCP scope range.

Not all DHCP severs will number sequentially and there is a line of thought that says there is some advantage not to reassign a recently used address for a extended further period pf time if possible - but anyway the DHCP address assignment is arbitrary as long as its within the scope range for that subnet and not being actively used by a host on the network.

S

...one other thing is to try first updating to 3.12 or 3.17 or some "high-ish" version in the 3.xx series. I know the Naim guy told you to go straight to the latest 4.x but I seem to recall that when I first started updating (it was still in the 3.x's and I was also on 3.0) that the advice was to first go to an intermediate version, then go up regularly by each new release. Nothing to lose but a little time if you try that. Maybe useless if the new updater software is agnostic, I don't know  

Best wishes. It used to be a ton of fuss and stress and worry about bricking things; it is really much better now and that's why folks are having an issue helping from experience!

rrgards alan

ps - the suggestion to use the Airpot as a router to create a tiny, stand alone network for only your Mac and your Qute is a good one. Disconnect it from your home hub, turn on DHCP, wire both your mac and Qute and see if they are all happy, then give it a whirl. 

Adam Zielinski posted:

M Hendra posted:

 

My network:

Im connected to a BT Home Hub 3. I know nothing about static or dynamic addresses. The only thing I had to do to get it all working (from what I can remember) was to put my time capsule in bridge mode (DHCP off). I can get into the BT home hub and look at the addresses and options and so on. A DHCP range has been set up from 192.168.1.64 to 192.168.1.253. it tells me this is the default. You can configure this manually.

I can look at the DHCP table and look at details for each equipment connected. Within the detail there is an option 'Always Use this IP address' this is set to 'Yes'. Does that mean my IP addresses are static, is this a problem.

Like I said before this has been working for years

Id agree with Adam, this should be a fairly automatic process but unlike him I have an RS232 port on my UQ

So HH I can see all my addresses and all looks well (I tried to post a snapshot of the DHCP list but will have to investigate how to post an image). I can confirm the UQ is connected to the internet and I can receive iRadio.

Yes Dave Ive almost given up, Doug Brady beckons

HUGE, I'm inclined to agree with you regarding the 'friendly' serial. Dont know how to verify that??. I may uninstall th driver and connect the cable and see what happens.

Thanks everyone, this is getting complicated. Ive connected cameras and Sat Navs before and it just works!!

Malcolm

I don't think the RS232 vs mini-USB matters that much here.

However I did spot an improvement opportunity: you mention you already have TimeCapsule (so in essence Apple Airport Extreme). This is a very user friendly and reliable way to build a home network.

My suggestion would be to rebuild your entire network in the following manner:

BT Home Hub > Lan cable to TimeCapsule.
TimeCapsule not in a bridge mode, but in a full network mode. If possible switch the WiFi on your BTHome Hub and use it only as a modem.

If you have a switch, connect the LAN output from your TimeCapsule to your switch, and the rest of the wired devices to the switch.

This way TimeCapsule will define your new WiFi network. Managing it will be much simpler too. I do realise there will be some initial work, reconfiguring the other devices to run on the new network. But the end game is worth it. I've been running Apple network at home for many years now. The only challenge came this year, when my old TimeCapsule died (hard drive failure). 

If you need a network extender, just get a cheap Airprot Express.

Just to say that my own experience of trying to use an Apple TimeCapsule as a router in place of the one supplied by my ISP was wholly unsatisfactory. In particular the 5 GHz wifi network didn't work well with my Apple devices (both of which support 5GHz and one of those being 892.11ac). Subsequently I got a new hub from my ISP and now regularly get 150 Mbps to the same iPad, as compared with about 4Mbps when I was using the TimeCapsule). I know others have had better success but personally I don't think it's a given that Apple Extreme-based products always work as well as expected.

So I suggest not complicating things until the firmware update is resolved.

best

David