Both the COM.LTE and Servo2 modules are powered externally.

There seems to be a short when I use them together, but they both work when they're the only connected module. Are these two incompatible, or is there a dip switch or something I'm missing?

I'm trying to connect to AWS's IoT Core with the NB-IoT module.

I have been able to connect to IoT Core over wifi and have been able to get expected status and signal strength messages from my com.NB-IoT module, but I can't get them to work together.

The NB IoT module does come with it's own MQTT implementation, but the username/password configuration won't work with AWS Iot Core. But, when I try the AWS package (without wifi), messages aren't published to IoT Core.

Is this going to be possible? Am I missing a configuration?

I did notice that the network registration value is 6 Registered for "SMS only", home network (applicable only when <Act> indicates NB-IoT). I suspect I should be getting 1 Registered, home network?

For anyone finding this. I contacted M5 and they suggested the odrive module, but that's currently out of stock.

I've moved on to trying to use either a stepper motor or a servo for my application and I think I can make them work.

Good question, @felmue...

I guess I'd be interested in two different configurations. I'm prototyping with a smaller one (12V/.8A), but I suspect I might need the more powerful one (12V/3A) in the future.

Thanks!

Anyone have any suggestions for the best module to use to control a linear actuator?

I've used the relays but the wiring and logic aren't super clean.

Hoping folks might have used other methods...?

The UnitV2 appears to use a UART connection with the same HY2.0-4P Grove connector as other peripherals that use I2C.

If I wanted to connect multiple peripherals and a UnitV2 camera to the Core2 (which only has one Grove port), I can't simply use the Grove-T or the PbHub, right?

Would I need a port expansion module, like the COMMU to get the additional I2C ports?

For anyone finding this. I had to restart the ethernet over usb interface with ifconfig with down and up commands to get connected. Then it worked fine.

Anyone have any troubleshooting tips for connecting a UnitV2 with Ubuntu. I see there are drivers for MacOS and Windows, but not for *nix (maybe because it's already supported?).

When I connect via USB, the device fan spins up, but neither http://10.254.239.1 nor http://unitv2.py resolve.