[Rick St John]

I ended downgrading the conduit to 3.3.7 then upgrading it back to mLinux 5.1.8. That fixed the problem of clearing out our custom firmware. No further info required.

[Rick St John]

Steve,

Agree concerning support portal/ticket. I am concerned about the 20 series and newer firmware and or settings. Our product at the moment does not function with the 20 series unless we can figure out why it would not take the initial program sequence attached to our sensor.

[Rick St John]

Steve,

No, can’t send AT commands to the 19 series mDot. Good to know that the AT commands are not necessary when reverting software back, but was still unable to make the 20 series work in our system with reverted firmware.

Is the 19056321 using the 2.0.16 or 2.0.16-1 firmware?

Once I build up another sensor, I’ll attach a 20 series to see if the sensor will program properly.

[Rick St John]

We send all of the configuration settings to the mDot when we program it on our sensor board. We normally just attach an mDot to our product without any of these intermediate steps with the MTUDK2-ST-CELL board. I’m using a USB to serial adapter. Device comes up as COM12. Flow control is set to none, 115,200 rate. Still not able to send any commands.

UPDATE: We have 2 shipments of mDots in house; the first has serial numbers beginning with 20 – the problem one specifically is 20121591. The other series has serial numbers beginning with 19 – specifically 19056321. I installed the 19 series board onto our sensor and programmed it up as if it were a fresh sensor – worked with no issues. Unable to achieve the same results with the 20 series mDot. Questions: Do these mDots serial versions have different underlying firmware versions? Perhaps I have some how corrupted the 20 series mDot when first programming it with our sensor; still unable to bring it back to life. I can load new firmware on it, but can’t get it to work with our conduit.

[Rick St John]

Unable to give it AT commands via Tera Term and does not connect to conduit when attached to sensor.

[Rick St John]

Are the AT commands required following programming?

[Rick St John]

When I say I tried to program it on our sensor board, our normal procedure is to attach a new mDot to the sensor board, then program the sensor board. The sensor appears to boot up properly, but the mDot is not connecting/communicating with the conduit properly.

[Rick St John]

Order part #: MTUDK2-ST-CELL. Serial # 18085756; we probably purchased it 4 years ago, so it is pretty old. The MDot is brand new; tried to program it on our own sensor board, which is our normal procedure. It does show up as a drive on Windows 10. I’ve since tried to put versions mdot-firmware-0.1.4.bin, mdot-firmware-1.0.8.bin and mdot-firmware-1.0.8-1.bin. It seems to add properly, but I can’t give it the AT commands – are they even necessary? Thanks.

[Rick St John]

Figured out this issue. Actually running linux 3.x, so got 1.0.43 to install.

[Rick St John]

Attempted with sudo, but same error; still running mLinux 4:

root@mtcdt:~# sudo opkg install lora-network-server_2.1.5-r5.0_mlinux.ipk
Collected errors:
* opkg_prepare_url_for_install: Couldn’t find anything to satisfy ‘lora-network-server_2.1.5-r5.0_mlinux.ipk’.
root@mtcdt:~#

[Rick St John]

After loading the ipk using teraterm SSH SCP, get the following error:

root@mtcdt:~# opkg install lora-network-server_2.2.5-r5.0_mlinux.ipk
Collected errors:
* opkg_prepare_url_for_install: Couldn’t find anything to satisfy ‘lora-network-server_2.2.5-r5.0_mlinux.ipk’.
root@mtcdt:~#

[Rick St John]

OK, thanks. Was also not able to re-install the lora-network-server_2.1.5-r5.0_mlinux.ipk however. Do you know why I would not be able to reinstall 2.1.5?

Also, I don’t see 3.3.15 in the standard http://www.multitech.net/developer/downloads/ area; I do see it in the link you provided.

[Rick St John]

Jason, Thanks for your quick reply. Can you provide the link or location on website for opening a case? Thanks.

[Rick St John]

It worked! Reverted to 1.0.43 and the system works again. Many thanks.

Do you know why the 1.0.36 release is no longer listed on the web site? That is the one we have been using.

Thanks.

[Author]

Posts