Meridian Unplugged - Powered by MrTechGuy.co.uk Forums Discussion Meridian - Systems 861v4 Fetch Issues

Morning All,

I am trying to connect my 861v4 via a new USB adaptor to my Laptop so I can run the MConfig and am having some issues. Really hope you can help?

Here is what I do:

Connect 861v4 to Windows 7 Laptop via USB adaptor (EasySync). Run the Meridian Configuration Program and the fetch comes back straight away saying: "There is a Meridian 861v4 connected to COM3, Do you wish to fetch from the 861v4 now?" I click 'Yes'. It then says: there is a Meridian 861v4 connected to USB1, Do you wish to fetch from the 861v4 now? I click 'Yes' again. The Fetch then states: "Please ensure that a serial cable is connected from USB1 on your Computer to the product. when you are ready click Start." I click Start. the 861 then starts blinking on the display for about 5-10 seconds and I get the following errors from the Fetch: "Failure during directory read. Failed to reset product. Failed to reset Product and Fetch Failed."

I have tried physically powering off the 861v4, trying different USB ports on the laptop and I get the same results. It is strange as it is seeing the 861v4 but not doing the fetch.

The version of the Config software is: V3.07 build 3495.

Any help would be great guys.

All the best,
G

Have you tried assigning a different COM port to the USB adaptor and then setting Mconfig to use this? There is a potential conflict in the ports.

What happens if you say "No" to the fetch and ask the 861 to identify itself? Fetch is pretty useless anyway.

Hi Malcolm,

How do I assign a different Comm Port? Sorry, I am being seriously useless today.

Cheers
G

Hi Malcolm,

If I ignore the Fetch and do an 'Identify' it returns details fo my 861. But I still do not know how to configure it as the Fetch still fails. Bizarre huh?

Malcolm,

You are a superstar! The identify found it and then I changed the port from USB to Com 3 and it has now found my info! Thank you so much.

A beer is here if you are ever in my neck of the woods.

Thanks so much
G

Glad you got things sorted, I had a similar issue with my G68 in that M use a FTDI USB-Serial host in their processors if I'm not mistaken AND so do lots of embedded evaluation boards - consequently Windows was getting confused (25 years and they still haven't fixed all the old bugs, just made new ones) about what device I had actually connected.

EDIT: Meant to say that it's highly likely your USB serial adaptor uses the same chipset, thus confusing the hell out of MConfig.