If we update the firmware for interfacing. I can offer you the choice between upgrading the current commands or writing another protocol intended for M2M ?
As explained by Clauss, doing 32 bits multiplication or divide on an old 8 bits mcu in assembly is possible but complicated and consumme a lot of cpu cycle. Instead I can output the PLL step and you do the computation.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I now did some modifications within the PRM80xx Firmware to handle channels with shift frequency now. Tested with Terminal works fine.
Stéphane:
I did some more test with the HAMLIB V4.1, for me that looks like your changes for the PRM80 are not included.
Do you have your changes available on Github so I can check the current implementation for the Squelch?
I'm wondering because the Squelch is handled within V4.1 correctly (sending an "O" instead of "0" as command to the PRM). I'm still not able to compile the software myself (Windows PC), but I will do some more investigations).
I also found one behavior which could be an issue.
The JRX Backend Software is sending a "," instead of an "." for decimal numbers.
I assume HAMLIB is expecting a ".", but I have a German Windows version so I this is the reason why JRX is using the "comma" as decimal point.
Do you have any idea?
73 Claus
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I now did some modifications within the PRM80xx Firmware to handle channels with shift frequency now. Tested with Terminal works fine.
Stéphane:
I did some more test with the HAMLIB V4.1, for me that looks like your changes for the PRM80 are not included.
Do you have your changes available on Github so I can check the current implementation for the Squelch?
I'm wondering because the Squelch is handled within V4.1 correctly (sending an "O" instead of "0" as command to the PRM). I'm still not able to compile the software myself (Windows PC), but I will do some more investigations).
I also found one behavior which could be an issue.
The JRX Backend Software is sending a "," instead of an "." for decimal numbers.
I assume HAMLIB is expecting a ".", but I have a German Windows version so I this is the reason why JRX is using the "comma" as decimal point.
Hello Mike,
thanks a lot for the patch. Now with this version I can control the volume and squelch of my PRM via JRX as expected. The changes, Stéfan did for the VCO stuff are not included, yet. A merge of both versions will solve nearly all of the issues I had while starting this topic.
Some features are still missing (e.g. reading RSSI), I will impöement as soon I know how this command should be implemented for HAMLIB
73 Claus
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Mike,
thanks a lot for the patch. Now with this version I can control the volume and squelch of my PRM via JRX as expected. The changes, Stéfan did for the VCO stuff are not included, yet. A merge of both versions will solve nearly all of the issues I had while starting this topic.
Some features are still missing (e.g. reading RSSI), I will impöement as soon I know how this command should be implemented for HAMLIB
73 Claus
Hi Mike, Hi Claus,
I'm going to send you a pull request. Sorry for missing version 4.1.
Just need to make a fix regarding the set_level AF (set volume) command, and a cleanup.
73 Stéphane
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi all,
all my tests done with positive results.
The onliest questions I still have are: when will we have a released HAMLIB version? Is there a possibility to mark this topic as "solved"?
Thanks a lot for your help
Claus
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi all,
all my tests done with positive results.
The onliest questions I still have are:
when will we have a released HAMLIB version?
Is there a possibility to mark this topic as "solved"?
In regard to Squelch:
I did some more investigations into write and Read squelch via Terminal:
Setting the squelch was done via "F"
Reading the squelch via "E" (Show system state)
The 4th Byte (from left) is reflecting the squelch value and correspondends with the value, set via "F" command
If we update the firmware for interfacing. I can offer you the choice between upgrading the current commands or writing another protocol intended for M2M ?
As explained by Clauss, doing 32 bits multiplication or divide on an old 8 bits mcu in assembly is possible but complicated and consumme a lot of cpu cycle. Instead I can output the PLL step and you do the computation.
Hello,
I now did some modifications within the PRM80xx Firmware to handle channels with shift frequency now. Tested with Terminal works fine.
Stéphane:
I did some more test with the HAMLIB V4.1, for me that looks like your changes for the PRM80 are not included.
Do you have your changes available on Github so I can check the current implementation for the Squelch?
I'm wondering because the Squelch is handled within V4.1 correctly (sending an "O" instead of "0" as command to the PRM). I'm still not able to compile the software myself (Windows PC), but I will do some more investigations).
I also found one behavior which could be an issue.
The JRX Backend Software is sending a "," instead of an "." for decimal numbers.
I assume HAMLIB is expecting a ".", but I have a German Windows version so I this is the reason why JRX is using the "comma" as decimal point.
Do you have any idea?
73 Claus
Here's a Windows build of the latest.
I assume the comma problem is dealing with setting levels?
I put in a patch that should fix that.
https://www.dropbox.com/s/q0i90h7ee1w2tnf/bin.zip?dl=0
Mike W9MDB
Hello,
I now did some modifications within the PRM80xx Firmware to handle channels with shift frequency now. Tested with Terminal works fine.
Stéphane:
I did some more test with the HAMLIB V4.1, for me that looks like your changes for the PRM80 are not included.
Do you have your changes available on Github so I can check the current implementation for the Squelch?
I'm wondering because the Squelch is handled within V4.1 correctly (sending an "O" instead of "0" as command to the PRM). I'm still not able to compile the software myself (Windows PC), but I will do some more investigations).
I also found one behavior which could be an issue.
The JRX Backend Software is sending a "," instead of an "." for decimal numbers.
I assume HAMLIB is expecting a ".", but I have a German Windows version so I this is the reason why JRX is using the "comma" as decimal point.
Do you have any idea?
73 Claus
PRM80xx can not connect to my PRM8020 and PRM8070
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
Hello Mike,
thanks a lot for the patch. Now with this version I can control the volume and squelch of my PRM via JRX as expected. The changes, Stéfan did for the VCO stuff are not included, yet. A merge of both versions will solve nearly all of the issues I had while starting this topic.
Some features are still missing (e.g. reading RSSI), I will impöement as soon I know how this command should be implemented for HAMLIB
73 Claus
Where did Stefan post those changes?
Mike
Hello Mike,
thanks a lot for the patch. Now with this version I can control the volume and squelch of my PRM via JRX as expected. The changes, Stéfan did for the VCO stuff are not included, yet. A merge of both versions will solve nearly all of the issues I had while starting this topic.
Some features are still missing (e.g. reading RSSI), I will impöement as soon I know how this command should be implemented for HAMLIB
73 Claus
PRM80xx can not connect to my PRM8020 and PRM8070
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
I got a link via private mail.
We have to wait until he is able to spend some time, again.
73 Claus
If you can send me the link I'll build another version.
Mike
I got a link via private mail.
We have to wait until he is able to spend some time, again.
73 Claus
PRM80xx can not connect to my PRM8020 and PRM8070
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
I only got the link to the binaries.
73 Claus
Ask him to contact me.
Mike
I only got the link to the binaries.
73 Claus
PRM80xx can not connect to my PRM8020 and PRM8070
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
Hi Mike, Hi Claus,
I'm going to send you a pull request. Sorry for missing version 4.1.
Just need to make a fix regarding the set_level AF (set volume) command, and a cleanup.
73 Stéphane
Hi all,
all my tests done with positive results.
The onliest questions I still have are:
when will we have a released HAMLIB version?
Is there a possibility to mark this topic as "solved"?
Thanks a lot for your help
Claus
4.2 will hopefully be released by the end of the month.
We're going through testing with several apps and fixing some bugs
Mike W9MDB
Hi all,
all my tests done with positive results.
The onliest questions I still have are:
when will we have a released HAMLIB version?
Is there a possibility to mark this topic as "solved"?
Thanks a lot for your help
Claus
PRM80xx can not connect to my PRM8020 and PRM8070
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
There's no topic marking available here....so people will just have to read that it's testing OK now.
The issue has been closed on github.
Mike W9MDB