Derek, Regarding the pulsing, the issue is on startup we don’t know which modem is used, so have to pulse from the generic base driver. We only identify the modem after it has been powered and responds to its version identification command. If your modem is not responding to AT commands (on rx/tx), then how is it even loading the SIM7600 driver? Or are you using config modem/driver to manually configure it? Regards, Mark.
On 5 Jul 2023, at 1:48 PM, Derek Caudwell <d.caudwell@gmail.com> wrote:
Thanks Mark,
I am on the "edge" firmware and have the verbose logging already enabled. The tx is being logged ok but no rx back.
Another anomaly is it will sometimes go from PoweringOn to PoweredOn with no apparent response to the AT command being sent, then times out back to PoweringOn.
So there may be a hardware failure, voltage level shifter perhaps? I will try putting an oscilloscope on both ends of transmission next.
In testing I simply modified the simcom 7600 driver code to override the default modem driver so as not to effect the 5360 pulse logic. The spec sheet also mentioned it takes the UART around 11s to respond after power up. Using the spec sheet timing with a delay after turning on appears very reliable on mine in powering up and down the module. Whereas the 2s and 6s pulse turned it on and the 4s pulse turned it off going by the led status. _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev