Re: ESTCube GS-1

[Lauri Kimmel]

Yesterday I checked out Hummingbird from github (JohannesKlug/hummingbird.git).

I have few questions now:

1. Since I'm not able to build project with maven - what's the status of the Hummingbird at the moment? Codebase and project as well.
2. I want to use Hummingbird to control ground station. GS has dedicated PC and uses Hamlib to control the radio and antenna rotator. What I need to do to connect Hummingbird to Hamlib daemons (simple text line based protocol over TCP/IP)?

 

----- Original Message -----

From: Lauri Kimmel

Sent: 09/23/11 04:16 PM

To: humming...@googlegroups.com

Subject: ESTCube GS-1

Hi,

I'll check the new generic parameter soon.

In the meanwhile here is protocol documentation for Hamlib TCP daemons which are going to be used in the ESTCube GS-1 to control antenna rotator and radio.

http://hamlib.sourceforge.net/pdf/rigctld.8.pdf
http://hamlib.sourceforge.net/pdf/rotctld.8.pdf

Our first plan was to implement custom codecs for these protocols using camel-netty component.
After discussion with Johannes and Mark today it looks like there might be better solution for this.

So, I'm waiting for your opinion now =)

Thanks,
Lauri Kimmel

 

----- Original Message -----

From: Johannes Klug

Sent: 09/23/11 12:37 PM

To: humming...@googlegroups.com

Subject: New, generic Parameters for Hummingbird

 
 
Dear devs, 

Mark recently created a generic parameter [1], which can hold any type 
of actual "payload". 
It could simply hold a String, or an Integer, for example. It is on the 
ssm branch currently, so not yet merged into master. 

Could others please review this, and share their thoughts? Input from 
the ESTcube project would be helpful, for example. 

Cheers, 
Johannes 


[1] 
https://github.com/JohannesKlug/hummingbird/blob/ssm/src/transport/space-system-model/src/main/java/org/hbird/transport/spacesystemmodel/parameters/HummingbirdParameter.java 

 

[Johannes Klug]

Hi Lauri,

regarding your first point: can you try and check out this one?
https://github.com/JohannesKlug/hbird

Regarding Hamlib, you could use the camel-netty or camel-mina components. I think Mark has been doing something similar for our Arduino-based rotor controller.

Johannes

[Mark Doyle]

Yeah, hummingbird.git it long dead. Move to hbird.

Not looked at the Hamlib stuff yet. I'll try and get around to it soon.

[Lauri Kimmel]

After fresh checkout from git://github.com/JohannesKlug/hbird.git
maven build failed. It turned out that src/core/xtce/src/main/
resources/schemas/SpaceSystemV1.0.xsd contains some funky qoutation
marks in documention sections like - ‘bit order’ on line 92 etc. In my
PC this ended up with compilation error - javadoc in produced sorce
files containing non UTF-8 characters. Most probably this is related
to my environment (Win7 x64, jdk 1.6.0_26 x64, Eclipse 3.7.1) but
won't hurt to change those sneeky chars to good old quotes. Which i
did and I was able to run mvn test without problems.

After that i tried to import hbird to eclipse workspace using "Import
exisiting Maven projects" wizard. This is where I'm stucked at the
moment. Eclipse is not able to update maven configuration for projects
core/common, core/space-system-model, core/xtce etc. That's it - no
meaningful error message. Just "Unable to update maven
configuration". Usual Eclipse tricks - refresh, clean, close-open
project etc. are not working.

I don't have time to play hide and seek with Eclipse at the moment. I
will continue next week and hope you can give some clues for me in the
meanwhile.

On Feb 8, 9:32 am, Johannes Klug <j...@jklug.com> wrote:
> Hi Lauri,
>

> regarding your first point: can you try and check out this one?https://github.com/JohannesKlug/hbird

> >>>https://github.com/JohannesKlug/hummingbird/blob/ssm/src/transport/sp...

[Mark Doyle]

I have no idea what you xml error was. I have a new laptop on which I did a fresh check out that worked perfectly. The system is exactly the same Win7 x64, jdk 1.6.0_26  x64, Eclipse 3.7.1.

The second error I can help with, it's a problem with the new maven plugin m2e. This is the new version of m2eclipse and the default version you will see from the latest update sites and marketplace.

This explains the core of the problem:

http://wiki.eclipse.org/M2E_plugin_execution_not_covered 

The felix bundle plugin and possibly the castor plugin don't have configurators. I am checking out FUSE FAB (fuse application bundle) which can replace the current bundle plugin.

One work around is to install the older m2eclipse. It works fine with the latest Indigo release of Eclipse. The update site is on the sonatype website.

You should still get a successful build from the command line regardless.

[Johannes Klug]

On my three Eclipse installations (all Linux, 64 bit), I've got it all set-up with the m2e plug-in that comes with Eclipse Indigo. Sometimes it reports some modules to be erroneous, but a "refresh project config" fixes that. As Mark says, the m2e plug-in isn't perfectly smooth yet.

