Miata Problem, Not ready for emissions testing

Hopeful the hive can help.

Ive been trying to get my Miata inspected for a couple of weeks now and every time I go the computer shows "not ready for testing"  The first time I went it was my fault.  It has a Braille battery in it and we were out of town for a wedding so I disconnected it while we were gone.  When we got home, I reconnected the battery, got in and went straight to the inspection station.  When they tested it, it of course was not ready.  So.. I drove it for a week and  I put 400 miles on it.  I took it back and got the same result, "not ready for testing".  I've never had a car take that long to reset the monitors.  Any thoughts, ideas would be greatly appreciated.  For a  little back ground:

Its a 1996 with 160,00 miles on it and its been treated well.  It has a braille battery and had Megasquirt for a hot minute, then switched back to the OEM computer. 

Thanks In advance.

Pic because posts need pics...

Do you have an OBD2 reader so you can see what monitors are not ready?

While just driving it can get the monitors to reset it is better to follow an OBD2 drive cycle to try to get the exact monitors that you need to reset.

https://forum.miata.net/vb/showpost.php?p=8837865&postcount=3

https://trackdogracing.com/OBDII.aspx

The most accurate OBD drive cycle is the Federal Test Procedure and to be safe, add a highway into it.  

Here are the actual cycles that are run, where the tests HAVE to run- https://www.epa.gov/vehicle-and-fuel-emissions-testing/dynamometer-drive-schedules

Do an FTP test and then a HWFET test to be safe.  The best you can, at least.  The length of the FTP is about 10 miles total- almost 7 for bag 1+1 and just over 3 for bag 3.  And the highway test is another 10 miles.  The requirement is that all tests have to be completed running these cycles- mostly the FTP.  It's possible that the outside environmental conditions will prevent the tests from running, though. 

I had the same problem with my Suburban, drove more than 600 miles and they wouldn't set.  Started watching sensor readings and noted the original 178k mile O2 sensors were having lazy readings, never getting to extremes either.  I swapped them out and the monitors set fairly soon after that.