Date   
Re: DPlus connection to REF001C failed - WinDV on WIn10 #cal-invite

Kk4lyn@...
 

I am have trouble getting blue dv to conect to dmr using bandmast


On Sun, Oct 14, 2018, 2:54 PM Pete N <kc2wi.afa2cq@...> wrote:
The problem I reported was caused by a defective router. However, even when I took my netbook to another location I found only the Free*Star VE3TNK (ve3tnk.homelinux.net) callsign server worked. 

I tried WinDV a couple of days ago and I just tried it again (at a different location on a different computer). Both times/places it would not connect even using the Free*Star server.  the problem is the server is unreachable. I can't ping it. Tracert shows request timed out an the 9th hop.

WinDV has not been updated in a long time. Apparently there have been enough changes in DSTAR that WinDV no longer works. 

I followed the advice I got on https://www.facebook.com/groups/DSTAR.Users.Group downloaded and installed BlueDV. It works great with the ThumbDV.

The only disadvantage is I can't use it on my old Dell Mini 9 with XP. But there is a Linux version so I will probably convert the Mini 9 to Linux Mint.

Re: DPlus connection to REF001C failed - WinDV on WIn10 #cal-invite

TOMMY <Tommyleb@...>
 

Good to know, my windv app stop working few weeks ago, so i use bluedv, works
great with my red nwdr thumbdr. Use on old dell laptop with windows 7.
73, KM4VTE, Tommy



Sent from my Verizon, Samsung Galaxy smartphone

Re: DPlus connection to REF001C failed - WinDV on WIn10 #cal-invite

Pete N
 

The problem I reported was caused by a defective router. However, even when I took my netbook to another location I found only the Free*Star VE3TNK (ve3tnk.homelinux.net) callsign server worked. 

I tried WinDV a couple of days ago and I just tried it again (at a different location on a different computer). Both times/places it would not connect even using the Free*Star server.  the problem is the server is unreachable. I can't ping it. Tracert shows request timed out an the 9th hop.

WinDV has not been updated in a long time. Apparently there have been enough changes in DSTAR that WinDV no longer works. 

I followed the advice I got on https://www.facebook.com/groups/DSTAR.Users.Group downloaded and installed BlueDV. It works great with the ThumbDV.

The only disadvantage is I can't use it on my old Dell Mini 9 with XP. But there is a Linux version so I will probably convert the Mini 9 to Linux Mint.

NOAA issued an ALTTP2-0239 UTC - High speed particles escaped the sun!

A Schwarz
 

Hi Everybody;

 

NOAA issued a ALTTP2 alert. This is not the kind of alert I would expect at solar minimum. I also honestly have to admit this is the first time I see it. It states that we will be getting nit by a plasma cloud at the speed of almost 900km/s. This is fast! The only indication that there was a masse ejection is a B class solar x-ray-flux spike. Kp and proton flux are low too.

Conditions at the MDSR test station are still reasonable good, but if the type II emission hits we will get some serious propagation change. We cannot predict if this will be good or bad for    

 

Stay tuned!

 

Current conditions at the MDSR test station:

80m open S5

40m open S4

30m open S3

20m open S4

15m closed S3

10m closed S1

 

Watch it live here:

http://users.skynet.be/myspace/mdsr/

 

All the best and 73;

 

Alex - VE7DXW

===============================================================================

NOAA Alert:

 

Space Weather Message Code: ALTTP2

Serial Number: 1068

Issue Time: 2018 Oct 12 0239 UTC

 

ALERT: Type II Radio Emission

Begin Time: 2018 Oct 12 0152 UTC

Estimated Velocity: 864 km/s

www.swpc.noaa.gov/noaa-scales-explanation

Description: Type II emissions occur in association with eruptions on the sun and typically indicate a coronal mass ejection is associated with a flare event.

Re: DPlus connection to REF001C failed - WinDV on WIn10 #cal-invite

TOMMY <Tommyleb@...>
 

have same issue, worked great for few weeks, didnt use the nwdr thumb dv for about a week and half , turned on and " d plus connection failed{ref anyone} failed. any ideas,thanks KM4VTE Tommy

Re: nwdr thumb drive

james
 

give me a call jimbo ---458-209-1221


On 10/6/2018 8:49 PM, Brad NK8J wrote:
have you updated you Reflector lists?

On 10/5/2018 8:00 PM, TOMMY wrote:

