Callsign/Node ID

OS Help
1

Hi all,

RE: Callsign/Node ID

I inadvertently changed the Callsign/Node ID from VK3HJQ-ELBridge to VK3HJQ, then it would not let me change it back again. It was allowing up to 15 Characters in the Callsign area before but not now, I have been using hyphened callsign for ages to indicated that a particular node is a dedicated node for a specific use mainly for Bridging to EL, DMR & DVSW

i.e. VK3HJQ-ELBridge,VK3HJQ-DMRASLBR &

VK3HJQ-DVSM (typo needs fixing as well) VK3HJQ-DVSW

Can someone maybe fix this for me.

Thank you.

73 John vk3hjq

2

You cannot use characters any longer in the callsign field that aren't found in ITU-defined callsigns such as -. You can use a /. So you could set VK3HJQ/ELBridge.

3

Thanks for the reply.

Just tried VK3HJQ/ELBridge, this does not work in the callsign field either.

73 John vk3hjq

4

Sorry, I should have said it needs to be in all caps. I'll have to fix the form field to auto-uppercase the field.

5

Thanks for the reply.

Just tried VK3HJQ/ELBridge, this does not work in the callsign field either.

73 John vk3hjq

____________________________

Still No good using CAPS either.

73 John vk3hjq

6

I just tried entering KK6RQ/SOMETHING in the Callsign field for one of my nodes and it’s working for me, just FYI.

EDIT: I looked at your nodelist and was able to change for yours, too John; is that how you wanted it..?

7

Just tried it again now & it worked this time, Fantastic, thank you so much.

Edit: all good kk6rq

73 John vk3hjq

8

I may be duplicating effort; don’t want to step on any toes…

9

All good.

It’s “VK3HJQ/ELBRIDGE” now, as it was previously.

Thank you.

73 John vk3hjq

1 Like
10

VK3HJQ/DVSW needs to be VK3HJQ/DVSM as it was before, what was I thinking, now I cannot change this 1 back either.

73 John vk3hjq

11

Again, it let me no problem…which makes me think it could be a caching issue maybe..? Try deleting your browser history, deleting your cache and completely restarting the browser, then trying again.

Of course it’s already done, but you could test on something else.

12

Thank you, yep working again now, cache issue.

73 John vk3hjq

1 Like
13

I added some more cache-busting around the JavaScript that validates form fields and forced all callsign fields to uppercase as one types. Hopefully this won't happen to anyone else.

1 Like
14

Thanks. That answered a problem I had with ‘-’

1 Like
15

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.