Activity

Ok, that’s very interesting. It sounds like the LTEBee with a Hologram SIM has been using what it sees as the ‘best’ carrier for a given connection. The Digi modems would never do that for us in areas where Verizon was the only viable option, so we had to get Verizon-branded SIMs for those cases.

These modules are new enough that I think everyone who has bought one so far is using the same Hologram SIM cards that we use in all of ours.  I’ve deployed over 50 of them in the past couple months with Hologram cards, and according to our dashboard page that shows connection information, they are active on all the major carriers including…[Read more]

Hmm, so maybe no one has tried Verizon with the new modem yet. SIMCom claims that chip supports Verizon, but (suspiciously?) they don’t have a Verizon Certification document available for download, as they do for other carriers. And they list all their supposedly supported carriers under a heading labeled “Certifications(plan)”, which makes me…[Read more]

It’s not really an error, it’s just an artifact of the Eagle Cad schematic component since the original part in my library was for the ADS1015/1115, since both parts share the same footprint and schematic shape, but there’s no way to easily change the name displayed without editing the device.  I had to manually update that on previous Mayfly…[Read more]

There is no benefit in turning off the USB dipswitch if your board will be deployed with only a Lipo for power.  The switch is there solely for the purpose of deactivating the USB interface chip in case you are powering the Mayfly via the USB jack and want to save power, because the CP2102 chip can draw up to 10ma when idle, so turning it off can…[Read more]

Got it – thanks! I had the USB DIP switch off. I misinterpreted the specs sheet about the function of the switch, thinking it only disabled the LED, not the port. Is there a power penalty if I leave the USB switch on for a field deployment? The spec suggests that there is, but the USB LED won’t be lit in that case.

Matt

I’ve never experienced this problem with any of the Mayfly boards on any of the various PCs I’ve used them on, but I do have a colleague who has a similar problem with another CP2102-based board.  I think his solution was that sometimes it takes plugging and unplugging the device a few times before Windows finally recognizes it and assigns a com…[Read more]

Ah, that helps. Thanks Shannon and Neil!

Oh interesting I hadn’t seen the PYsync

In EnviroDIY_DS3231examplesPCsyncPYsync.py

There is a line looking for the port
# Keep only ports with the device communication type
device_ports = [
p for p in ports
if ‘VID_0403+PID_6001’ in p[2]
]

From device manager, PORTS , Silicon Labs CP210x USB to UART
In Events
I see
Device…[Read more]

When I connected my first v1 Mayfly last week, my laptop (Win10) didn’t recognize it. I manually installed the VCP drivers for CP210x from SiLabs, and then it worked. Uploaded code (using PlatformIO) to the board, and all was well. I set it aside for the weekend, and today I can’t get Windows to recognize the Mayfly. Windows Device Manager’s list…[Read more]

Sara is the person who wrote that PCSync program, so she’ll have to be the one to comment on why it’s not working.  I’m assuming it’s just looking for the FT232RL device of the older Mayfly boards and isn’t programmed to see the CP2102 of the Mayfly 1.0 as a viable device.  In the meantime, you can just use the the DS3231/adjust.ino sketch to m…[Read more]

Thanks for the info Neil.  Glad to know it’s not something I am doing wrong!

James

James, gosh nice to see systems up and going, seems like the TSA interface is being rebuilt
https://github.com/ODM2/ODM2DataSharingPortal/issues/512