Latest firmware update has created random exception errors

[mnewkirk]

Did a firmware update about two weeks ago, and since then I've been seeing random exception errors occurring. I'm unable to capture the screen as I'm only seeing it scroll through my modem buffer window on the BBS, but it has happened now about five times since the update - and was not happening at all before. The BBS is a 24x7 operation, so can definitely see where I was in a stable state before the update as to what has occurred over the last few weeks.

Anyone else been seeing this?
Mike

[admin]

I have not had any reports of issues, and I have not seen anything myself. What were you doing when exceptions were generated?

If you have not updated in awhile you might want to do AT&F to reset the settings to the defaults. Some new functions were added.

You can always go backwards to a previous version by using AT*DOWNGRADE.

[mnewkirk]

I have not had any reports of issues, and I have not seen anything myself.  What were you doing when exceptions were generated?

If you have not updated in awhile you might want to do AT&F to reset the settings to the defaults.  Some new functions were added.

You can always go backwards to a previous version by using AT*DOWNGRADE.

This is occurring when the BBS is in an idle state waiting for a caller. As mentioned, I can't capture what the exception error is saying, it just scrolls by in the small screen area where I can see the modem communication screen.

Below is the snapshot of my modem settings:
RTS/CTS:disabled
DCD state: 1
DCD polarity: 1
CTS State:
CTS Polarity: 1
RTS State: 0
RTS Polarity: 1
Translation: None

b0 c0 e0 l0 m1 n0 q0 v1 w255 x1 s0:0 s1:0 s2:43 s3:13 s4:10 s5:8 s6:2 s7:60 s8:2 s9:6 s10:30  s11:90 s12:11 s25:0 s30:0 s37:6 s73:0 *b2400 *bl1024 *bt5 *c1 *ct1 *d1 *ho25 *l6502 *led5 *p1541 *r1 *t0 &c1 &d0 &g0 &k0 &q0 &s0

[admin]

Set W to 0. You have not done AT&F, so W is set to 255... that value should be either 0 or 1. So, in a terminal program type:

ATW0 <RETURN>
AT&W <RETURN>

This could be reason you are seeing the issue.

[mnewkirk]

Set W to 0.  You have not done AT&F, so W is set to 255... that value should be either 0 or 1.    So, in a terminal program type:

ATW0 <RETURN>
AT&W <RETURN>

This could be reason you are seeing the issue.

Awesome, much thanks! and correct, I sent the settings before doing the AT&F so you could see my current config.
Thanks for the awesome and quick support!!

[admin]

I have made a new update (6.41) that checks the variable now to make sure that value for W is correct on power up when the EEPROM was not reset yet.