worked fine for few weeks, useing Windv,  left alone for 2 weeks turned back on and now "dplus connection (ref whatever) failed!)

any ideas.

Thumd drive still works useing Blue dv 






Re: nwdr thumb drive

Brad NK8J <bradnk8j@...>
 

have you updated you Reflector lists?

On 10/5/2018 8:00 PM, TOMMY wrote:

worked fine for few weeks, useing Windv,  left alone for 2 weeks turned back on and now "dplus connection (ref whatever) failed!)

any ideas.

Thumd drive still works useing Blue dv 





Re: Linux RMS - headed for digital dustbin?

Tony <w7efs@...>
 

Yes, that requires something like https://github.com/AlbrechtL/RPi-QEMU-x86-wine

On 10/06/2018 11:35 AM, John D Hays - K7VE wrote:
You can build wine, but x86 applications aren't conducive to running on ARM processors. 

On Sat, Oct 6, 2018, 11:18 Tony <w7efs@...> wrote:
On 10/04/2018 03:09 PM, Steve wrote:

> Wine has not been ported to the ARM architecture, so NO Windoze app
> will work on a RPi. ...

I'm not defending it or its usage, but the open-source wine compiles
cleanly on a RPi2B after bison and flex packages are installed:

$ time (./configure --prefix=$HOME && make && make install)
...
Wine build complete.
...
real    1859m48.653s
user    1501m34.850s
sys     66m20.200s

$ uname -mr && wine --version
4.4.11+ armv6l
wine-3.17-74-gee206a3





Re: Linux RMS - headed for digital dustbin?

 

You can build wine, but x86 applications aren't conducive to running on ARM processors. 


On Sat, Oct 6, 2018, 11:18 Tony <w7efs@...> wrote:
On 10/04/2018 03:09 PM, Steve wrote:

> Wine has not been ported to the ARM architecture, so NO Windoze app
> will work on a RPi. ...

I'm not defending it or its usage, but the open-source wine compiles
cleanly on a RPi2B after bison and flex packages are installed:

$ time (./configure --prefix=$HOME && make && make install)
...
Wine build complete.
...
real    1859m48.653s
user    1501m34.850s
sys     66m20.200s

$ uname -mr && wine --version
4.4.11+ armv6l
wine-3.17-74-gee206a3




Re: DRAWS Technical Documents

Dave_G0WBX <g8kbvdave@...>
 

Hi John.

I'll pass thanks, if it's this fragmented and peculiar just to see basic technical spec's I wont bother.   Especially as there are viable alternatives that are indeed fully documented.

73.

Dave G0WBX.

Unsubscribe imminent.



  Re: DRAWS Technical Documents

From: John D Hays - K7VE
Date: Fri, 05 Oct 2018 07:26:04 PDT

Groups.io has groups and sub-groups. We use sub-groups for topics surrounding a product or major topic. 

In theory, discussions about AMBE products have a sub-groups as does one for UDRC & DRAWS. People can then subscribe to sub-groups off interest. 

Main, this group, is for general topics. It sometimes gets thread that truely should be in a sub-group.

Simply join the sub-groups that interest you.
-- 
Created on and sent from a Unix like PC running and using free and open source software:

Re: Linux RMS - headed for digital dustbin?

Tony <w7efs@...>
 

On 10/04/2018 03:09 PM, Steve wrote:

Wine has not been ported to the ARM architecture, so NO Windoze app
will work on a RPi. ...
I'm not defending it or its usage, but the open-source wine compiles
cleanly on a RPi2B after bison and flex packages are installed:

$ time (./configure --prefix=$HOME && make && make install)
...
Wine build complete.
...
real    1859m48.653s
user    1501m34.850s
sys     66m20.200s

$ uname -mr && wine --version
4.4.11+ armv6l
wine-3.17-74-gee206a3

Re: nwdr thumb drive

Tony <w7efs@...>
 

On 10/05/2018 05:00 PM, TOMMY wrote:

worked fine for few weeks, useing Windv,  left alone for 2 weeks turned back on and now "dplus connection (ref whatever) failed!)

any ideas.


Have you tried other reflectors? Your default may be temporarily down.

Re: nwdr thumb drive

 

If the ThumbDV works with BlueDV (or Buster), then the ThumbDV is fine.

Software support is by the software author -- WinDV support is at http://www.dutch-star.eu/feedback.aspx


