Exactly what I was looking for. Thanks!

@Gustavo-Bertoli said in Installing WiPy3 using Expansion Board 2.1 on Win10: @sealyons please, any news on this troubleshooting ? I am using the expansion board V2.1a with SiPy and the COM do not become available also on Windows 7. I tried the drivers from FTDI website, multiple usb cables (that works with other modules) and still do not work. I just got it working by installing the FTDI driver through the windows installer instead of using the driver in the zip file and through driver update in the device manager. https://www.ftdichip.com/Drivers/CDM/CDM21228_Setup.zip

I came up with a solution to this that for the moment seems to work. It is based on checking the length of the outgoing message queue (will fail if no mqtt connection) for _ in range(10): in_queue = len(pybytes.__pybytes_connection.__connection.__mqtt._msgHandler._output_queue) if in_queue == 0: break time.sleep(1)

Hi all, May I know what pins are free on a FiPY/Pytrack2 combo. It seems that pin P4 SD_CMD, P8 SD_DAT and P23 SD_CLK are taken for SD card; pin P21 SCL and pin P22 SDA are for GPS and Accelerometer. External IO header has routed with 6 GPIO pins, but, only 3 of them - EXT_IO1, EXT_IO2 & EXT_IO3 are available as free ports, others are actually mean for RGB_LED(EXT_IO0), SD_CMD(EXT_IO4) and SD_DAT(EXT_IO5). Are there any more "free ports" for us with FiPy/Pytrack2 combo? for example, direct wire solder to the socket header on the pytrack2 board ? pin16? pin3? The pin orientation at Pytrack2 "External IO header" https://docs.pycom.io/datasheets/expansionboards/pytrack2/ is incorrect. is there any way to highlight this to the relevant party?

@Gijs said in Is there a dog in my py?: and clear the CONFIG and NVS partitions This seems to fix the problem for me. I had installed fresh firmware bur without resetting these two. Thanks again!

How do your calcs compare with m=lora.stats() print('TxTime(ms)',m[7])

@Copypastepro I was trying to connect a gateway to TTN as well last Friday, and for some reason I had a hard time with that as well. The initial discovery was really slow (that might also be caused by me using different pygates under the same EUI, sometimes (accidentally) simultaneously), so I cannot tell you where the fault is exactly. Great to see you got it working. the line 1452258414] lorapf: INFO_ [main] gateway MAC address is configured to lX saying lX at the end is my fault, I will get it fixed in the next pygate firmware! (If you're interested, we switched from using printf(..) to mp_printf(..) to make the logs also show up on telnet, but apparently the format that prints the MAC, %016llX, is not implemented in the latter) Gijs

@Cees_Meijer Yeah we measured SWR & cross checked it with RSRP reported by the modem. Many pcb style antennas fail to perform as well as a simple quarter wave ground plane or even a half wave dipole on band 28(750MHz). Not exactly sure why, could be compromises related to multiband (the PCBs are invariable multiband whereas the quarter/half waves are single band) or just that band28 is not included in the multiband design? In general many antennas advertised as LTE don't perform very well below 800MHz.

GReattt!! thanks

@bitvijays the default rx buffer size us 512. But you can set it when instantiating the uart object with the parameter rx_buffer_size=nnn Whether that can be set to a value like 40000 has to be tested.

The problem is solved! We got a new firmware for the expansion board from Pycom. As far as the information I have got from Pycom, the reason was that a custom expansion board firmware with a 30 sec watch dog implemented, was accidentally shipped on boards to others than the costumer who requested this function. The problem was entirely related to the firmware and not to the I2C bus as indicated in the headline and the initial post.

Both PyTrack still availbel £14/£15 each

I believe, but Im not sure, that the difference is related to the place the firmware is built from. When checking backtraces using one of the pycom.elf files, it will tell me the file locations of the file when it was compiled (complete path), so it somehow has to be contained in the .elf file Gijs

@Henning I had the same issue with the Expansionboard v3.1. The issue got solved, after using another Expansionboard v3.1 I've bought recentely..... I never used the SD-Card slot on the first one before, so I don't know, why it seems to be broken. Well, at least it works flawless with the second Expansionboard.

I've tested the SparkFun Nano Power Timer board some months ago, it was working ok, but it wasn't powering Expansion Board. What about : using LiPo/LiIon battery to avoid any USB cable to power Expansion Board ? powering LoPy4 directly, from Vin (3.0-5.5V) ? Why 15 s ? Is there any code in LoPy4 enabling the DONE pin of the Nano Power Timer ?

@MichaelWojcik Yes, the convention is to have all library files in the lib/ directory, no subdirectories. Or at least that's how it's worked out for me. Regarding your issue, I believe it stems from you doing import pycoproc.Pycoproc, when you should really be doing from pycoproc import Pycoproc