Stokerforum
Pillefyr => Boink, Scotte, Woody, Biocomfort, RTB => Emne startet af: Profft efter Okt 31, 2015, 15:07
-
Jeg har opgivet stokerkontrol på min rasperry men er nu gået igang med Pellmon.
Det er også gået godt.
Men
Jeg kan ikke få kontakt mellem pillefyr og Pellmon den står bare på "Connecting..."
Nogle forslag, er kørt fast :-/
-
Jeg går ud fra du benytter en USB til seriel adapter, virker den?
-
Ja det skulle jeg mene.
Den kommer i hverfald frem når jeg skriver lsusb
-
Og du har givet Pellmon lov til at benytte seriel porten som beskrevet i Readme.
-
Ja og den skriver sådan her i events
2015-10-31 17:19:15,437 - INFO - Activated plugins: ScotteCom, SiloLevel, Consumption
2015-10-31 17:19:15,420 - INFO - version detection failed
2015-10-31 17:19:15,401 - INFO - Timeout again, give up and return fail
2015-10-31 17:19:13,380 - INFO - Timeout again, give up and return fail
2015-10-31 17:19:11,336 - INFO - serial port ok
2015-10-31 17:19:10,860 - INFO - starting pelletMonitor
2015-10-31 17:10:51,288 - INFO - Activated plugins: ScotteCom, SiloLevel, Consumption
-
Kan det være porten der er forkert?
og hvor retter jeg evt den?
Bus 001 Device 004: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x067b Prolific Technology, Inc.
idProduct 0x2303 PL2303 Serial Port
bcdDevice 3.00
iManufacturer 1 Prolific Technology Inc.
iProduct 2 USB-Serial Controller
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x000a 1x 10 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Device Status: 0x0000
(Bus Powered)
-
Her kommer jeg nok lidt til kort ???
Mine Linux evner er desværre rimeligt begrænsede.
Men Motoz plejer at svare hurtigt på spørgsmål her i forummet, så mon ikke han kan jeg hjælpe.
-
Jeg ved heller ikke meget om Linux, så det er godt Google kan hjælpe hjælpe lidt :-)
Nu har jeg prøvet at starte helt forfra med at geninstaller raspberry og lægge pellmon på igen og jeg kommer frem til samme resultat :-/
Så jeg håber der er nogle der har et løsningsforslag?
-
Og du har fulgt installationsvejledningen slavisk og husket de såkaldte dependendies.
-
Ja det har jeg.
Har prøvet igen og den skriver de er opdateret.
-
Hello Profft.
First, run this in the terminal:
ls /dev/ttyU*then you should see:
/dev/ttyUSB0
But that hardly is the problem.
Looking at your message history I found that at some point you had chip version 4.13. Is that still the case?
Pellmon is made according to the protocol specifications found here http://www.nbe.dk/download/pc-kommunikation.html, starting from version 4.99. I know that older versions did communication slightly different (no checksums), but since I don't have any specifications or access to a control box with the old chip I had to guess how to handle it.
PellMon does try to work with a chip that responds without checksum but the code is untested and might be wrong. It works like this: if there is no answer on version detection to a request with checksum then PellMon resends the request without checksum and expects a response without checksum. It is possible that the request should still have a checksum even though the response doesn't have it, or vice versa, or the code might be buggy since I couldn't test it. Another possibility of course is that these old chips have completely different communication.
Anyway, If you are interested we could try to work out a solution (which involves you trying out possibly several different test versions of pellmon), otherwise chip version 4.99 should work fine.
-
I am with to try different versions.
-
Thanks to the patient cooperation by Profft we now have support for V4 control boxes older than 4.17 in PellMon version 0.3.0
(PellMon finally has a version number, releases and a changelog)
https://github.com/motoz/PellMon/releases
I'm still not quite sure how V4 boxes from 4.17 but older than 4.99 and the earliest V5 boxes behave. PellMon tries to handle them anyway but I haven't gotten any feedback on those yet.