On 02/10/2012 08:34 PM, Mark Doyle wrote:

I have no idea what you xml error was. I have a new laptop on which I did a fresh check out that worked perfectly. The system is exactly the same�Win7 x64, jdk 1.6.0_26 �x64, Eclipse 3.7.1.

The second error I can help with, it's a problem with the new maven plugin m2e. This is the new version of m2eclipse and the default version you will see from the latest update sites and marketplace.

This explains the core of the problem:

http://wiki.eclipse.org/M2E_plugin_execution_not_covered�

The felix bundle plugin and possibly the castor plugin don't have configurators. I am checking out FUSE FAB (fuse application bundle) which can replace the current�bundle�plugin.

One work around is to install the older m2eclipse. It works fine with the latest Indigo release of Eclipse. The update site is on the sonatype website.

You should still get a successful build from the command line regardless.

On 10 February 2012 18:47, Lauri Kimmel <lauri....@gmx.com> wrote:

After fresh checkout from git://github.com/JohannesKlug/hbird.git
maven build failed. It turned out that src/core/xtce/src/main/
resources/schemas/SpaceSystemV1.0.xsd contains some funky qoutation

marks in documention sections like - �bit order� on line 92 etc. In my

PC this ended up with compilation error - javadoc in produced sorce
files containing non UTF-8 characters. Most probably this is related

to my environment (Win7 x64, jdk 1.6.0_26 �x64, Eclipse 3.7.1) but

won't hurt to change those sneeky chars to good old quotes. Which i
did and I was able to run mvn test without problems.

After that i tried to import hbird to eclipse workspace using "Import
exisiting Maven projects" wizard. This is where I'm stucked at the
moment. Eclipse is not able to update maven configuration for projects
core/common, core/space-system-model, core/xtce etc. That's it - no

meaningful error message. Just �"Unable to update maven

[Lauri Kimmel]

Installing older version (0.12.1) of m2e from http://m2eclipse.sonatype.org/sites/m2e did the trick. I'm now able to run Maven build from Eclipse.

Next question is how to setup Hammlib communications. In my understanding it should look something like this:

HW <---> hammlib <---> hammlib-hbird connector <---> space system model based on hammlib protocol <---> rest of the hbird based setup

Is this correct?
Should I start with space system model deffinition?
Are there some pointers how to do it in most efficient way? Eg. using xml -> castor -> java source approach like in xtce.

----- Original Message -----

From: Johannes Klug

Sent: 02/12/12 02:04 PM

To: humming...@googlegroups.com

Subject: Re: ESTCube GS-1

On my three Eclipse installations (all Linux, 64 bit), I've got it all set-up with the m2e plug-in that comes with Eclipse Indigo. Sometimes it reports some modules to be erroneous, but a "refresh project config" fixes that. As Mark says, the m2e plug-in isn't perfectly smooth yet.

On 02/10/2012 08:34 PM, Mark Doyle wrote:

I have no idea what you xml error was. I have a new laptop on which I did a fresh check out that worked perfectly. The system is exactly the same Win7 x64, jdk 1.6.0_26  x64, Eclipse 3.7.1.

 

The second error I can help with, it's a problem with the new maven plugin m2e. This is the new version of m2eclipse and the default version you will see from the latest update sites and marketplace.

 

This explains the core of the problem:

http://wiki.eclipse.org/M2E_plugin_execution_not_covered

 

The felix bundle plugin and possibly the castor plugin don't have configurators. I am checking out FUSE FAB (fuse application bundle) which can replace the current bundle plugin.

 

One work around is to install the older m2eclipse. It works fine with the latest Indigo release of Eclipse. The update site is on the sonatype website.

 

You should still get a successful build from the command line regardless.

On 10 February 2012 18:47, Lauri Kimmel <lauri....@gmx.com> wrote:

After fresh checkout from git://github.com/JohannesKlug/hbird.git
maven build failed. It turned out that src/core/xtce/src/main/
resources/schemas/SpaceSystemV1.0.xsd contains some funky qoutation

marks in documention sections like - ‘bit order’ on line 92 etc. In my

PC this ended up with compilation error - javadoc in produced sorce
files containing non UTF-8 characters. Most probably this is related

to my environment (Win7 x64, jdk 1.6.0_26  x64, Eclipse 3.7.1) but

won't hurt to change those sneeky chars to good old quotes. Which i
did and I was able to run mvn test without problems.

After that i tried to import hbird to eclipse workspace using "Import
exisiting Maven projects" wizard. This is where I'm stucked at the
moment. Eclipse is not able to update maven configuration for projects
core/common, core/space-system-model, core/xtce etc. That's it - no

meaningful error message. Just  "Unable to update maven

[Mark Doyle]

I've finally cracked this! Well, I'm pretty sure I have.

Bundle builds in m2e should now work with now project configuration errors. I also fixed the xtce castor generated sources issue.