I allowed a windows 10 laptop to setup usb drivers and powered up the Minitiouner. Running TestMyMinitiouner (latest) fails completely. Am I looking for hardware or software failure?
Mini Test gives:
D2XX test -OK Device Present... NIM : ?????
DLL version: 3.2.14
we have found 2 device (s)
device named: FT2232H MiniModule A
device named: FT2232H MiniModule B
>>>>>>>>>> NO MiniTiouner connected to USB MASTER!
>>>>>>>>>> NO MiniTiouner-Pro connected to USB AUX!
Can you post screen shots after starting TestMyMiniTiouner_V2_0a, after clicking I2C Master init (NIM) and after clicking Test NIM.
I think your problem is that the FT2232 USB module has lost it's configuration?
See how your device names do not contain NIM in their names.
I have attached a snapshot from my TestMyMiniTiouner_V2_0a..
See how the difference in the device names found in my snapshot, attached.
On on the BATC wiki page, there's a link to the instructions for instaling the FTProg module programming software and the template XML file to apply, once you have the FTProg software installed.
- NIMTest.png (61.45 KiB) Viewed 1592 times
Do you have a DigiLite board attached to your system?
If you do, then that's where the "FT2232H MiniModule" device name is coming from..
I have tested this myself, TestMyMiniTiouner_V2_0a reports the same as yours, with only a DigiLite board connected..
I also tested with a MiniTiouner and a DigiLite board connected, TestMyMiniTiouner_V2_0a reports four devices & seems select the correct devices when running the NIM tests.
So I think that if you do also have a DigiLite board connected, then your MiniTiouner has a cable or hardware fault?
Expect that you should see four devices configured, same as mine?
What do you see when you run TestMyMiniTiouner_V2_0a with _only_ your MiniTiouner connected?
If you still see "FT2232H MiniModule" device names, then I think your FT2232H module needs reprogramming?
- With DigiLite module only.
- NIMTest2_DL_Only.png (45.12 KiB) Viewed 1569 times
- With DigiLite and NIM Tuner attached.
- NIMTest2.png (61.23 KiB) Viewed 1569 times
But if it can't find the minitiouner, then there might be several reasons. The first is bad USB cables which can so often cause the detection problems. Ones that come from Ebay only intended for charging are prime examples. They will not work, or work very poorly.
The FT module from BATC should have been pre-programmed. They don't normally just forget what they are. If it is not programmed (e.g obtained from elsewhere) you will need to use FT Prog and follow the instructions on the Wiki. It's not difficult.
I still think there is a possibility of a communication problem with the NIM. This can be caused by a problem on the I2C communication bus due to a bad socket, an unsoldered pin, a short or wrong value resistor terminating the bus, or power supply problem. There must have been over a hundred built by now so most issues will have come to light. Time for a troubleshooting guide maybe.
It is built as the basic v2 board as per the instructions, no digilite or other add-ons. Supplies all checked and re-checked ok. I now wish that I had used sockets for the NIM rather than soldering, although this can cause other problems. The usb cable is the newer version from Lindy. I will try the FTprog method first, if the NIM is faulty I doubt the board will survive its removal.
I am reticent to condemn your NIM at this point, as Brian G4EWJ pointed out, even with the NIM removed we do not see the same errors as you?
From the testing that I have done, to try to reproduce your problem, I think the problem is around the USB interface?
If we can discount any confusion with DigiLite.
I think that, either an unprogrammed module or a module with the DigiLite template applied, escaped from the shop?
Hopefully reprogramming will be the solution?