I personally have no experience with Chirpstack but do you have an end-node already operating in class B on your Chirpstack? Also, does the gateway has GPS?
Another thing is that you must be successfully joined first to establish the device in class B. Then I suggest wait for around two minutes (128seconds) to see if your device can see a beacon downlink coming from the Network Server (via your gateway). Without the beacon lock, the device will keep on S1 state or S3.
Thanks for the reply @carlrowan . I do not have another end-node. The GW I am using does have GPS and has fix on the satellites. I can successfully join the network but I don’t ever see beacon lock even after letting it sit for over an hour. Is there an example of the setup for class b somewhere? The GW I’m using is currently under development so I’m trying to remove as many variables as possible to test things.
I cannot same much about your gateway and your configuration on Chirpstack. However, I can probably make a guide using RAK3172 and WisGate Edge for class B then put it in our knowledge hub.
Btw, your sequence is correct. You configure to class B, join the network, send uplinks and wait for successful lock.