Pin outs novatel

[Pheasant Surprise]

I’ve tried the 57600 already, but I’ll do the other suggestions now, if the pop up window is the one I’m thinking of, it’s set at 9600 at the moment

Yeh right click at this point....then choose properties etc.

Can you do a screen shot at this point and also the port settings bit?

 

[Pheasant Surprise]

Does the receiver need to see the sky while I’m doing this?

No

 

[Matt77]

Sorry I’m such an idiot, I was sure I’d got cables right, Tx and Rx changed and we’re away........not sure what I do now.

 

[Pheasant Surprise]

Nice work. You won’t be the first (or last) to get Tx and Rx around the wrong way. Anyway now we’re cooking with gas!

You need to change the baud rate setting for the receiver serial port - first have a look at receivers info (top). Take a screen shot. Then click on configuration, take another shot. Sorry still only on my phone here.

 

[Matt77]

 

[Pheasant Surprise]

....baud rate on COM1 looks ok!

So to recap the situation; it’s been connected/working fine with the Arag Delta80 using its COM1 (pins 1 and 2) to the Arag controller but when connected to the AFS screen using the same pins, the AFS screen does not recognise it?

 

[Matt77]

Yes that’s right, what I don’t understand is the 372 has connected with the delta 80 on 57600 setting and there is no mention of that number on these screens?

 

[Matt77]

This screen is also available, if I check advanced configuration I can change com1,com2 and unknown but not the top All one

 

[Pheasant Surprise]

Unfortunately I’m not familiar with the NovAtel receiver, so I’ll have a look at the reference manual for it when I get back to my laptop.

My thoughts are now it’s either a simple wiring mismatch between COM1 on the NovAtel and the corresponding port on the AFS - but I think you said you swapped around wires going to pins 1 and 2 of the NovAtel on your loom to the AFS. Check your signal ground has continuity too through your loom to the right pin on the AFS.

My second thought then is basic comms is OK but there is some sort of message issue, a difference in expected update rate or a key message type is missing on the comms going to the AFS.

It’s obviously fine for the Arag but not for the AFS. So will will need to look into that...

 

[Matt77]

Unfortunately I’m not familiar with the NovAtel receiver, so I’ll have a look at the reference manual for it when I get back to my laptop.

My thoughts are now it’s either a simple wiring mismatch between COM1 on the NovAtel and the corresponding port on the AFS - but I think you said you swapped around wires going to pins 1 and 2 of the NovAtel on your loom to the AFS. Check your signal ground has continuity too through your loom to the right pin on the AFS.

My second thought then is basic comms is OK but there is some sort of message issue, a difference in expected update rate or a key message type is missing on the comms going to the AFS.

It’s obviously fine for the Arag but not for the AFS. So will will need to look into that...

Thank you for all of your help so far, yes I did change pins 1&2 but maybe I should revisit it all, plus the other points you make. That maybe not for a day or two as I’m off with my girls on half term.
I’d like to buy you a drink for the help so far as it’s massively appreciated, maybe you could PM me an an address so I could post a drink of some sort, name your tipple!!

 

[Pheasant Surprise]

Thanks that’s very kind of you

Just to see what messages / formats etc the receiver is actually putting out on its COM1; when you're next looking at the unit - hook it up to you laptop again, go into the last screen where your were above in post #68 - on that screen click on “Interface Mode” tab next to “COM Config”

Take a screen shot!

Enjoy half term with your kids! Mine are driving me to that drink

 

[Matt77]

So this is the interface mode, it’s blank

Now I’m a little worried, just after I sent pic #68 I thought I’d change com2 baud rate from 19200 to 38400, it did this will no problem and excepted the change, now I can’t change it back!! The above pic was also blank before I did that as I’d already looked at that page.

 

[Matt77]

So this is the interface mode, it’s blank
View attachment 633764
Now I’m a little worried, just after I sent pic #68 I thought I’d change com2 baud rate from 19200 to 38400, it did this will no problem and excepted the change, now I can’t change it back!! The above pic was also blank before I did that as I’d already looked at that page.

It will change to all the other baud rates from 900 up to 230400 but won’t go back to 19200 on com2, which it was on, hope I’ve not messed this up!

 

[Pheasant Surprise]

It will change to all the other baud rates from 900 up to 230400 but won’t go back to 19200 on com2, which it was on, hope I’ve not messed this up!

Disconnect from the receiver. Try power cycling the receiver. Then reconnect and take the readings again.

 

[Matt77]

Disconnect from the receiver. Try power cycling the receiver. Then reconnect and take the readings again.

It will not change back to 19200, guess I should try it back on sprayer to check if it still works.

 

[Pheasant Surprise]

It will not change back to 19200, guess I should try it back on sprayer to check if it still works.
View attachment 634124

Is COM2 actually being used though? I thought the receiver was using COM1 as it’s method of communicating with the Arag controller. Try it again anyway.

You an also go use direct text commands (issued from the command line) to interogate the receiver and make settings.

It is probably far more flexible (and powerful) than the graphical interface but should be used with care.

 

[Matt77]

Is COM2 actually being used though? I thought the receiver was using COM1 as it’s method of communicating with the Arag controller. Try it again anyway.

You an also go use direct text commands (issued from the command line) to interogate the receiver and make settings.

It is probably far more flexible (and powerful) than the graphical interface but should be used with care.

Would this mean anything to you, on windows device manager you can pick the ‘com port’ number on the usb serial port, it connects on most numbers, not 3 and 7 now, odd as it did work on 7 before I started messing with it, I’ve connected up to 11 now as I’ve noticed the baud rate is different on the ‘com ports’ on the receiver screen for most of them, the unknown is always the same, 9600, but 1 and 2 change, got 115200, 38400, 460800 and 9600 as a mix?

 

[Pheasant Surprise]

Its a bit odd really . I can understand that the USB adapter may be auto detecting the serial port speeds and can connect at various baud rates to match the other end, so I would not be surprised to see it actually connecting at different reported baud rates.

On the other hand, almost without exception
the serial port baud rate on a GPS receiver is fixed at a particular value, unless it is explicitly changed by command (or in your case via Connect graphical interface). So I dunno, I'm scratching my head a bit there. I think it’s a red herring.

What would be definitive is to see or get the log output of the receiver, with all its current settings.

I had a quick look at the firmware reference manual for the receiver now, and its the RXCONFIG command that gives out the receiver settings. This can be done directly from the console with NovAtel Connect, as the following command:

log rxconfiga once

This will cause the receiver to output its current command settings

You have to be quite careful when issuing commands like this, especially if you've never done it before, its all too easy to brick something. So please tread carefully.

For reference,there’s also a software help guide here for NovAtel Connect v2.0. As well the Ag-Star User Manual which I linked earlier.

 

[Matt77]

Thanks, I put it back on the sprayer last night and put the screen back to it’s setting to connect, it connected straight away and gave forward speed so I’d say it’s all still working, and probably hasn’t changed anything?

 

[Pheasant Surprise]

I don’t have this particular software (or receiver), but typically with these programs you make a change using the graphical interface but have to ‘commit’ the changes (explicitly save them) to the receiver, to make them current, then power cycle it to make the changes active.

Issuing direct commands from the console though, like above, is typically instantaneous. They are committed once you receive the prompt back. That’s why in command mode you are in direct control, it’s very powerful and fast, but if your unfamiliar with the commands, structure/formats or make a mistake, it can be easy to cause carnage or potentially brick a device.

You’re safe though. Just looking won’t stuff things up.