Pytrack + FiPy setup on Win7

[jmarcelino]

@sandipg
Sorry for all basic question but can I ask if the FiPy is plugged the right way around (with the LED and reset button on top of the Pytrack USB connector) and all pins are correctly seated?

[crumble]

@sandipg

How do I proceed?

Your pytrack is still deteced as an dfu and not com device. The dfu device will be visible only for 7 seconds. Open device manager, pug out pytrack, plug in again. If you see your device pop up as a dfu device:

• open the device manger
• select show all devices (or be really quick, the device will be visible for 7 seonds)
• open dfu devices
• right click on the pytrack device
• select properties/details/drivers
• click on deinstall

[jmarcelino]

@crumble
Really appreciate you trying to help but in this case @sandipg already seen the Pytrack as a COM port device, it's just when he tries with the FiPy.

Also there is no need to remove the DFU driver as it's very convenient to have it for future upgrade. I can assure you it works without doing so, the DFU driver expects a different USB ID which only active when you press the button.

So please don't remove the DFU driver that is not really a valid long term solution. Perhaps it worked for you in a specific case, maybe if you used Zadig it set the regular device with the wrong driver, but if you use the drivers I posted below this should not happen.

[sandipg]

@jmarcelino Yes it is plugged in correctly. All the pins are fit snugly.

[Sat]

@sandipg Did this work for you?

I am having the same issue. PyTrack is seen as a COM device. However, we I add the FiPy module to PyTrack I cannot see it as a COM device.

[sandipg]

@sat Yes it worked when I used the drivers provided by @jmarcelino

[stefan85e]

@sandipg Make sure you have the device in DFU mode...
I tryied this many times sometimes It took me like 10 try to get the code in... also make sure you are in the right folder but it looks like you are in the right folder...

=======================================

Using DFU-util with Pytrack and Pysense
In order to put Pyrack or Pysense in DFU mode, press and hold the button on the Pytrack/Pysense board whilst powering on the board (connecting the USB cable).
Press the button and keep it held
Next plug-in the USB cable to the host computer and wait 1 second before releasing the button.
After this you will have approximately 7 seconds to run the DFU-util tool. -> This step you might have to do many times for it to work...

https://docs.pycom.io/chapter/pytrackpysense/installation/firmware.html

[combaindeft]

@jmarcelino

Hi, I'm on a Mac and I to experience the "no FiPy device is detected when I connect the Pytack+Fipy via USB to the computer" ...

I've done the installation procedure before on a LoPy+PyTrack combination ... and it worked like a charm.

But when I try now with the FiPy+PyTrack combo ... I don't get a usb-serial connection ...

The only way I can get it work is:

1st) Connect only the PyTrack to usb
2nd) I get a usb-serial device
3rd) I then plug the FiPy device into the PyTrack ...
4th) Now I see the FiPy boot up and run the "pycom.heartbeat(True)" ... Led blinking blue ...

To re-cap, if I try to power on the FiPy+Track (combo) via usb, it doesn't even boot up (no Led blinking blue) ...

[combaindeft]

@jmarcelino

I also just tried it with a JST LiPo Battery (FiPy+PyTrack+Lipo-Battery combo) ... and now it boots up and I get a usb-serial...

So the odd thing is, why does it try to boot-up in DFU-mode when FiPy+PyTrack is connected?

But it boots as usb-serial-device when only the Pytrack is connected? or when adding a battery, FiPy+PyTrack+Battery ...

I find this a little bit of strange logic ... and It's a little bit odd ... and I do think there is some sort of issue in the Firmware code (pytrack_0.0.8.dfu)

Where might one find the Firmware code (pytrack_0.0.8.dfu)? ... so one might have an investigative look at boot sequence of the PyTrack :-)

[seb]

@combaindeft

Could you try measuring Vin and 3.3 of the FiPy + Pytrack combo that does not show the USB serial? We have had a few customers facing issues that are fixed by using a high quality usb cable that can deliver enough current, the fact it works with a battery suggests this could be the issue.

As for the code for the pytrack/pysense, at the current time we have not made this open source. This may be something that happens in the future but I can't give any more details at this time.

[combaindeft]

@seb

A) FiPy+PyTrack+LiPo-Battery (Not-Attached-to-USB3.0)

Vin = 4.09~4.10 V
3V3 = 3.32 V

B) PyTrack+USB-Serial-device (Attached-to—USB3.0)

• same port as A)

  Vin = 4.85 V
  3V3 = 0.23 V

C) PyTrack+USB-Serial-device (Attached-to—USB3.0) + Hotswap-in-FiPy

• same port as A) & B)

  Vin = 4.55 V
  3V3 = 3.32 V

D) PyTrack+FiPy+NO-USB-Serial-device (Attached-to—USB3.0)

• same port as A) & B) & C)

• same combo as C)

• Just unplugged USB from PyTrack, and re-attached it…

  Vin = 1.69~2.51 V
  3V3 = 1.15~1.91 V

• Also, worth nothing is that if my hand slips with the measuring probes, I get it to “boot-up” by accidentally shorting GROUND & 3V3, and I get a USB-Serial-Devices on my computer [ergo like A), B) & C) …] …

• And then, I get the same Vin & 3V3 as C)

• Which makes me conclude that you’ve guys have a Firmware issue!!! … and not a “bad usb-cable” or “bad usb-port” … etc etc.

• For some reason, in the boot-sequence of the PyTrack Firmware, it choose not to boot-up FiPy and enable USB-Serial …

• And, again, it’s odd that I can short GROUND & 3V3 with my measuring probes, and then it boots up FiPy and enables USB-Serial…