Month: June 2014

Posted on

EE6 and EE7 Maven deps for JBoss AS7 and WildFly8

For EE7 on WildFly8.x, use:

Full profile:

        <dependency>
            <groupId>org.jboss.spec</groupId>
            <artifactId>jboss-javaee-7.0</artifactId>
            <version>1.0.0.Final</version>
            <type>pom</type>
            <scope>provided</scope>
        </dependency>

Web profile:

        <dependency>
            <groupId>org.jboss.spec</groupId>
            <artifactId>jboss-javaee-web-7.0</artifactId>
            <version>1.0.0.Final</version>
            <type>pom</type>
            <scope>provided</scope>            
        </dependency

For EE6 on JBoss AS7.x, use:

        <dependency>
            <groupId>org.jboss.spec</groupId>
            <artifactId>jboss-javaee-6.0</artifactId>
            <version>1.0.0.Final</version>
            <type>pom</type>
            <scope>provided</scope>
        </dependency>

Info from JBoss’s EE spec Git repo here and referenced from this question here.

Posted on

Git notes (3) – tagging

To tag all files at a current point in time (e.g. to track a release), use:

git tag -a tagname -m "tag description"

To view current tags:

git tag

To show commits associated with a tag:

git show tagname

To push a tag to a remote repo:

git push remotename tagname
Posted on

Git notes (2): Checking out a branch

Continuing from other notes here.

To checkout a branch:

Clone a repo:

git clone user@server:reponame.git

Fetch all branches:

git fetch remote_name

List all available branches:

git branch -v -a

Checkout required branch:

git checkout -b branch_name remote_name/branch_name

Fetch all changes on branch:

git fetch

 

Posted on

D-Star setup with Icom ID880H

The 880H supports a couple of different approaches to using DSTAR:

  • regular memories, each one holding repeater info plus one UR, RPT1, RPT2, MY combination, with the DV mode selected
  • DR Mode memories combined with UR memories

The regular memory approach is probably the easiest the understand in terms of how memories would be used in a non-DSTAR mode, but given that you will likely want to send link/unlink commands to the repeater, this would mean each of these combinations would occupy one additional memory.

The DR Mode uses one memory for the common repeater settings, and then you select the variable parts for UR, RPT1, RPT2 etc as needed.

If you follow the instructions in the 880H manual for configuring DR Mode, it talks about three settings, GRP CQ, GRP RPT, and GRP UR. The manual is not very clear about the difference in these modes relating to your UR, RPT1, RPT2, and MY settings however. So here’s my understanding of the differences:

  • GRP CQ – removes RPT2 setting for routing which means when you transmit, you’re only heard on the local repeater and you do not get forwarded out via the gateway to any linked reflectors or other repeaters.
  • GRP UR – does keep the RPT2 value (usually ‘repeater-call G’), plus you can select any of your stored values for UR, either CQCQCQ or a link or unlink command.

I read somewhere that you should use UR of DRCQCQ to indicate that you’re using DR mode to force the repeater to see this as destined not only for the repeater and include the gateway routing info too (RPT2). I don’t think this solves the issue of GRP CQ though, which seems to intentionally remove the RPT2 value – changing the default UR of CQCQCQ to DRCQCQ I don’t think has any effect.

So in summary, if you’re intending to get forwarded out from your repeater’s gateway, use the GRP UR mode.

  • Press DR, select one of your DR repeater memories (from your repeater list memories)
  • Long press UR and select CQCQCQ from your Callsign List
  • Select GRP UR (instead of GRP CQ) by pressing BAND button (each press cycles through GRP CQ, GRP RPT, GRP UR)
  • Long press UR and select GW instead of NOT USED.
  • Press DR Button to return to DR Mode.

I got this tip from this post here.

A few other random observations:

  • If you watch the dashboard for your repeater (eg for W6CX) and a reflector that it is linked to (eg REF014), you’ll see your call appear when you transmit on the repeater dashboard, but NOT the reflector. I’ve asked questions about this in multiple forums online and the opinion seems to be mixed, but I don’t believe if you are accessing a reflector linked to a repeater, then you don’t appear on the reflector’s dashboard. Initially this was misleading for me, as I misread this as I wasn’t making it to the reflector, but calling CQ and a couple of QSOs later confirmed that I was successfully being forwarded to the reflector, even though I never showed up on the reflector dashboard.

I’ll summarize a few other tips later.

Proudly powered by WordPress