On Fri, Oct 5, 2018 at 5:20 PM TOMMY <Tommyleb@...> wrote:

worked fine for few weeks, useing Windv,  left alone for 2 weeks turned back on and now "dplus connection (ref whatever) failed!)

any ideas.

Thumd drive still works useing Blue dv 






--


John D. Hays
Edmonds, WA
K7VE

   

nwdr thumb drive

TOMMY <Tommyleb@...>
 

worked fine for few weeks, useing Windv,  left alone for 2 weeks turned back on and now "dplus connection (ref whatever) failed!)

any ideas.

Thumd drive still works useing Blue dv 




Re: Linux RMS - headed for digital dustbin?

 

Someone gave me a pointer and I pulled down the HTML directory zip file.  Yes, they are pretty straight forward HTML files.  I did not know where they were located, and I didn't see a top level "Here are the forms" top level link. I would have installed WE to see if I could find them.  However, it will take some time to figure out what the transmission API looks like.

What I would like to see are some nice architectural diagrams and protocol/API documentation.  Plus move the code to Open Source and public repositories.


On Fri, Oct 5, 2018 at 10:20 AM Scott Currie <scott.d.currie@...> wrote:
Indeed. Apparently my last post was deemed inappropriate. I'll reword it...

All the WE standard forms are downloadable in a zip file using the manual update process:
Or you can pull them from an installed instance of WE, they live in the "RMS Express\Standard Templates" directory.
 
Instructuctions for creating forms and how the process works is clearly explained in the WE help files:
HTML Forms
Winlink Express supports using html forms for requesting input from users.  This is similar to using <ask...> and <select...> fields in templates, but it provides the full power of html including JavaScript, cascading style sheets, etc.  Since Winlink Express is intended for field use without the Internet, forms must be stored on the client computer, and they should not reference items through the web.  Here's an example of an html form.....
 
There are several pages dedicated to this with very detailed examples. Even a novice HTML author like me can create usable forms (in fact, a few of the standard forms did come from me). Someone with real HTML/CSS skills should have no trouble reading the doc and creating high quality forms.
 
-Scott, NS7C



--


John D. Hays
Edmonds, WA
K7VE

   

Re: Linux RMS - headed for digital dustbin?

Scott Currie
 

Indeed. Apparently my last post was deemed inappropriate. I'll reword it...

All the WE standard forms are downloadable in a zip file using the manual update process:
https://winlink.org/WinlinkExpressForms
Or you can pull them from an installed instance of WE, they live in the "RMS Express\Standard Templates" directory.
 
Instructuctions for creating forms and how the process works is clearly explained in the WE help files:
HTML Forms
Winlink Express supports using html forms for requesting input from users.  This is similar to using <ask...> and <select...> fields in templates, but it provides the full power of html including JavaScript, cascading style sheets, etc.  Since Winlink Express is intended for field use without the Internet, forms must be stored on the client computer, and they should not reference items through the web.  Here's an example of an html form.....
 
There are several pages dedicated to this with very detailed examples. Even a novice HTML author like me can create usable forms (in fact, a few of the standard forms did come from me). Someone with real HTML/CSS skills should have no trouble reading the doc and creating high quality forms.
 
-Scott, NS7C

Re: Linux RMS - headed for digital dustbin?

Scott Currie
 

Really, did you spend more than 5 seconds looking? All the standard forms are downloadable in a zip file using the manual update process:
https://winlink.org/WinlinkExpressForms
Or you can pull them from an installed instance of WE, oddly, they live in the "RMS Express\Standard Templates" directory. Who would have guessed?!

Instructuctions for creating forms and how the process works is clearly explained in the WE help files:
HTML Forms
Winlink Express supports using html forms for requesting input from users.  This is similar to using <ask...> and <select...> fields in templates, but it provides the full power of html including JavaScript, cascading style sheets, etc.  Since Winlink Express is intended for field use without the Internet, forms must be stored on the client computer, and they should not reference items through the web.  Here's an example of an html form.....

There are several pages dedicated to this with very detailed examples. Even a novice HTML author like me can create usable forms (in fact, a few of the standard forms did come from me). Someone with real HTML/CSS skills should have no trouble reading the doc and creating high quality forms.

If other developers choose not to create a compatible process, or user choose not to create forms for their needs, it is not due to a lack of documentation.

-Scott, NS7C
 

Re: DRAWS Technical Documents

 

