Sends another code

[Sn0ff]

HI, Thanks for CCManager
I do not know whether this is a problem or not . But always sends such code as in the picture ,Then sends the code that needs to be sent.

Sorry for bad english

"Audacity img"

[jglim]

Hi! Thanks for reporting this issue. Would this issue be related to your problem?

In the meantime I also realized that the previously compiled binary was not in sync with the current code. I've rebuilt and updated the binary at https://github.com/jglim/CCManager/raw/master/other/CCManager.exe

Perhaps you can try again with the new version and let me know if the issue has been resolved?

[Sn0ff]

Thanks for the quick response

1. Yes, the first part is disappeared, But when I send 0xEE, 0x00, 0xEE, 0x00 see screenshot

2. And I have another question I can use Serial Terminal instead CCManager ?
   something like this ( -f 430.0000 -b 3333 -h 0xEE, 0x00, 0xEE, 0x00 )

3. And just want to share a photo of the resulting device
   

Thanks..

[jglim]

I am able to replicate your issue (the extra "bit" before the data) but unfortunately I was unable to disable it. In the meantime can I recommend sending a few 0x00s before your data if the extra bit affects your receiver?

A command line mode is a great idea - I've implemented it, and the usage is below:

ccmanager -h:00FF00AA00FF -f:433.92 -b:3333 -p:COM23

-h: Data in hex, no affixes
-f: Frequency (MHz)
-b: Transmission baud rate
-p: Hardware's serial port name

Your hardware looks fantastic too, especially how the enclosure is assembled! Thanks for using CCManager ^_^

[Sn0ff]

1. No, the extra bit does not effects on receiver (Thanks for the recommendation) .
   I have a request, If possible and you will have time to write a terminal version of the CCManager in the Python or BASH. for linux (I will try too, but May knowledge is limited)

2. I did not understand how to use command line mode like this ?
   ( /Dir_To_File/ccmanager.exe -h:00FF00AA00FF -f:433.92 -b:3333 -p:COM23 )

3. There is a small bug . If you press Transmit without Data the CCManager gives an error and freezes.
   You can disable the button until the data is entered (If possible)

once again THANKSSS

[jglim]

At the moment CCManager will be C# only, though I think it does not use windows-specific APIs and might run via Mono on other platforms. The underlying communications layer is simply via the serial port, so please feel free to try!

The command line mode works by running CCManager.exe with the 4 required parameters:

-h: Data in hex, no affixes
-f: Frequency (MHz)
-b: Transmission baud rate
-p: Hardware's serial port name

Here is an example of sending the data 0x00, 0xFF, 0x00, 0xAA, 0x00, 0xFF on 433.92 MHz with a baud rate of 3333. The hardware's port name on my computer is COM23.

Please note that this runs from your computer (command prompt) to generate the serial data (serial terminal) required for the hardware to transmit. I might have misunderstood that part - sorry!

I've also fixed the transmit crash. Thanks for bringing it up

[Sn0ff]

I guess I'm stupid ! ;) But when I insert a command in terminal CCManager.exe -h:00FF00AA00FF -f:433.92 -b:3333 -p:COM5 He opens a window to choose Com Port , After the selection opens CCmanager

As if he does not see this part ((( -h:00FF00AA00FF -f:433.92 -b:3333 -p:COM5 )))
what am I doing wrong
Maybe you did not update Github ? Because the transmit crash also left

Thanks

[jglim]

Hi no worries - I've downloaded the binary from Github, checked it again and there appears to be no problem. Maybe removing older versions of CCManager.exe and re-downloading it from https://github.com/jglim/CCManager/raw/master/other/CCManager.exe might work.

For reference, the sha1sum of the most recent binary is
de20293ecc7830789954227c9c60afd97626109d CCManager.exe

An easy way to check: if the transmit button is pressed with invalid values, it should report an error instead

[Sn0ff]

Yes, I downloaded it again and checked sha1sum it matches .

1. Transmit crash is gone.
2. Terminal mod still opens a window to choose Com Port , After the selection opens CCmanager.
   Probably a problem only in my pc.

Thank you !

[CptLeeChuck]

I had the same command line issue (prompting for port) even if the arguments are correct. The bug is here, this compares the available ports with the one from command line. This Loop works if there is only one port at the system. But if you have 3 ports (as in my case) it will loop 3 times and set 2 times "canStartInConsoleMode = false;" and therefore never enter command line mode.

 foreach (string availablePort in SerialPort.GetPortNames())
            {
                if (availablePort.ToUpper() == serialPortName.ToUpper())
                {
                    SerialPort sp = new SerialPort(serialPortName);
                    if (sp.IsOpen)
                    {
                        Log.Error("Specified serial port is in use!");
                        Environment.Exit(0);
                    }
                    else
                    {
                        break;
                    }
                    sp.Dispose();
                }
                canStartInConsoleMode = false;
            }

[jglim]

Thanks @CptLeeChuck ! I've updated the checks ( fb9591d ) and I hope it works correctly now for you too. The updated binary is available here.

[szakal1919]

I still have a problem with terminal mode mentioned by Sn0ff. Is there a solution for this ?

[Delson704557]

Thanks for the quick response

1. Yes, the first part is disappeared, But when I send 0xEE, 0x00, 0xEE, 0x00  see screenshot

1. And I have another question I can use Serial Terminal instead CCManager ?
   something like this ( -f 430.0000 -b 3333 -h 0xEE, 0x00, 0xEE, 0x00 )

2. And just want to share a photo of the resulting device
   ![stick](https://user-images.githubusercontent.com/31393093/29772760-75aabf88-8bfa-11e7-833d-e1cb84ef5742.jpg)

Thanks..

What is that Black thingy right down to CC1101 and Pro mini

[jglim]

The device that you described is @Sn0ff 's custom build, though it should most likely be a USB-UART module

[Delson704557]

The device that you described is @Sn0ff 's custom build, though it should most likely be a USB-UART module

Thanks for your reply !

By any chance can you give the Circuit connection for the Entire build???