Groups.io has groups and sub-groups. We use sub-groups for topics surrounding a product or major topic. 

In theory, discussions about AMBE products have a sub-groups as does one for UDRC & DRAWS. People can then subscribe to sub-groups off interest. 

Main, this group, is for general topics. It sometimes gets thread that truely should be in a sub-group.

Simply join the sub-groups that interest you. 

On Oct 5, 2018 07:18, "Dave_G0WBX via Groups.Io" <g8kbvdave=googlemail.com@groups.io> wrote:
I am subscribed to this group just fine (judging by the onslaught of WinLink spam, now filtered out) but I too cant see the documents as the link John posted results in a page showing a red banner at the top of the page that says:-
"You are not subscribed to this group with this email address."

I think that's because that page is not part of the "main" group.   So, what gives?

I only came here to find some tech info, at John's suggestion, as all that's publicized so far is advertising copy with no real "meat on the bone".

Dave G0WBX.


Re: DRAWS Technical Documents

Dave_G0WBX <g8kbvdave@...>
 

I am subscribed to this group just fine (judging by the onslaught of WinLink spam, now filtered out) but I too cant see the documents as the link John posted results in a page showing a red banner at the top of the page that says:-
"You are not subscribed to this group with this email address."

I think that's because that page is not part of the "main" group.   So, what gives?

I only came here to find some tech info, at John's suggestion, as all that's publicized so far is advertising copy with no real "meat on the bone".

Dave G0WBX.

Re: Linux RMS - headed for digital dustbin?

Stuart Longland VK4MSL
 

On 05/10/18 12:05, sancudo wrote:
What Scott is saying rings true with me bc I've taught ham classes
locally and KISS is a big four letter word when it comes to my students
trying get hardware to work with simple software. Most folks barely know
how to access Windows, much less Linux or ARM based software. 
Yeah, well… KISS to me means dedicated system that just does ONE thing.
Maybe an embedded CPU of some kind running an emcomm application out of
ROM (flash).

If you want Linux that just does one thing and one thing well, perhaps
one can provide a USB stick/CD-R for you to boot off, and your machine
will do *only* that thing.

You're basically making an appliance. A single-board computer running
Linux such as a Raspberry Pi gets close. Still a lot of complexity
going on, but you've got more scope for paring it down to bare essentials.

I can freely do this with Linux, so long as I can lay my hands on the
sources in the event you ask me for them (GPLv2 clause 2b). I can also
do it with *BSD, and then I don't even have to give you the source.

If I try handing you Windows on a USB stick, I'm liable to be sued for
copyright violation unless I spend megabucks on appropriate licenses for
each and every copy I hand out.

That said, Windows in the right hands is a perfectly viable OS. There
are ways you can tame it and coerce it into working for you.

This is really beside the point however.

To quote what I actually said in my last email:
On 05/10/18 08:27, Stuart Longland wrote:
This is just a symptom of a larger problem, people who write software
for legacy operating systems only and don't document how their software
operates.

Really, it should not matter that Winlink Express is Windows-only. It
should not matter that they only support Windows.

The protocol should be open and documented. Sufficient for someone to
come up with an alternate but interoperable system.
If the details of Winlink Express are available and openly implementable
by anyone, this becomes a non-issue. You use Winlink Express, I use
whatever the hell I want, both tools talk the same language, we can
communicate.

I don't have to use Gmail to send you this reply, nor do you have to be
running Thunderbird to receive my reply. Our email clients speak the
same language: Unicode, RFC-822 and Multipurpose Internet Mail Extensions.

It wasn't that long ago that the latter bit (MIME) was not a feature of
email clients, and so sending an attachment to someone was truly a dark
art requiring a good understanding of tools like `uuencode`. (My memory
is hazy, but I seem to recall Trumpet Mail & News reader on Windows 3.1
circa 1996 having problems in this department.)

What we use over the air should be the same.

If Microsoft get bored of running that activation server your Windows XP
box phones home to, preventing you from re-installing the OS when your
HDD crashes, or the latest Windows 10 update prevents you from
installing applications that aren't from the "Windows Store", you're not
stuck for a replacement computer, you can grab whatever's to hand and
load on whatever compatible replacement software.

So long as *you* know how to drive your end, I know how to drive mine,
and the two "systems" talk the same language, that is all that matters.
--
Stuart Longland (aka Redhatter, VK4MSL)

I haven't lost my mind...
...it's backed up on a tape somewhere.